Ground Branch Server Not Showing in Browser or Can't Join (Fixes)
Ground Branch server missing from the browser or players cannot join? Fix the query port, version mismatch, filters, mod sync and startup errors.
Updated Oct 7, 2026 · 5 min read
On this page
- First: is the server actually running
- Cause 1: Query port closed or wrong
- Cause 2: Version mismatch after a patch
- Cause 3: Browser filters
- Cause 4: It shows up, but joining fails
- Cause 5: Mod sync problems
- Cause 6: Startup ignores your settings
- When it is one player only
- A server that just stays reachable
- FAQ
A Ground Branch server that does not appear in the browser almost always has a closed or wrong query port (UDP 27015 by default), is on an older build than the players after a patch, or is hidden by the browser's own filters. If it shows up but players cannot get in, look at the game port (UDP 7777), the password and the Workshop mod sync. Work through the sections below in order; most problems are solved by the first two.
First: is the server actually running
Before chasing ports, open the server log (GroundBranch/Saved/Logs/GroundBranch.log) and check it finished starting. A server that crashed on boot, or is stuck downloading an update, never registers with Steam. Common log hints:
- A config line it cannot parse, often a broken
MapList=entry after an edit. - Missing files after an interrupted update. Run SteamCMD with
validate:
steamcmd +force_install_dir C:\GBServer +login anonymous +app_update 476400 validate +quit
Cause 1: Query port closed or wrong
The browser finds servers through Steam's query system on the QueryPort. If that port is not reachable from the internet, the server can be running perfectly and still never appear.
- Check the launch line:
Port=7777 QueryPort=27015(or the values you chose). - Forward both ports as UDP to the server's local IP. TCP is not used.
- Allow the server executable through Windows Firewall, or open the UDP ports on Linux.
- If two servers share a machine, each needs its own pair of ports. Two servers fighting over
27015means one of them vanishes from the list.
If your ISP uses CGNAT (your router's WAN IP differs from your public IP), forwarding cannot work. See how to host a game server without port forwarding for the options.
Cause 2: Version mismatch after a patch
This is the most common reason a server that worked yesterday disappears today. When BlackFoot pushes an update, players get it through Steam right away, while your server keeps the old build until you update it. The game hides or refuses servers on a different version.
Fix it by running the SteamCMD update above and restarting. Since V1.0 landed on July 16, 2026, patches have come regularly, so make updating part of your routine. Also check no player is on a beta branch the server is not running: in Steam, right click Ground Branch, Properties, Betas.

Cause 3: Browser filters
The in game browser filters by game mode, map, player count and ping. A fresh server with zero players is easy to filter out without noticing.
- Clear every filter and search by exact server name.
- Turn on showing empty and password protected servers.
- Raise the ping limit. A server in another region can be hidden by a low ping filter.
If the server appears with filters cleared, nothing is wrong with the server.
Cause 4: It shows up, but joining fails
| What players see | Likely cause | Fix |
|---|---|---|
| Join hangs then times out | Game port 7777 blocked |
Forward UDP 7777, check firewall |
| Rejected straight away | Wrong password | Recheck ServerPassword in Server.ini |
| Stuck on the mod sync window | Large or broken Workshop item | Remove the newest mod, retest |
| Kicked back to menu after loading | Map or mission line broken | Fix the MapList= entry the server tried to load |
| Server full but nobody is on | Stale slots after a crash | Restart the server |
Cause 5: Mod sync problems
Ground Branch's mod sync downloads Workshop content when players join. That is convenient, but a big map can make the first join look frozen. Tell players to wait, and check their Steam download queue. If one mod fails for everyone, unsubscribe it from the server, restart, and confirm the server is joinable before adding it back. Mods made for an older game version are the usual culprit right after an update.
Cause 6: Startup ignores your settings
If the server shows but with the wrong name or slots, it read a different config than the one you edited. Make sure you edited GroundBranch/ServerConfig/Server.ini while the server was stopped. Editing during a run is silently discarded. Our Ground Branch config guide shows what each file should contain.
When it is one player only
If everyone except one friend can join, the issue is on their side: verify game files in Steam, restart Steam, disable VPNs and check their firewall. Very high ping can also trip the connection, which is where choosing a location close to your players helps.

A server that just stays reachable
On a GamezServers Ground Branch server the ports are already open on its own address, automatic updates run on restart so a patch only needs a restart from the panel, and a Validate Server Files option repairs a broken install after a bad update: turn it on for one restart, then off again. The live console shows the startup log as it happens, so you can see a broken map line straight away.
FAQ
Why is my Ground Branch server not in the server list?
Usually the query port (UDP 27015) is closed, or the server is on an older build after a game update. Open the port and update the server.
Which ports does a Ground Branch server need?
UDP 7777 for the game and UDP 27015 for queries by default. Both must be forwarded for public play.
Why did my server vanish after a game patch?
Players updated and the server did not. Run the SteamCMD update with validate and restart.
Can players join a Ground Branch server that is not listed?
Rarely in practice. Fix the query port so the browser can see it, since that is how players join.
Skip the setup. Your own Ground Branch server.
Then $14.99/mo. Just trying it? $3.75 for 3 days