Update troubleshooting
Find out why an update couldn't start or hasn't finished.
Read the installation type
A standalone CLI replaces its binary. A desktop flow updates the app and bundled component. Docker and the Proxmox server image path replace the container image.
An update command inside a container can report availability without applying a binary replacement. Pull and recreate the image instead.
Running sessions prevent an update
An update or restart may stop before making changes if it would interrupt running sessions. Review that work, then use maintenance or stop the sessions when it's safe. Use --force only if you accept the interruption described in the warning.
Signature or download failure
Check the configured release source and asset target. Don't bypass a signature failure. Use a coherent set of artifacts from a trusted release.
An empty release URL disables network fetching. Use the documented local-file path for an intentionally air-gapped installation.
Update staged but not running
--no-restart installs the update but leaves the current process running. You may also need to restart manually if the service is missing or stopped. After restarting, check the running version to confirm the update took effect.
Rollback
Keep a separate backup before rolling back the server database. A binary rollback on a node can fail the server's exact protocol check.
Next steps
Read Update the server, Node updates, and Backups and restoration.
Edit on GitHubLast updated on
