Skip to content

Ports and Firewalls

Liam Robinson edited this page Nov 8, 2026 · 1 revision

Ports and Firewalls

The ports

With the default port = 27450:

Port Protocol What uses it When
27450 UDP the game: rides, chat, scripts' messages always
27450 TCP HTTP: the join, the server's details, the player list, resource downloads, the remote console, /metrics always
27451 UDP the server browser's query and ping (port + 1) [discovery] query (on with public, the default)
35450 UDP LAN discovery (the game's LAN tab broadcasts here) [discovery] lan = true

Change port in [server] to move the first three: the query always uses port + 1. The LAN port is fixed. Players outside your network need UDP and TCP on the game port and, for the browser's ping, UDP on the query port.

Firewalls

Open the ports for inbound traffic. On Linux with ufw:

sudo ufw allow 27450/udp
sudo ufw allow 27450/tcp
sudo ufw allow 27451/udp

On Windows, in an administrator's PowerShell:

New-NetFirewallRule -DisplayName "Project Avalanche server (UDP)" -Direction Inbound -Protocol UDP -LocalPort 27450,27451 -Action Allow
New-NetFirewallRule -DisplayName "Project Avalanche server (TCP)" -Direction Inbound -Protocol TCP -LocalPort 27450 -Action Allow

Windows may also ask the first time avalanche-server.exe listens; allow it on the networks you host on. Add UDP 35450 if you turn LAN discovery on.

IPv6

bind = "0.0.0.0" (the default) listens on IPv4 only. bind = "::" listens on IPv6 and IPv4 at once, on the game port, the HTTP side and the query. A specific address (bind = "192.168.1.20" or an IPv6 address) listens on that address alone. LAN discovery is IPv4 broadcast either way.

Behind a home router

A router forwards nothing by default. Either forward the ports by hand in the router's settings (UDP 27450, TCP 27450, UDP 27451 to the server's machine), or let the server ask the router to do it:

[port_mapping]
enabled = true

The server then asks the router (the gateway of the default route, or gateway = "192.168.1.1") with UPnP IGD, PCP or NAT-PMP, in the order of methods. It maps the game port (UDP and TCP) and the query port to the same numbers outside, all of them or none. Each mapping lasts lifetime seconds (7200 by default) and is renewed at half of it; the server removes the mappings when it stops. It talks only to the gateway's own address and logs every refusal with the router's reason; status shows the mapping's state.

This only works when the router supports one of the three methods and has it switched on. Port mapping is refused when bind is an IPv6 address alone (the methods map IPv4). In Docker, port mapping needs the host's network (Running in Docker).

Checking from outside

Once the server runs, http://<your address>:27450/info answers in a browser with the server's details as JSON. If a friend outside your network cannot open it, the TCP side is blocked; the server browser's ping needs UDP 27451.

Clone this wiki locally