Game server not showing in the server browser? How to fix it
Fix a Source, Rust or ARK server on Schokr that players can't find in the in-game browser: tokens, LAN settings, query ports and direct connect.
Updated · 2 min read
If your server is running but doesn't appear in the in-game browser, check that it's not in LAN mode, that it has a valid Steam token where the game needs one, and that its query port is set correctly. While you fix it, players can always join by direct connect.
First, try direct connect
Direct connect skips the browser entirely, so it tells you whether the server itself is reachable.
| Game | Command |
|---|---|
| CS:GO, TF2, Garry's Mod, other Source games | connect <server-ip>:<port> in the developer console |
| Rust | client.connect <server-ip>:<port> in the F1 console |
| ARK | Join via the Steam server list's Favourites, using <server-ip> and the query port |
If direct connect works, the server is fine and only the listing is the problem. If it doesn't, check the server has actually finished starting in the console.
Source games (CS:GO, TF2, Garry's Mod)
- Check
sv_lan. It must be0inserver.cfg. Withsv_lan 1, the server only accepts local players. - Check the Steam token. CS:GO needs a valid GSLT for App ID 730 to be listed and accept internet players. Look for a Steam login failure in the console at startup. See getting a GSLT.
- Don't reuse a token. One token on two running servers kicks one of them off Steam.
- Check filters. The browser hides password-protected, full or high-ping servers depending on the player's filters, and Garry's Mod groups servers by gamemode.
- Wait a few minutes. Listing on Steam's master server isn't instant.
Rust
- New servers can take a while to appear in the Community tab.
- Servers running Oxide/uMod plugins are listed under the Modded tab, not Community.
- If the server uses a separate query port, it must match a port allocated to the server. See adding port allocations.
- Search for your exact server name and turn off filters.
ARK: Survival Evolved
ARK relies on its query port for the Steam browser. The query port must be set in your Startup settings to a port allocated to the server. Without it, the server often won't show up even though it's running. Also check:
- Players are searching the right category (Unofficial) and have "Show password protected servers" ticked if you set a password.
- The session name matches what you're searching for.
Adding the server to Steam's own server list is a reliable workaround: in Steam, open View, then Game Servers, go to Favourites, and add <server-ip>:<query-port>.
Still not showing?
- Restart the server and wait five minutes.
- Check the console for errors about ports already in use. A mismatched port in a startup variable is a common cause.
- Make sure players are on the right game version. For example, CS:GO servers need players on the legacy CS:GO client, not Counter-Strike 2.
Still stuck?
Share your server's startup log in the Schokr Discord and someone can help spot the problem.