> 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.13/cortex-xsoar-installation-guide/upgrade-your-installation/upgrade-the-cortex-xsoar-server.md).

# Upgrade the Cortex XSOAR Server

Upgrade your Cortex XSOAR 6.13 server.

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

During an upgrade, these core content packs might automatically upgrade:

<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

To upgrade a multi-tenant deployment, including high availability and disaster recovery, see [Upgrade Your Multi-Tenant Deployment](/cortex-xsoar-6-installation-guides/6.13/cortex-xsoar-installation-guide/upgrade-your-installation/upgrade-your-multi-tenant-deployment.md).

* If your server uses Elasticsearch for indicators only, migrate all data to Elasticsearch with the [Migration Tool](/xsoar-6-administrator-guide/6.14/onboard-cortex-xsoar/elasticsearch/migration/migrate-objects-to-elasticsearch-for-a-single-server.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 Cortex XSOAR 6.12, upgrade through 6.4, 6.6, 6.8, and 6.10.
* 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. Log in to [Cortex Gateway](https://cortex-gateway.paloaltonetworks.com/accounts).
   2. Locate the tenant 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.
   7. Select **Download**.

      <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>In Google Chrome, set <strong>Settings</strong> > <strong>Privacy and security</strong> > <strong>Site settings</strong> > <strong>Additional permissions</strong> > <strong>Automatic downloads</strong> to <strong>Sites can ask to automatically download multiple files</strong>. This setting downloads the image and license files together.</p></div>

      Two files download: the `demistoserver-xxxxx.sh` installer and a zipped 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 token for offline installation.</p></div>

{% endstep %}

{% step %}

#### Copy the installer

Copy the installer to every 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 GPG public key provided with it. Open a ticket with [Palo Alto Networks support](https://support.paloaltonetworks.com/Support/Index) to obtain the key.

{% hint style="info" %}
You might 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

Run:

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

{% step %}

#### Run the installer

Run:

`sudo ./demisto.sh`

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

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

{% step %}

#### Provide installation details

Accept the EULA and provide this information when prompted:

1. Server HTTPS port. The default is `443`.
2. Elasticsearch details, if applicable, such as the URL and timeout.
3. Admin user name. 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 that 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.