Changelog

Overview

The releases below are read from GitHub when this site is built, so they are current as of the last deploy. Each tagged release publishes static Linux binaries for amd64 and arm64, covering the panel itself, the nasnet-tool operations tool, and an offline bundle that packages PostgreSQL and Xray-core for servers with no outbound internet access.

Upgrading

The upgrade path is the same shape whichever way you deployed, and the first step is not optional:

1. Take a backup. Database schema migrations run automatically on startup, and a failed migration is much easier to recover from than to debug.
2. Replace what is running:
   • Docker. Pull the new images and run docker compose up -d --build.
   • systemd or a plain binary. Swap the binary and restart the service.
   • Either. Run nasnet-tool.sh and choose Update, which does the same thing with the prerequisite checks attached.
3. Watch the logs through the first boot. Migrations name the step they are on, so a failure tells you where it stopped.

nasnet-tool.sh can update itself from GitHub Releases. If you hit API rate limits while it does, set a GITHUB_TOKEN in the environment.

What to read before a major upgrade

Release notes call out configuration changes, and this project moves fast enough that a new .env key or a changed default is a normal thing to find in them. Skim the notes for every version between the one you are on and the one you are moving to, not just the newest.

The upgrade itself is covered in Installation, and taking the backup that precedes it in Backup and restore.