Addresses, ports and firewalls
Game traffic, voice and resource downloads use separate connections. Configure access for the services you enable.
These are the ports in the packaged configuration:
| Service | Protocol | Port | Setting | Access |
|---|---|---|---|---|
| Game | UDP | 27015 |
port |
Players connect here. |
| Voice media | UDP | 27017 |
voice.media_port |
Players connect here when voice is enabled. |
| External voice control | UDP | 27016 |
voice.port |
The game server connects to the separate voice process. Allow access from the game server only. |
| Embedded resource hosting | TCP, HTTP | 27018 |
resources.http.port |
Players download resources here when resources.http.enabled = true. |
| Local discovery | TCP, HTTP | 27019 |
api.local_port |
Listens on 127.0.0.1 when api.enabled = false. |
For embedded voice with resources hosted on a CDN, allow public inbound UDP
traffic on 27015 and 27017 at the game server. Resource downloads go to
the CDN address in resources.url.
The game server also needs outbound access to the registration API and, in
remote resource mode, the configured resource host. HTTPS uses TCP port 443
unless the URL specifies another port.
Public addresses
Section titled “Public addresses”For a registered production server using embedded voice, merge these values into its configuration:
port = 27015
[api]public_host = "play.example.com"
[voice]enabled = truemode = "embedded"media_port = 27017public_host = ""api.public_host is the hostname or IP given to players for the game connection.
An empty voice.public_host makes voice use the game connection’s host. Both
services still use their own ports.
The hostname must resolve to an endpoint that accepts the configured UDP
traffic. For a server behind NAT, forward external UDP 27015 to game port
27015 and external UDP 27017 to voice port 27017. The public and listening
port numbers must match the settings advertised to clients.
For voice on another machine, set voice.public_host to that machine’s public
hostname or IP. In external mode, voice.host and voice.port identify the
control endpoint reached by the game server. Configure that endpoint’s firewall
to accept only the game server’s address, and set the same secret in both
server configurations. Match media_port in both configurations too. See
Run a separate voice server for the complete setup.
Resource downloads
Section titled “Resource downloads”resources.url is the full public HTTP or HTTPS base URL, including its path.
Use an address players can reach, such as https://cdn.example.com/resources/.
The resource hosting guide covers publishing to
storage and serving downloads through a CDN.
If you enable the embedded HTTP server, resources.http.host controls its
local listening address. 127.0.0.1 allows access from the same machine, while
0.0.0.0 listens on all IPv4 interfaces. Allow inbound TCP on
resources.http.port when players download directly from this server.
The embedded listener serves HTTP. To provide HTTPS through a reverse proxy,
terminate TLS at the proxy, route the path from resources.url to the embedded
listener and set resources.url to the public HTTPS address. Allow the proxy
to reach the listener.
Firewall rules
Section titled “Firewall rules”Apply the required inbound rules in the operating system and any hosting-provider firewall. Configure port forwarding separately if the server is behind NAT.
For the embedded-voice example above, run this in an administrator PowerShell session on Windows:
New-NetFirewallRule -DisplayName "Revo game and voice" -Direction Inbound -Action Allow -Protocol UDP -LocalPort 27015,27017If you change either port, update the firewall and forwarding rules as well. Keep the external voice control port restricted to the game server. Local discovery stays on loopback.
Local development and multiple instances
Section titled “Local development and multiple instances”dev resolves through http://127.0.0.1:27019/local/server on the player’s PC.
dev:27119 changes the local discovery port to 27119. The game port is read
from the discovery response.
To connect from another PC, use a registered server with an address reachable from that PC. The local setup covers running the game and server together.
For two servers on one host, follow the multiple-instance setup. It includes separate ports, state files and local join codes.
Check connectivity
Section titled “Check connectivity”| Check | What to verify |
|---|---|
| Game connection | Join from outside the server’s network using its assigned code. Check public DNS, the advertised UDP port and forwarding if it times out. |
| Voice connection | Connect two players to a voice channel. Check voice.connected and the voice endpoint if the game works but voice stays disconnected. See Your first voice channel. |
| Resource downloads | Request manifest.json below the public resources.url. It should return the resource manifest as JSON. |
| Local discovery | Open http://127.0.0.1:27019/local/server on the server PC and check the returned game port. |
| Port already in use | Check for another instance or service using that protocol and port before changing the configuration. |
Test-NetConnection -Port checks TCP. Verify the game and voice UDP endpoints
through their client connections.