Garry's Mod Server Connection Troubleshooting: Retrieving Server Info and NAT

Garry's Mod Guide • Updated Sep 17, 2026

Garry's Mod Server Connection Troubleshooting

“Retrieving server info” can mean an unreachable server, a LAN flag applied too late, a missing GSLT/browser registration, or a Workshop download that never completes. Test those boundaries in order instead of reinstalling the client or changing every port at once.

Last verified: September 1, 2026. The Facepunch dedicated-server guide and command-line reference are the source for app 4020, startup flags, GSLT, and sv_lan behavior.

Fast triage

Symptom	Boundary to test	First action
“Retrieving server info” never ends	Reachability or startup state	Boot a stock map with no addons and try direct `connect IP:PORT`.
Local clients join; internet clients do not	NAT/firewall/host network	Test from a second network and verify the configured port reaches the host.
Server works by direct connect but not browser	Registration/GSLT metadata	Check the GSLT, truthful server info, and public startup mode.
Join stalls while downloading	Workshop/client content	Use the Workshop download checklist.
LAN server appears public or vice versa	`sv_lan` timing	Set it at startup or follow it with `changelevel`; server.cfg alone can be too late.

1. Prove the server boots

./srcds_run -game garrysmod -console \
  +maxplayers 4 +gamemode sandbox \
  +map gm_construct -port 27015 \
  -noaddons -noworkshop

Keep the console open and wait for the map to load. If this fails, fix SteamCMD app 4020, missing libraries, the map, or the x86-64 branch before looking at client networking.

2. Test direct connect

On the client, open the console and run:

connect YOUR_SERVER_IP:27015

Use the actual port from the startup command. Direct connect bypasses some browser-discovery assumptions and tells you whether the server is reachable at all. If local works but a friend on another network fails, focus on the host firewall/NAT boundary rather than reinstalling GMod.

3. Check `sv_lan` and browser registration

For LAN-only testing, set +sv_lan 1 before startup.
For an internet server, keep LAN mode off and use the correct public startup settings.
If you changed sv_lan after boot, run changelevel gm_construct and retest.
For public listing, verify the GSLT and truthful hostname, gamemode, and map. Facepunch's operator rules prohibit misleading server information.

4. Isolate Workshop and gamemode content

A stock map with -noaddons -noworkshop is the clean comparison. If it joins, re-enable the collection, then the custom map/gamemode, one change at a time. A client that reaches the server but hangs while downloading belongs in the Workshop addons guide, not the port-forwarding section.

5. Record evidence

SteamCMD/app 4020 output and server branch.
Startup command, map, gamemode, player slot count, and whether GSLT is present (never share the token).
Client console line where it stops and server console lines at the same time.
Whether local, direct external, and browser joins differ.
Workshop collection ID and whether the failure disappears with -noworkshop.

Related Garry's Mod guides

Want the network, process, and Workshop directory managed together? Use managed Garry's Mod hosting and keep this checklist for client-side diagnosis.

Tired of fighting this issue every patch?

Run a managed Garry's Mod server with us. We handle the patches, mod-version pinning, save backups, and DDoS protection. Set up in minutes, multiple datacenter regions, no contract.

See Garry's Mod hosting plans →

← Back to Garry's Mod Guides

Menu

Garry's Mod Server Connection Troubleshooting: Retrieving Server Info and NAT