Senhasegura upgrade

Senhasegura upgrade


Before execute Senhasegura update ALWAYS execute a SNAPSHOT in your hypervisor!
Snapshots in Senhasegura instances must be done with the instance powered off, to make sure that the rollback will be possible.

Info
Validate that the instance has access to the official mirror servers of the senhasegura.





  1. To begin, first turn off the senhasegura instance using the command:
  2. $ sudo orbit shutdown
  3.  After the instance is off, proceed with the execution of the snapshot the hypervisor;
  4. When the snapshot is done, turn on the senhasegura instance again and proceed to update the application.

Online update


Update the platform using our official mirror so that this instance receives the most up-to-date version of Senhasegura;
The sequence of commands below will update the package list, update the Orbit binary and update the platform. A long log output will be displayed and this process may take a few minutes.

$ sudo apt-get update
$ sudo apt-get install orbit-cli
$ sudo orbit upgrade
You will need to restart the instance to ensure that all services use this configured interface.
$ sudo orbit shutdown --reboot
Wait for the instance to finish the reboot and the system will be available to be accessed by the web interface.

Offline update

To perform the update offline, if the safe does not have Internet access, perform the following steps:
In another station, download the update package:
Upload the downloaded file to the senhasegura server (e.g. via scp):
$ scp buster-se-update.sh mt4adm@[IP]:/home/mt4adm
Perform the package installation:
$ sudo bash buster-se-update.sh
In this step, remember to make the confirmations when they are requested in the terminal.


Important
Do not execute the command "apt-get upgrade". 

If you run it, use "orbit upgrade" to fix any problem.



    • Related Articles

    • Senhasegura app certificate update

      The default senhasegura installation includes a self-signed 512-bit SSL certificate. Senhasegura recommends that you change this certificate for a valid market certificate. You can use crt or cer for the certificate and a file extension key for the ...

    • Senhasegura - System key agent was not properly initialized

      Ukoliko se nakon nadogradnje ili promjene postavki pojavi ova poruka napravite sljedeće: 1. Logirajte se preko ssh konzole (port 59022). 2. Upišite “sudo su” naredbu da bi postali root. 3. Zatim upišite naredbu “orbit application init” (potvrdite sa ...

    • N-sight RMM agent losing connection

      There is an issue in the current Windows GA Agent (v10.13.2), which is causing some servers to incorrectly show as overdue. It also fixes an issue related to Take Control policies not being adhered to in some cases. We encourage you to upgrade to ...

    • N-sight Patch Management update

      In the week of February 6th, N-sight patch management will receive a major update. As a part of this update, N-sight patching will be updated to align with Microsoft classifications, and third-party products can be configured individually. The ...

    • EDR End of Support for TLS 1.1 or 1.0

      EDR End of Support for TLS 1.1 or 1.0 Starting October 1, 2022, SentinelOne will no longer support Transport Layer Security (TLS) 1.1 or 1.0 for Agent to Management Console communication. After this change, the Management Console will not connect ...