Self-hosted server ports and port forwarding

Open TCP 8088 for chat and files, and 7070 as both UDP and TCP for voice and video, then forward them on your router.

Self-Hosted Servers · Updated November 19, 2026

Open TCP 8088 for chat, signaling and files, and 7070 for voice and video. Open 7070 as UDP and TCP. UDP is the normal path. TCP is a fallback for members whose network blocks UDP.

PortProtocolUsed for
8088TCPChat, signaling, file downloads
7070UDPVoice and video
7070TCP (optional)Voice fallback when UDP is blocked

All calls share the one UDP port, so one rule covers the whole server.

TCP 8088 and UDP 7070 are both required. If only TCP is open, chat works but voice does not.

Forward the ports on your router

  1. Find the server machine's local IP, for example 192.168.1.50.
  2. Open your router's admin page and find port forwarding.
  3. Forward TCP 8088 to that IP.
  4. Forward UDP 7070 to that IP.
  5. Optionally forward TCP 7070 for the fallback.

Also allow the ports in the machine's own firewall. See the Windows or Linux guide.

Test them

Open Server Settings > General > Network Diagnostics in the GameVox app. It shows what GameVox can reach from the internet, including the TCP fallback. Testing from inside your own network proves nothing, because that traffic never leaves your router.

Change the ports

Choose other ports when you install the service, or set TCP_PORT and UDP_PORT. The fallback follows UDP_PORT unless you set WEBRTC_TCP_PORT. WEBRTC_TCP_PORT=0 turns it off. See environment variables.

If forwarding does not work

Your provider may use carrier-grade NAT, which shares your IPv4 address so it cannot be forwarded. See CGNAT and Starlink. If everyone is on one network or VPN, you do not need forwarding. See LAN and VPN mode.

Still need help?

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

Email support@gamevox.com