Skip to content
nuVPNnuVPNDocumentation

Updates and rollbacks

Gateways update automatically. You do not need to install new versions manually.

Automatic updates

Section titled “Automatic updates”
  • When a new version is released, the gateway receives an update offer as part of its regular reporting to nuVPN. On Linux, it updates immediately. On Windows Server, it checks for an update offer every 10 minutes.
  • The gateway only installs a version signed with the nuVPN release signing key, and only if the downloaded file matches the signature. On Windows, the MSI file's code signature is also checked. If an update fails these checks, it is rejected and the current version keeps running.
  • You cannot defer an update or lock the gateway to a specific version.
  • The Gateways page in the partner panel shows each gateway's version. Gateways running a version older than the latest release are marked Outdated version.

Rollbacks

Section titled “Rollbacks”
  • On Linux, a copy of the previous version is kept. If the new version cannot run for 2 consecutive minutes even after 3 starts, the gateway automatically rolls back to the previous version.
  • On Windows Server, the update is installed as an MSI file. If installation fails, Windows Installer restores the previous version. The failed update is retried after 6 hours.
  • Devices and profiles are stored in the gateway's database, so updates and rollbacks do not delete them.
  • There is no command for manually rolling back to a previous version.

What you can do

Section titled “What you can do”
  • If a gateway stays on an older version, check that it is connected. Only gateways reporting to nuVPN receive updates.
  • On Linux, you can rerun the installation script on a server where the gateway is already installed, without an installation code. The script verifies and replaces the files. Your devices and settings are preserved.
Terminal window
curl -sSL <INSTALL_URL> | sudo bash
  • On Windows Server, you can install an MSI file for a newer version. Installing an older version is blocked.
  • Windows Update is the responsibility of whoever operates the server. We recommend scheduling a regular maintenance window so restarts do not catch employees by surprise.
  • If a gateway repeatedly rolls back to the previous version, collect the details listed on the Escalation and support page and contact support.