My self-hosted server will not start

Check the log for a port already in use, a missing execute permission, a damaged download or database, then try --repair.

Self-Hosted Issues · Updated November 19, 2026

Check the log first. It names the cause.

  • Logs are in the logs folder of your data directory. After a crash, last-crash.txt there says why.
  • Run gamevox-self-hosted-server --logs to see the latest lines, or sudo gamevox logs on a Linux service install.
  • On Windows, startup and service errors are also in Event Viewer under Applications and Services Logs > GameVoxSelfHosted.

See View server logs.

Causes and fixes

Port already in use. Another program uses port 8088 or 7070. CubeCoders AMP is a common one. Set a different TCP_PORT or UDP_PORT, or on Docker remap the port, for example -p 8090:8088. See Environment variables. Two GameVox servers on one machine each need their own ports and data folder. See Run more than one server.

Permission denied on Linux. Make the binary executable:

chmod +x gamevox-self-hosted-server

"database is read-only". The data folder belongs to another user, often after running the server once as root or Administrator and then as a service. On a Linux service install:

sudo chown -R gamevox:gamevox /opt/gamevox

On Windows, give your account Full Control of the data folder, then restart the server.

"magic marker not found". The binary is damaged or is not your server's binary. Download it again from your server's download page in the GameVox app.

The service is broken, or an uninstall left the service registered with the files gone. Repair it. This keeps the same data directory and ports:

sudo ./gamevox-self-hosted-server --repair

On Windows, run .\gamevox-self-hosted-server.exe --repair from an Administrator PowerShell. Add =N for a specific instance, for example --repair=2.

The database is damaged. This is rare. If the server runs, restore the latest snapshot in Server Settings > Backups. If it cannot start, copy a database snapshot from a backup folder over the live database by hand. See Back up and restore.

It broke right after an update. If a new version fails to start twice, the server goes back to the previous version by itself. If it stops on a database error, it asks GameVox for a newer build that fixes it. See Update failed.

Still need help?

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

Email support@gamevox.com