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

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

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

## Requirements

- Set the correct server time.
- Take a snapshot before the update.
- The Arbitrator must be removed from the cluster (only for environments with an Arbitrator).

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 offline 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).

To update Segura™ offline, follow these steps:

1. In another machine with access to the internet, download the update package to a separate device:

```
wget https://repo:HpRh0BVMNVAq@repo.senhasegura.com/bullseye-se-update.sh --no-check-certificate
```

1. Create a folder for the update files inside the `/var/update` directory.  Use the following command:

```
sudo install -d /var/update -g mt4adm -o mt4adm
```

1. Contact Segura™ technical support to upload the update file.
2. Add a "**#**" symbol to comment every line in `resolv.conf` to prevent it from trying to connect to the internet during the update:

```
sudo vim /etc/resolv.conf
```

1. Give the user permission to run the update file:

```
sudo chmod +x <update_file_name>
```

1. In our example, we named the update file `bullseye-se-update.sh`, so our command is:

```
sudo chmod +x bullseye-se-update.sh
```

1. Run the package using the following command:

```
sudo bash <update_file_name>
```

1. Run the following command to reboot the device:

```
sudo orbit shutdown --reboot
```

1. Run the package one more time using the following command:

```
sudo bash <update_file_name>
```

1. Type **Y** to agree with the EULA terms.
2. After running the update file, return to `resolv.conf` and remove the '**#**' symbol from all previously modified lines.
3. Run the following command to reboot the device:

```
sudo orbit shutdown --reboot
```

1. After the reboot is complete, run the following command and type **Y** to confirm:

```
sudo orbit application init
```

1. A message in the terminal will indicate that the update was successful. To check the current version, run the following command:

```
sudo orbit version
```