> 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/xsoar-6-administrator-guide/6.14/onboard-cortex-xsoar/single-server-deployment/upgrade-the-cortex-xsoar-server.md). # Upgrade the Cortex XSOAR Server Upgrade a Cortex XSOAR 6.14 server with preparation, installation, and post-upgrade validation steps. The installer automatically detects the existing configurations and applies them to the upgraded server. When performing an upgrade, the following core content packs may automatically upgrade to a newer version:
Core content packs * 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
**Before you begin** * If you are using a server with Elasticsearch for indicators only, you need to migrate all the data to Elasticsearch using the [Migration Tool](/xsoar-6-administrator-guide/6.14/onboard-cortex-xsoar/elasticsearch/migration.md#UUID-9b12a2c4-fbfd-366c-f1b5-d5bb3ee6d965) before upgrading. * Verify that your system meets the [system requirements](/xsoar-6-administrator-guide/6.14/onboard-cortex-xsoar/single-server-deployment/system-requirements.md), including the required operating system. * You can upgrade by up to two versions at a time. For example, if you want to upgrade to Cortex XSOAR 6.13 and you are in Cortex XSOAR 6.2, you upgrade to Cortex XSOAR 6.4 > Cortex XSOAR 6.6 > Cortex XSOAR 6.8 > Cortex XSOAR 6.10 > Cortex XSOAR 6.12 > Cortex XSOAR 6.13. * You can [upgrade multi-tenant deployments](broken://spaces/w0Gnt3LmZ1hd1u9rTUNQ/pages/d0aQ6LrvKB9xYljXOkVo), including high availability or disaster recovery. * (High Availability) - When upgrading a high availability environment, you must stop the demisto service on all application servers prior to performing the upgrade. * 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 list of failed integrations 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 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**.

If you use the same license, clear Download License file(s).

6. Select the checkbox to accept the license terms, then select **Download**.

In Google Chrome, set Settings → Privacy and security → Site settings → Additional permissions → Automatic downloads to Sites can ask to automatically download multiple files. This downloads the image and license files together.

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

Copy the download link button from your browser’s Downloads section to obtain the token for offline installation.

{% 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 app 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 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 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 runs, install it on the primary server. For High Availability, run the installer on one app server to trigger the database upgrade. When it is available, log in and upgrade the remaining app servers. {% endstep %} {% step %} #### Provide installation details Accept the EULA and provide the following information when prompted: 1. Server HTTPS port. The default is `443`. 2. [Elasticsearch](/xsoar-6-administrator-guide/6.14/onboard-cortex-xsoar/single-server-deployment/install-the-server-with-elasticsearch.md) 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 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/xsoar-6-administrator-guide/6.14/onboard-cortex-xsoar/single-server-deployment/upgrade-the-cortex-xsoar-server.md?ask=&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.