Self-hosted server update failed or did not install
Updates wait while people are in voice, and failed updates are usually a full disk or no permission to write next to the binary.
The update has not installed yet
The server skips updates while anyone is in voice, so calls are not cut off. GameVox offers the update again about every 15 minutes, and it installs the first time nobody is in voice.
To install now, the owner clicks Update & Restart in Server Settings > Server. People in voice are disconnected briefly.
The update failed
The server keeps running the current version and tries again at the next offer. Check the log for the error. See View server logs.
- The disk is full. Free space on the drive with the binary and data folder. Reclaim disk space on the Backups tab can strip file backups from old snapshots.
- Permission denied. The server must be able to write to the folder that holds its binary. Make sure the service user can write there.
The new version will not start
If a new version fails to start and connect twice, the server puts the previous version back by itself. The previous binary is kept as .old next to the main one until the new version connects. Still stuck? See Server will not start.
Docker keeps going back to an old version
Use the entrypoint.sh from the GameVox Docker download and keep the ./data:/app/data volume. Updates are written to data/bin/ on the volume, so they survive container rebuilds. See Run a self-hosted server with Docker.