How to Fix Garry’s Mod Server Lag and Connection Problems (2026 Troubleshooting Guide)

Garry’s Mod lag is not one problem. A server that simulates slowly, a player with packet loss, a broken server-browser query, an outdated build, missing Workshop files and a blocked port can all look like “lag.” Start by identifying which symptom affects whom, then test the connection path before changing tickrate or removing addons. The sequence below isolates client routing, browser discovery, server CPU work, addon networking, content, versions and firewall configuration without treating a ping problem as a server-performance problem.

What kind of Garry’s Mod lag or connection failure are you seeing?

Use the scope of the symptom as your first diagnostic. If every player sees delayed doors, weapons, NPCs or player movement, investigate server simulation and addon workload. If only one player rubber-bands while others are fine, investigate that player’s route, Wi-Fi, packet loss or firewall. A blank browser, “connection failed after retries,” “server is out of date,” and checkerboard textures are different failure classes and need different fixes.

Symptom	Most likely layer	First useful test
Everyone experiences delayed simulation	Server CPU, gamemode or addon work; possibly a low server tick	Watch server performance and test with addons disabled or on a clean map
One player has high ping or rubber-banding	That player’s route, Wi-Fi, packet loss or local firewall	Try a wired connection and compare with another server
Internet tab shows no servers	Garry’s Mod browser filters, local firewall or query path	Restore default filters, refresh, then use a direct connect test
“Connection failed after retries”	Unreachable address, wrong port, firewall/router block or a server that is offline	Connect directly to a known address and verify the configured port
“Server is out of date”	Client/server version mismatch	Update the server; a client cannot downgrade to an older server build
Checkerboards or ERROR models	Missing mounted game files or Workshop content	Install or mount the content required by the map and addons

These categories can overlap. For example, an overloaded addon may make everyone freeze while a separate firewall issue prevents a new player from joining. Record who is affected, when it starts, whether the console reports packet loss or retries, and whether the problem occurs on a second server.

How do I tell whether the server or my Internet connection is lagging?

Compare the experience of multiple players and separate simulation delay from network delay. Server tickrate and CPU workload determine how quickly the game world advances; Internet ping determines how long packets take to travel between a client and server. Raising a tickrate cannot repair a congested Wi-Fi link, and changing DNS cannot make an overloaded gamemode simulate faster.

Signs of server-side simulation trouble

• Most or all players report the same delayed actions at the same time.
• NPCs, physics objects and scripted entities update late even for players with different Internet providers.
• The problem follows the server or gamemode rather than one player’s location.

Signs of a client route or packet-loss problem

• Only one player freezes, rubber-bands or sees ping spikes.
• Other players continue normally and the issue changes when the player joins a different server.
• Switching from Wi-Fi to Ethernet, or removing a local firewall block, changes the result.

Signs of discovery or reachability trouble

• The browser is empty, but you have a known server address.
• A direct connection fails before the server presents its join screen.
• Friends outside the host’s local network cannot join while the host can.

How can I fix a blank Garry’s Mod server browser?

Facepunch Support identifies an empty in-game browser as a common Source-engine multiplayer problem. Restore the browser’s defaults, refresh the Internet list, and then test a known address manually. The direct test tells you whether discovery is broken or the server is unreachable.

1. Open the Garry’s Mod server browser and restore its default filters. Remove restrictive map, mode, region, password and player-count filters that could hide every result.
2. Refresh the Internet tab and wait for the list to repopulate. A temporary query delay can make an otherwise healthy browser appear empty.
3. Open the developer console and run connect <ip>:<port> for a known server. Include the port when it is not the default.
4. Compare the result with the Steam Server Browser or another Source game’s browser. If those list servers while Garry’s Mod does not, focus on Garry’s Mod’s browser handling or a local firewall rule.
5. If the direct command also fails, check that the server is running, the address is current, and the configured port is allowed through the host and router.

A working direct connection with an empty browser is a discovery problem, not proof that the server itself is lagging. Conversely, a failed direct connection points to a nonexistent server, an incorrect address or port, or firewall/network blocking.

What should I do when Garry’s Mod says “connection failed after retries”?

First determine whether the failure is local to one player or affects everyone outside the host. A retry error means the client did not complete a usable connection; it does not identify the cause by itself.

For a server you do not operate

1. Confirm the address and port with the administrator and try connect <ip>:<port> instead of the browser entry.
2. Join a different server. If other servers work, the original server may be offline, full, filtering your region, or blocking your route.
3. Try a wired connection if you are on Wi-Fi, then temporarily check whether local security software is blocking Garry’s Mod or Steam networking.
4. Verify Garry’s Mod files in Steam if failures persist across servers. File verification cannot fix a remote server that is down, but it can replace damaged client files.

For an operator’s own server

1. Test from the host itself using the server’s local address, then from a device on the same LAN, and finally from an external network. The point at which it fails identifies the boundary.
2. Confirm the process is listening on the intended port and that the router forwards that same port to the correct machine.
3. Allow the server through the host firewall for both TCP and UDP, and check that an upstream firewall or carrier-grade NAT is not preventing inbound traffic.
4. Give players the public address, not a private LAN address such as 192.168.x.x or 10.x.x.x.

How does tickrate affect Garry’s Mod server lag?

Garry’s Mod documents a default tickrate of 66.6666, which is approximately one simulation tick every 15 milliseconds. The documented -tickrate target range is 30–128. Tickrate is a CPU-and-gamemode budget, not a universal lag cure: increasing it asks the server to perform simulation work more often and can worsen stutter when the host is already CPU-bound.

Change	What it can improve	What it cannot improve	Risk
Keep the default 66.6666	A balanced baseline for many gamemodes	Packet loss, blocked ports or oversized addon messages	Heavy scripts can still miss the budget
Lower the target toward 30	CPU headroom on a constrained host	A player’s Internet route or missing content	Less frequent simulation updates and a less responsive feel
Raise the target toward 128	Potentially finer update cadence when CPU capacity is available	Network reachability and client-side lag	More CPU work; can create worse stalls if the gamemode cannot keep up

Change the setting only after measuring the symptom. Compare a clean server and the production gamemode, watch CPU utilization and tick performance, and change one variable at a time. There is no published universal player-count, processor or bandwidth threshold that guarantees a “lag-free” server; the practical limit depends on the specific gamemode, addon set and host.

How can addons cause freezes, lag and disconnects?

Addon networking is a frequent cause of failures that look like ordinary latency. Garry’s Mod’s networking documentation sets a maximum net message size of 64 KB and describes a reliable-buffer overflow threshold of roughly 256 KB. A single oversized message, or several bursts arriving before clients can process them, can freeze a client or disconnect it.

Reduce oversized net messages

• Do not send large tables, inventories, map data or serialized objects in one message. Split data into bounded chunks.
• Send only the fields the recipient needs. Compressing or delta-encoding data can reduce payload size, but still enforce a hard per-message limit.
• Validate lengths on both server and client so a malformed or unexpectedly large payload is rejected rather than queued.

Spread updates over time

• Replace “send to everyone on every event” with targeted recipient lists where possible.
• Queue non-urgent updates and release them over several ticks instead of creating a burst.
• Throttle HUD, scoreboard, position-adjacent and inventory updates; these are often sent far more frequently than players can perceive.

The reliable channel is documented at approximately 120 KB/s, with the exact usable bandwidth varying by client. Designing below the theoretical maximum leaves room for other traffic and prevents a temporary burst from filling the reliable queue.

Why do NW and NW2 variables create recurring traffic?

Standard SetNW* and SetGlobal* values are re-networked every 10 seconds. The NW string table has 4,095 slots; NW2 has a separate 4,095-slot table and uses PVS-based delivery. Excessive keys and frequent value changes therefore create recurring traffic and can consume table capacity even when the values appear small.

Audit NW usage

1. List every key created by the gamemode and addons, including global keys and keys on frequently spawned entities.
2. Remove keys that duplicate data already available client-side or that are read only once.
3. Set a value only when it changes. Avoid writing the same value every tick or on every Think hook.
4. Use the narrower recipient scope available to the feature; a local HUD state does not need to be broadcast globally.
5. Watch for key churn during map changes and round restarts, when repeated entity creation can consume table slots quickly.

NW2’s PVS behavior can reduce delivery to clients who cannot see an entity, but it does not remove the need to control key count and update frequency. If an addon approaches the 4,095-key limit, redesign its data model rather than adding more abbreviated names.

How do I update and validate a dedicated server?

Operators should update the server before changing client settings. SteamCMD identifies Garry’s Mod with app ID 4020; the validation command checks that installed files match the current depot.

1. Stop the server cleanly so files are not being written while SteamCMD updates them.
2. Start SteamCMD and log in with the account and credentials appropriate for your server setup.
3. Run app_update 4020 validate. The validate option checks and reacquires damaged or missing files.
4. Update the server’s Workshop collection and confirm that every required addon is available to the account and mounted by the startup configuration.
5. Restart the server and test a direct connection before inviting players. Read the console for missing depots, failed Workshop downloads or Lua errors.

The official dedicated-server setup also requires a Game Server Login Token (GSLT) for authenticated public operation and documents startup parameters, Workshop collections and Linux 32-bit-library requirements. Match those prerequisites to the operating system and launch script rather than copying options from an unrelated game server.

How do I fix “server is out of date” and missing-content errors?

“Server is out of date” is a version-state problem. The operator must update the server; a player cannot solve the mismatch by changing ping settings or by forcing a client downgrade.

Version mismatch procedure

1. Have the operator run the SteamCMD update and validation command, then restart the server.
2. Close and restart Steam on the client so it can apply any pending Garry’s Mod update.
3. Check that the server is not launching an old installation directory or an obsolete branch.

Checkerboards, ERROR signs and invisible models

These symptoms usually mean the server or client lacks a mounted game, map dependency or Workshop addon. Identify the exact asset named in the console, install the required game content, and ensure the server mounts it in its configuration. For Workshop content, verify the collection ID, download permissions and that the addon actually finished downloading before the map loads. Removing an addon that supplies required materials can replace a visible error with missing gameplay, so fix the dependency instead of deleting files at random.

Which ports and firewall rules must a Garry’s Mod server use?

Port advice must match the server’s actual configuration. A dated Steam Community guide commonly recommends forwarding 27005–27015 and allowing both TCP and UDP, but that range is a starting point rather than a guarantee. Read the launch configuration, confirm the listening port, and forward only the port the process uses unless another service requires additional ports.

1. Set or confirm the server port in the launch command or configuration.
2. Create a router rule forwarding that external port to the server’s fixed internal IP address.
3. Allow inbound and outbound traffic for the server executable on both TCP and UDP in the host firewall.
4. Check that the router’s WAN address is publicly routable. Carrier-grade NAT or a second router can prevent inbound connections even when local rules are correct.
5. Restart the server and test from a different Internet connection; a test from the same LAN may succeed because of local routing while public players remain blocked.

Do not assume that opening every port solves a retry error. An incorrect address, a stopped process, a stale DNS record or a provider-level firewall can produce the same message.

Can a wired connection fix a laggy Garry’s Mod client?

A wired connection is a useful diagnostic for Wi-Fi instability, not a remedy for server CPU overload, tickrate choices or addon-networking bugs. A Steam Community troubleshooting discussion suggests trying a cable alongside file verification and firewall checks. Connect the affected computer directly to the router with a Cat6 Ethernet cable, restart the game, and compare ping and packet loss on the same server.

• If the problem disappears on Ethernet, investigate Wi-Fi interference, signal strength, channel congestion, power-saving behavior and competing traffic.
• If the problem remains identical, the cause is more likely the server, Internet route, firewall, version or content.
• If only one game is affected, compare another Source game or a non-Steam network application before replacing hardware.

What is the fastest diagnostic order for an operator?

Use reversible tests first and reserve persistent configuration changes for a confirmed cause.

1. Classify the scope: ask whether everyone or one player is affected, and record the exact error text.
2. Test reachability: restore browser filters, refresh, then run connect <ip>:<port>. Compare the in-game and Steam browsers.
3. Test a clean baseline: run the same map or gamemode with nonessential addons disabled. If the lag vanishes, re-enable addons in groups until the trigger is found.
4. Measure simulation: compare the default 66.6666 tickrate with the documented range only when CPU or tick budget is the suspected bottleneck.
5. Inspect networking: audit net message sizes, burst frequency, reliable-channel queues and NW/NW2 key churn.
6. Update state: run app_update 4020 validate, restart, and check Workshop downloads and mounted games.
7. Verify public access: confirm the real port, TCP/UDP firewall rules, router forwarding and external testing.
8. Retest one change at a time: keep a short log of the setting, test server, players affected and result so a temporary improvement is not mistaken for a fix.

Intervention	Scope	Layer	Reversible?	Evidence strength	Typical cost
Direct connect test	One client or browser path	Discovery/reachability	Yes	Official support procedure	Free
Ethernet comparison	One client	Local network	Yes	Community troubleshooting advice	Existing cable or accessory purchase
Addon disable-and-retest	All players on that server	Lua and networking	Yes	Controlled diagnostic	Free
Tickrate change	All players	Server simulation	Yes, if documented in launch settings	Official tickrate documentation	Free, but may require more CPU
Router/firewall rule change	All external players	Reachability	Yes	Configuration-dependent	Free; hardware or provider limits may apply
Managed hosting migration	All players	CPU, network and operations	No, until migrated back	Depends on provider’s published plan and policy	Recurring hosting fee

How should I choose hosting when the current machine cannot keep up?

Move hosts only after confirming that the bottleneck is the machine or its network policy. When comparing managed Garry’s Mod hosting, ask for the actual CPU allocation or single-thread performance, network capacity, DDoS policy, geographic region, Workshop support, backup policy, mod access and current price. A larger advertised player slot count is not a performance specification.

• CPU allocation: Garry’s Mod gamemodes and Lua scripts can be sensitive to per-core performance; shared “vCPU” language may not tell you how much sustained time is available.
• Network and region: Choose a location near most players and confirm whether traffic is filtered or rate-limited.
• Workshop and mod access: Verify that you can set collections, mount required games, edit launch parameters and inspect logs.
• Backups and recovery: Ask whether backups include maps, Lua files, configuration and database data, and how quickly a restore can be performed.
• Security policy: Understand DDoS mitigation limits, exposed ports and what support will troubleshoot.

No provider can guarantee a universal lag-free player count without profiling the exact gamemode and addon set. Preserve a copy of the validated configuration and test the same workload after migration.

What should I check before reopening the server?

• All players can join by direct address, and the browser listing is not being mistaken for reachability.
• The server and clients are on compatible current versions.
• Required maps, mounted games and Workshop addons download without errors.
• Nonessential addons are re-enabled gradually, with network-heavy features tested under real player load.
• net messages stay below 64 KB, bursts are paced, and reliable traffic has headroom below the roughly 256 KB overflow threshold.
• NW and NW2 keys are bounded, changed only when needed and not recreated every tick.
• The selected tickrate is supported by measured CPU capacity rather than chosen as a generic “lag fix.”
• The configured port, router forwarding and TCP/UDP firewall rules agree, and an external connection test succeeds.
• A rollback copy exists for the launch command, addon list and server files.

Frequently Asked Questions

Why is my Garry’s Mod ping high only on one server?

The route to that server may be longer or congested even when your local connection is healthy. Compare the same client on several servers, note whether other players see the issue, and ask the affected server’s operator about its region and upstream network.

Can changing DNS stop Garry’s Mod server lag?

DNS can affect how quickly a hostname resolves, but it does not lower in-game latency after the connection is established. It will not fix server tick delays, packet loss, oversized network messages or blocked ports.

Why do I download addons every time I join a Garry’s Mod server?

The server may be using a Workshop collection that is not installed locally, or its collection and mounted-content configuration may be changing. Let the download finish, restart Steam if subscriptions are stuck, and have the operator verify collection IDs and addon availability.

Why can the host join but nobody outside the house can?

Local access proves the server process is running but not that it is publicly reachable. Check the server’s listening port, forward that port to the host’s fixed LAN address, allow TCP and UDP through the firewall, and rule out carrier-grade NAT or a second router.