Sauerbraten Server Not Showing in the Server Browser? Fixes

A Cube 2: Sauerbraten server shows in the server browser only after the master server at sauerbraten.org accepts its registration, and the master checks that by pinging the server's info port, which is always the game port plus 1. So the usual fix is to open UDP 28786 (or your port + 1) as well as 28785, and to make sure updatemaster is 1. The server log tells you which problem you have: master server registration succeeded means you are listed, and master server registration failed: failed pinging server means the info port is closed.

How Sauerbraten servers get listed

1. When the server starts, it opens a TCP connection to the master server (sauerbraten.org, port 28787) and sends regserv with its game port.
2. The master pings the server on UDP game port + 1, the info port, a few times.
3. If a reply comes back, the master answers succreg and the server logs master server registration succeeded. If not, it answers failreg with a reason, logged as master server registration failed: ....
4. The server repeats the registration every hour while it runs.
5. Players' clients download the list from the master and then ping each server's info port themselves to show the ping, player count, map and description.

That last step is why a closed info port hurts twice: the master will not list you, and even players who add your server by hand see no ping or details.

Read the log first

Start the server and watch the first lines:

Fix 1: open the info port

Forward and allow both UDP ports:

If you moved the game to 30000, the info port is 30001, and that is the one the master pings. A router rule for only the game port is the single most common reason a working server never appears in the list. The router side is covered in how to port forward a game server.

On Linux with ufw:

sudo ufw allow 28785:28786/udp

On Windows:

netsh advfirewall firewall add rule name="Sauerbraten" dir=in action=allow protocol=UDP localport=28785-28786

Restart the server after changing ports so it registers again straight away instead of waiting for the hourly refresh.

Fix 2: registration is turned off

Two settings stop the server from even trying:

updatemaster 0

in server-init.cfg, or an empty master server on the command line (-m with nothing after it), which sets updatemaster to 0. Make sure server-init.cfg says:

updatemaster 1

and that -m is either left off or set to sauerbraten.org. Remember that server-init.cfg runs after the command line flags, so a line in the file wins over a flag.

Fix 3: the server cannot reach the master

could not connect to master server means the outbound TCP connection to sauerbraten.org port 28787 failed. Check DNS on the machine (ping sauerbraten.org), and that no outbound firewall or VPS security group blocks TCP 28787. If you set -m to a different master, make sure it is spelled right and still running.

Fix 4: CGNAT or a double router

If the log says failed pinging server and your forwarding looks right, check your router's WAN IP against what a "what is my IP" site reports. If they differ, or the WAN IP starts with 100.64 to 100.127, your provider uses CGNAT and nothing you forward at home will be reachable from outside. A router behind another router (an ISP modem in router mode) needs the ports forwarded on both. The options are in how to host a game server without port forwarding.

Fix 5: it is listed, but players do not see it

If you have master server registration succeeded but a friend still cannot find the server:

• They need to refresh. In the server browser, use the update option, or type /updatefrommaster in the console. Old lists are cached in their servers.cfg.
• Check serverdesc is what you think it is. The name in server-init.cfg overrides -n because the file runs last, and an empty serverdesc "" line leaves the server showing only its address.
• A server in mastermode 3 (private) is still listed but nobody can join it. Use /mastermode 0 or have the master leave.

Joining without the browser

The browser is a convenience, not a requirement. Any player can always connect directly by pressing T and typing:

/connect your.server.ip 28785

That adds the server to their personal list too, so next time it shows under their recent servers. For a private group this is all you need, and you can skip the master server entirely with updatemaster 0.

On a GamezServers server

On a GamezServers Cube 2: Sauerbraten server, the master server and description are panel settings and the console shows the registration result live, so you can see straight away whether the master accepted the server. Players can always join with /connect and the address and port from your panel. If the console shows failed pinging server, email support@gamezservers.com with the server name and we will look at the info port for you. For admin commands once players are in, see Sauerbraten master and admin commands.

FAQ

What port does the Sauerbraten master server ping?

Your game port plus 1, over UDP. With the default port 28785 that is 28786.

How often does a Sauerbraten server register with the master?

At startup and then once an hour while it runs. Restarting the server forces a fresh registration.

Can players join a Sauerbraten server that is not in the browser?

Yes. Press T and type /connect with the server address and port. The server browser is only a list, not a requirement.

Why does my server show in the browser with no ping or description?

The client cannot reach the info port (game port + 1). Open that UDP port as well as the game port.