How self-hosted server updates work

Your self-hosted server downloads and installs new versions by itself, and waits until nobody is in voice before restarting.

Self-Hosted Servers · Updated November 19, 2026

Your server updates itself. When a new version is out, the GameVox cloud tells your server, which downloads it, swaps it in and restarts.

What happens

  1. The cloud offers the update.
  2. The server downloads the new binary next to the current one, as a .new file, and checks its size and SHA-256 hash.
  3. Connected members are told the server is restarting for an update.
  4. The current binary is renamed to .old, the new one takes its place, and the server restarts.

If anyone is in voice, the server skips the update. The cloud offers it again about every 15 minutes, and the server installs it once voice is empty.

Update now

In Server Settings > Server, click Update & Restart next to Running Version. This installs the update even if people are in voice, so they drop briefly. Check for Updates looks for a newer version.

Docker

The running binary is kept in data/bin/ on the volume, so updates survive rebuilds and reboots. To force a version, put a newer Linux binary in the gamevox-docker folder and run docker compose up -d --build. See Docker.

Rollback

The .old file stays until the new version starts and connects to GameVox. If the new version fails to start twice, the server puts the old version back.

If an update fails, see Self-hosted server update failed.

Still need help?

Email our support team and a person will get back to you.

Email support@gamevox.com