> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xsoar-6-installation-guides/6.15/cortex-xsoar-installation-guide/upgrade-your-installation/upgrade-the-cortex-xsoar-server.md).

# Upgrade the Cortex XSOAR Server

Upgrade your Cortex XSOAR server to version 6.14.

The installer detects existing configurations and applies them to the upgraded server.

The following core content packs may upgrade automatically:

<details>

<summary>Core content packs</summary>

* Base
* CommonDashboards
* CommonPlaybooks
* CommonReports
* CommonScripts
* CommonTypes
* CommonWidgets
* DefaultPlaybook
* DemistoLocking
* DemistoRESTAPI
* EDL
* FeedMitreAttackv2
* FeedUnit42v2
* FiltersAndTransformers
* HelloWorld
* ImageOCR
* Palo\_Alto\_Networks\_WildFire
* PAN-OS
* TIM\_Processing
* TIM\_SIEM
* ThreatIntelReports
* ThreatIntelligenceManagement
* Unit 42 Threat Intelligence by Palo Alto Networks
* VirusTotal
* Whois
* rasterize

</details>

### Before you begin

* If your server uses Elasticsearch for indicators only, migrate the data to Elasticsearch using the [Migration Tool](/xsoar-6-administrator-guide/6.14/onboard-cortex-xsoar/elasticsearch/migration/migrate-an-existing-elasticsearch-deployment.md) before upgrading.
* Verify that your system meets the system requirements, including the required operating system.
* Upgrade by no more than two versions at a time. For example, to upgrade from Cortex XSOAR 6.2 to 6.14, upgrade to 6.4, 6.6, 6.8, 6.10, 6.12, and then 6.14.
* To upgrade a multi-tenant deployment, including high availability or disaster recovery, see [Upgrade your multi-tenant deployment](/cortex-xsoar-6-installation-guides/6.15/cortex-xsoar-installation-guide/upgrade-your-installation/upgrade-your-multi-tenant-deployment.md).
* For high availability, stop the `demisto` service on every application server before upgrading. Rolling upgrades are not supported.

### Upgrade the server

{% stepper %}
{% step %}

#### Prepare the server

1. Take a snapshot of the server.
2. Back up your content. Select **Settings** → **About** → **Troubleshooting** → **Export**.
3. Disable external systems that push incidents to Cortex XSOAR, such as Splunk and Elasticsearch.
4. Run `!FailedInstances` in the CLI. Save the failed integration list for comparison after the upgrade.
5. Download the new installer from Cortex Gateway.
   1. Sign in to [Cortex Gateway](https://cortex-gateway.paloaltonetworks.com/accounts).
   2. Locate the tenant you want to upgrade.
   3. Select **Re-Download On-Prem**.

      The **Production-Standalone** license is selected by default. You can also select **Dev**.
   4. Select **Next**.
   5. Under **Choose Download Option**, select **Installer**.

      <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>If you use the same license, clear <strong>Download License file(s)</strong>.</p></div>
   6. Select the checkbox to accept the license terms, then select **Download**.

      Two files download: the `demistoserver-xxxxx.sh` installer and a compressed JSON license file.

      <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>Copy the download-link button from your browser's <strong>Downloads</strong> section to obtain the offline-installation token.</p></div>

{% endstep %}

{% step %}

#### Copy the installer

Copy the installer to each server you will upgrade.

If `/tmp` is blocked by policy, specify a target directory before other installation flags. For example, `sudo ./demisto.sh --target /var/tmp --multi-tenant`.
{% endstep %}

{% step %}

#### Stop the server

For disaster recovery or high availability deployments, stop the Cortex XSOAR server.

`sudo service demisto stop`

For disaster recovery, stop the primary server first, then the backup servers. For high availability, stop every application server.
{% endstep %}

{% step %}

#### Import the GPG public key

If you use a signed installer, import the GNU Privacy Guard (GPG) public key provided with it. Open a ticket in the Customer Support Portal to obtain the key.

{% hint style="info" %}
You may need to install `makeself` manually: `yum install makeself`.
{% endhint %}

For example, run `rpm --import public.key` to import the key into the local GPG keyring. Each operating system has specific requirements.
{% endstep %}

{% step %}

#### Make the installer executable

Make the installer executable.

`chmod +x demisto.sh`
{% endstep %}

{% step %}

#### Run the installer

Run the installer.

`sudo ./demisto.sh`

For disaster recovery, run the installer on the secondary server first. After it completes, install it on the primary server.

For high availability, run the installer on one application server to trigger the database upgrade. When it is available, sign in and upgrade the remaining application servers.
{% endstep %}

{% step %}

#### Provide installation details

Accept the license agreement and provide the following information when prompted:

1. Server HTTPS port. The default is `443`.
2. Elasticsearch details, if applicable, such as the URL and timeout.
3. Admin username. The default is `admin`.
4. Admin user password. The default is `admin`.
   {% endstep %}

{% step %}

#### Validate the upgrade

1. Confirm that Cortex XSOAR is active: `systemctl status demisto`.

   If the server is not active, start it: `systemctl start demisto`.
2. Confirm that Docker is active: `systemctl status docker`.
3. Confirm that custom content and incidents appear.
4. Run `!FailedInstances` and compare the results with the list saved before the upgrade. Fix any failed integrations.
5. Confirm that integrations enabled before the upgrade are available in the CLI and Playbooks.
6. Upgrade existing engines.
7. Enable the external systems you disabled before the upgrade.

{% hint style="info" %}
When upgrading from version 6.0 or earlier, installed incident types are detached. Content pack updates do not change detached incident type configurations. Reattach an incident type manually to receive content updates.
{% endhint %}
{% endstep %}
{% endstepper %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-xsoar-6-installation-guides/6.15/cortex-xsoar-installation-guide/upgrade-your-installation/upgrade-the-cortex-xsoar-server.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.