Open Fortress Server Not Showing or Version Mismatch (Fixes)

Q: Why is my Open Fortress server not showing up?

Check svlan 0, that UDP 27015 is open, and that the server is on the current alpha. Direct connect works even when the list is slow.

Q: How do I join a passworded Open Fortress server?

Open the console, type password followed by the password, then connect with the address.

Most Open Fortress connection problems come from version mismatches: after an alpha update, the server and every player must run Beans again so all sides are on the same build, otherwise players see a version error or the server disappears from their list. The other common causes are sv_lan 1 in the server config, UDP 27015 not reachable, a password that was not entered with password before connect, and players missing Team Fortress 2 or Source SDK Base 2013 Multiplayer on Steam.

Start with the version

Open Fortress is distributed as an alpha through the Beans updater from openfortress.fun, not through Steam updates. Nothing updates on its own:

When the alpha updates, players run Beans to get the new build.
The server also needs Beans run against its install, then a restart.
Until both sides match, Source either hides the server or refuses the connection with a version message.

The fix is the same every time: update the server with Beans, restart it, and ask everyone to run Beans and restart Steam. If one player still cannot join while others can, they are almost certainly still on the old build.

Keep in mind that a free Steam release is listed for 2026 and the developers have said it will differ from the alpha. When it arrives, expect players on the Steam version and players on the alpha to be unable to share servers until you know which one your server runs.

Open Fortress, a Source engine arena shooter

Server not in the list

Check	What to look for
`sv_lan`	Must be `0` in `server.cfg`. With `1`, only your local network sees it
Port	UDP `27015` (or your `-port`) forwarded and allowed through the firewall
Version	Server and players on the same alpha build
Startup	The console shows the map loaded and no fatal errors
Filters	Players' browser filters for empty, full or passworded servers

If the server still does not appear but everything above is right, try connecting directly. Source server lists depend on Steam's master server, and a new server can take a little while to show up. Direct connect skips the list entirely.

Joining by console

Open Fortress players connect the classic Source way:

Enable the developer console under the game's keyboard options, Advanced.
Open it with the tilde key.
If the server has a password, type password yourpassword and press Enter first.
Type connect 203.0.113.10:27015 with your server's address.

Typing the password after connect does not work, and players then see a bad password message. They must set it first.

Players get missing content or crash on join

Open Fortress needs Team Fortress 2 and Source SDK Base 2013 Multiplayer installed on Steam, and the alpha installed with Beans. If one is missing, the game either will not start or crashes when loading a map. Have the player check both are installed, run Beans again, and restart Steam.

On the server side, missing content usually means gameinfo.txt does not point at the right TF2 and HL2 folders. The server may still start but serve broken maps. Check the paths in open_fortress/gameinfo.txt match where the TF2 server files are installed.

Custom map problems

If players can join stock maps but drop when the server changes to a custom one:

They do not have the map and downloads are off. Set sv_allowdownload 1, or set up sv_downloadurl for fast downloads.
Their copy differs from yours, which gives a map differs error. They should delete their copy so it downloads again.
The map was made for an older alpha and crashes after an update. Take it out of mapcycle.txt.

Our custom maps guide covers each of these in detail.

The server starts and then stops

Watch the console from the start. Typical messages point to:

A missing library on Linux, fixed by the _srv.so symlinks described in the Open Fortress hosting guide.
A start map that does not exist. Check the +map value matches a file in maps/.
Port already in use, if a second server on the machine uses the same -port.

Port forwarding at home

If you host from home, forward UDP 27015 to the machine and allow srcds through the firewall. Behind CGNAT, forwarding cannot work at all. How to port forward a game server covers routers, and hosting without port forwarding covers the CGNAT case.

The fix list for match night

Restart the server so it is on the current alpha.
Post in your group chat: "Run Beans, restart Steam."
Share the exact connect line, with the password step first.
Keep a stock map as the start map, so a broken custom map does not take the whole night down.

Open Fortress gameplay screenshot

Easier with a host

A GamezServers Open Fortress server runs the same alpha build players download, with its own address and the port already open. If players see a version error after an alpha update, restart the server from the panel so it pulls the update, then have everyone run Beans. The live console shows the start map loading, and server.cfg is a click away in the file manager.

FAQ

Why can't I join my Open Fortress server after an update?

Your client and the server are on different alpha builds. Update the server, restart it, and run Beans on your own PC.

Why is my Open Fortress server not showing up?

Check sv_lan 0, that UDP 27015 is open, and that the server is on the current alpha. Direct connect works even when the list is slow.

How do I join a passworded Open Fortress server?

Open the console, type password followed by the password, then connect with the address.

Do players need TF2 to play Open Fortress?

Yes. They need Team Fortress 2 and Source SDK Base 2013 Multiplayer installed, both free on Steam.