Members cannot connect to my self-hosted server
Check that the server is running, that ports 8088 and 7070 are open and forwarded, and if you are behind CGNAT.
Causes and fixes
- A port is closed or not forwarded. This is the most common cause. Open the ports in the table below in the server's firewall and forward them on your router to the server's local IP. See Ports and port forwarding.
- You tested from inside your own network. That traffic never leaves your router, so it proves nothing. In the GameVox app, open Server Settings > General > Network Diagnostics and click Refresh. It shows what GameVox can reach from the internet. It appears on self-hosted servers for people who can manage the server.
- The server is not running or not connected. Check the service, container or console window, and look in the log for the line saying it is connecting to GameVox. See View server logs. If it will not start, see Server will not start.
- You are behind CGNAT. Starlink, T-Mobile Home Internet and mobile broadband often use carrier-grade NAT, where IPv4 port forwarding cannot work. Use IPv6. See Host behind CGNAT or Starlink.
- GameVox detected the wrong public IP. This happens on hosts with several IPs, split inbound and outbound networks, or Docker in bridge mode. See Set a custom public IP.
- Two copies are running. The log says "Another instance of the self-hosted server connected using the same server token". Stop the duplicate.
- Members see "token is expired". The server's clock is wrong. See Fix clock errors.
Ports
| Port | Protocol | Used for |
|---|---|---|
| 8088 | TCP | Chat, files, joining the server |
| 7070 | UDP | Voice and video |
| 7070 | TCP | Voice fallback (optional) |
Chat works but voice does not? See Voice does not work on a self-hosted server.