For whom: panel administrator. Rights required: panel administrator.
Why you can’t do it without a backup.
Remnawave drives the base migrations the first time a new image is launched, and then the old image doesn’t read the pattern, so the update is a one-way door, and the only way back is the dump taken before the switch. So the backup is not a precondition that the operator is asked about, but part of the update: the fresh dump is removed and checked right in the run, and the update does not begin until the backups on this connection are proven to actually work. The list of obstacles is the contents of the card: on a panel without backups, “you can’t update” is the normal state, and the operator must see what to fix. What the card can say:- the connection does not configure the Remnawave backup profile;
- Profile is set up, but no backup has yet been successfully executed.
- The Remnawave panel does not have a compose file, and the update changes it.
- The Remnawave panel is not detected: without access to its stack, there is nothing to update.
Choice of version
The list is the last five versions from the registry, and only fixed. Floating tags (latest, dev, bare major) do not get into it: pin on such a tag is the reason why 3.0.0 once came unnoticed and broke the installation.
Versions are not newer than the current one on the list are off. Downgrading is forbidden knowingly: the base has already migrated forward, and the honest way back is to restore the backup, which is another operation with another confirmation.
The Axottle installer asks for the Remnawave version the first time you install it, from the same list, and an unavailable registry or non-interactive launch leads to the default version, not the installation stop.
Confirmation
The update button opens a dialog that lists the consequences by item: the backup will be removed, the panel will restart and subscriptions will become unavailable for a few minutes, the base will be updated, and if you fail, the version and base will return from the same backup.Order of steps
1
backup
Remove the fresh Remnawave dump with the selected profile.
2
Backup check.
The dump is checked. The untested backup stops the upgrade: it exists to recover from it.
3
Change of version
In the compose file, the image tag is edited, the image is downloaded, the stack is recreated, and as the first steps go, the old dashboard continues to work.
4
Confirmation
The panel has to answer and name the version they asked for, and the answer with the old version is considered a failure of the update, not a protracted start.
Rollback
There are two types of recoil, and the difference is fundamental. The image didn’t jump. Nothing’s been started, the base hasn’t been touched, so only the compose file comes back, and restoring the base here would mean losing the data for nothing. The re-creation fell or the panel did not confirm the version. The new image could have time to expel the migration, so both the file and the base from the backup taken in the first step are returned. If you don’t get a rollback, the message calls the backup number for manual recovery, and it’s the one that gets read at the worst moment, so it has everything you need.Remnawave on a separate server
The update also works when Remnawave is not on the panel server; the image change and re-create is done by the agent installed on that machine; the backup, its verification, version confirmation and base restoration remain behind the panel in both cases; the requirement of a working backup does not weaken from where the panel is. A too old agent will give up the task of updating with a clear message - update the agent on this node.Compatibility of 2.x and 3.x
Axottle works with both branches of Remnawave: the version of the panel is determined by its response, and the client adjusts itself. The installer puts a third major, moving from another panel carries the version of the original.Verification
After updating, the card shows a new version, which the panel calls itself, and the number of the removed backup is visible in the step list.
Typical errors
The update stopped at checking the backup
The update stopped at checking the backup
Dump filmed, but couldn’t read it. Check the disk space and access to the backup vault, then repeat.
The panel after the update responds to the old version
The panel after the update responds to the old version
The update was considered unsuccessful, and the panel returned to the previous version with the restoration of the base, check if the image tag is redefined somewhere else in the compose file.
