---
title: "How to update versions prior to 3.29"
slug: "installation-how-to-update-versions-prior-to-329"
updated: 2026-11-03T14:48:26Z
published: 2026-11-03T14:48:26Z
canonical: "docs.senhasegura.io/installation-how-to-update-versions-prior-to-329"
---

> ## 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 online versions prior to 3.29

Customers with versions prior to 3.29 of Segura™ who wish to update to version 3.29 or later must follow the instructions provided in this article.

## Requirements

- Your [firewall rules](/v4-2/docs/installation-firewall-rules) must allow communication with Segura™ repositories.
- Set the correct server time.
- The Arbitrator must be removed from the cluster (only for environments with an Arbitrator).
- Take a snapshot before the update.

          Application unavailable during update

          

When Segura™ initiates the update process, it will be unavailable until the activity is complete.

---

## Take a snapshot

Snapshots should be taken only when Segura™ instances are offline. This ensures the ability to revert to a previous version if necessary.

1. You can shut down a Segura™ instance using the following command:

```
sudo orbit shutdown
```

1. Once the instance is completely shut down, take a snapshot in the hypervisor.
2. Reboot your Segura™ instance and update the application.

---

## How to update versions prior to 3.29

          Caution

          

Before updating Segura™, 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™. [Learn more in our documentation](/v4-2/docs/arbitrator-remove-arbitrator).

1. In the Segura™ platform, go to **Settings > Execution processes**, and turn the following items **OFF**:

- Expired password.
- Expired operation cancellation.
- Operation executor.
- Operation executor: Retry.

1. Take a snapshot.
2. [Start an SSH session using Segura™’s administrative user.](https://docs.senhasegura.io/v4-2/docs/en/administration-ssh-access)
3. Run the following commands to update the operating system to the latest Debian version:

```
apt-get update
```

4.1. Enter the following code twice as shown below:

```
apt-get install orbit-cli
apt-get install orbit-cli
```

1. To update the kernel, use the following command:

```
orbit update
```

1. After the update, restart the system to load the new kernel version:

```
orbit shutdown -r
```

1. Run the command below to update Segura™ to the newest version:

```
orbit update
```

1. After the second update, restart the system one more time to ensure that all changes were correctly applied. Use the following command:

```
orbit shutdown -r
```

1. Return to **Settings > Execution processes** and enable the following items that were turned off in step 1:

- Expired password.
- Expired operation cancellation.
- Operation executor.
- Operation executor: Retry.