--- title: "How to update Segura™ online" slug: "installation-how-to-update-senhasegura-online" updated: 2026-11-03T14:57:57Z published: 2026-11-03T14:57:57Z canonical: "docs.senhasegura.io/installation-how-to-update-senhasegura-online" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.senhasegura.io/llms.txt > Use this file to discover all available pages before exploring further. # How to update Segura™ online Important If you’re using a version prior to 3.33 and wish to update Segura™ Platform to version 3.33 or later, please refer to the article [How to update versions prior to 3.33](/v4-2/docs/how-to-update-senhasegura-in-stages). Important If you use Zabbix, it will be necessary to reconfigure it after updating Segura™ Platform to version 3.30 via Orbit Command Line Interface (CLI). For instructions on how to configure Zabbix via Orbit CLI, refer to the article [How to configure Zabbix via Orbit CLI](/v4-2/docs/orbit-cli-how-to-configure-zabbix-via-orbit-cli). In this article, you’ll find a guide on how to update Segura™ Platform online. ## Requirements - **Firewall Rules:** Ensure your firewall settings allow communication with the Segura™ Platform repositories. Detailed [firewall rules](/v4-2/docs/installation-firewall-rules) can be found in the documentation. - **Server Time:** Verify that the server's time is correctly set. - **(Situational) Arbitrator:** If your environment includes an Arbitrator, remove it from the cluster. - **Snapshot:** Take a system snapshot before proceeding with the update. - **Disk space:** Check that the appliance meets the [disk space requirements](/v4-2/docs/installation-update-senhasegura#disk-space-requirements) before the update window. - **Updating Sequentially:** For versions that are at least two releases old, update sequentially as instructed in this [article](/v4-2/docs/how-to-update-senhasegura-in-stages). - **New Segura™ Repository**: Learn how to set up the [new Segura™ repository](/v4-2/docs/installation-how-to-change-senhasegura-to-use-the-new-repository). Application unavailable during update When Segura™ Platform initiates the update process, all features will be unavailable until all nodes in the cluster have been fully updated. Caution Before updating Segura™ Platform, always run a snapshot on your hypervisor and [backup using the Orbit CLI](/v4-2/docs/orbit-cli-how-to-configure-backup). Caution If you use the Segura™ Arbitrator, remove it from the cluster before updating Segura™ Platform. [Learn more in our documentation](/v4-2/docs/arbitrator-remove-arbitrator). --- ## Take a snapshot Snapshots should be taken only when Segura™ Platform instances are offline. This ensures the ability to revert to a previous version if necessary. 1. You can shut down a Segura™ Platform instance using the following command: ``` sudo orbit shutdown ``` 2. Once the instance is completely shut down, take a snapshot in the hypervisor. 3. Reboot your Segura™ Platform instance and update the application. --- Download update packages for later installation As an option, you can download update packages to install at a later time. [Download update packages for later installation](/v4-2/docs/orbit-cli-how-to-update-the-platform#download-update-packages-to-install-later) 1. Take a snapshot. 2. [Start an SSH session using Segura™’s administrative user.](/v4-2/docs/en/administration-ssh-access) 3. Run the following command: ``` apt-get update ``` 4. Run the following command: ``` apt-get install orbit-cli ``` 5. Run the command below to update Segura™ Platform to the newest version: ``` orbit update ``` 6. After the update, restart the system to ensure that all changes were correctly applied. Use the following command to restart: ``` orbit shutdown -r ``` Debian Kernel Package Updates Pay attention to the messages displayed during the Segura™ Platform update process. If the update includes Debian kernel packages, a specific message will be shown at the end. In these cases, it is **essential** to follow the instructions in that message, which will require you to: 1. **Restart the Segura™ Platform server. (Step 6)** 2. **In some cases, run the update command again (Step 5)** Ignoring this step may result in an incomplete update or system instability.