--- title: "Upgrading a CTERA Portal" slug: "upgrading-a-ctera-portal-1" tags: ["Portal", "8.4"] status: "update" updated: 2026-10-22T18:33:48Z published: 2026-10-22T18:33:48Z canonical: "kb.ctera.com/upgrading-a-ctera-portal-1" --- > ## Documentation Index > Fetch the complete documentation index at: https://kb.ctera.com/llms.txt > Use this file to discover all available pages before exploring further. # Upgrading a CTERA Portal CTERA strongly recommends upgrading the portal with the help of [CTERA Support](https://www.ctera.com/support/). When you have Internet, you need scripts – `upgrade_online.sh` and `upgrade.sh` – and a URL where the upgrade packages are located that you get from CTERA support. For details, see [Upgrading the Portal Online](/v1/docs/upgrading-a-ctera-portal-1#upgrading-the-portal-online-internet-access). When you do not have Internet access, you need a zip file that you get from CTERA support – `tar xvf file` – where *file* is the zip filename for an offline upgrade. The file contains the packages for the portal upgrade and the script to run the upgrade. To upgrade when you don't have Internet access, see Upgrading the [Upgrading the Portal Offline](/v1/docs/upgrading-a-ctera-portal-1#upgrading-the-portal-offline-no-internet-access). Make sure that the required ports are open, as described in [Port Requirements](/v1/docs/planning-general-and-port-requirements#port-requirements). **Note** For portal version 8.4.4000.53 and later, portal servers defined with two NICs from an earlier version of CTERA Portal are upgraded and both NICs are used. The second NIC is used when enabling the CTERA MCP service and n8n service. For portal servers defined with a single NIC, the upgrade will continue with the single NIC. Portals configured with a single NIC must have a second NIC to use the MCP service and n8n service. Both NICs can be on the same VLAN but the internal NIC must have a different IP than the external NIC and they **must** be on a different network. CTERA strongly recommends a separate VLAN or proper firewall rules. ## Upgrading the Portal Online (Internet Access) **To upgrade the CTERA Portal:** 1. First upgrade the main database server. Next upgrade all application and preview servers. Finally, upgrade the replication database server. 1. Using SSH, log in as `root` to the portal server. 2. Copy the `upgrade_online.sh` file and the `upgrade.sh` file to the same directory on the machine. 2. Navigate to the directory where the script files are and run the commands: `chmod +x upgrade_online.sh` `chmod +x upgrade.sh` 3. Run the command: `./upgrade_online.sh https://<provided_upgrade_url>` where *provided_upgrade_url* is the URL received from CTERA support where the the upgrade packages are located. Patch upgrades are relatively quick as only the packages that have changed are updated. An upgrade to the next major version takes more time. **Notes** You can also check that the upgrade has succeeded by running `portal-manage.sh status` which displays the image version. ## Upgrading the Portal Offline (No Internet Access) **To upgrade the CTERA Portal:** 1. First upgrade the main database server. Next upgrade all application and preview servers. Finally, upgrade the replication database server. 1. Using SSH, log in as `root` to the portal server. 2. Copy the upgrade zip file to the machine. 2. Navigate to the location of the zip file and run the following command to extract the portal file: `tar xvf file` where *file* is the zip filename. The file contains the packages for the portal. 3. Navigate to the directory where the unzipped file is and run the following command: `chmod +x upgrade.sh` 4. Run the command `./upgrade.sh` Patch upgrades are relatively quick as only the packages that have changed are updated. An upgrade to the next major version takes more time. **Notes** You can also check that the upgrade has succeeded by running `portal-manage.sh status` which displays the image version. ## Upgrading a Portal with Subfolder Quotas Configured in an Edge Filer Subfolder quotas defined in an edge filer that were not implemented in the portal user interface, need to be exported from the edge filer and then imported to the portal to recreate the same centralized subfolder quotas in the portal using the CTERA SDK. For details, contact [CTERA Support](https://www.ctera.com/support/).