Fixing Insurgency: Sandstorm connection trouble starts with identifying the symptom. High ping, rubber-banding and packet loss that hit several players point to a network route or server incident; low or erratic FPS on one computer is a local performance problem; a missing server, join timeout or endless “Preparing Server” screen usually involves discovery, ports, versions or mods. Use the matching branch below instead of changing graphics settings for a server outage or forwarding ports for a single-PC frame-rate issue.
Work from the least destructive checks first. Test another server, remove competing bandwidth use, verify firewall and DNS behavior, synchronize your clock, and confirm an Open/Type 1 NAT where your platform supports it. Server owners should then inspect startup logs, query-port forwarding, version parity, map settings and mod authentication before reinstalling anything.
What kind of Insurgency: Sandstorm problem are you seeing?
The symptom determines the right fix. A useful first test is whether another player on the same server sees the problem and whether a different server or region behaves normally.
High ping, rubber-banding or packet loss
When characters snap backward, inputs arrive late, or several people freeze together, treat the issue as network or server lag. The fault may be your home link, an Internet-service-provider route, the server host, or a regional service incident. Saber Interactive currently lists connection and packet-loss instability as a known issue across server regions, so a local tweak cannot repair every outage.
Low FPS, stutter or a crash on one machine
If only your computer stutters while other players remain responsive, investigate rendering performance, drivers, background software and file integrity. Saber separates these local performance symptoms from online connection faults.
Server missing from the browser, join timeout or “Preparing Server” stall
A server that does not appear, times out while joining, or hangs at “Preparing Server” needs a discovery and startup diagnosis. Query-port forwarding, browser filters, a stopped process, version mismatch, map configuration and mod authentication are the common branches.
What should I check first when everyone is lagging?
- Compare players and servers. Ask another player whether the same delay or packet loss is visible. Join a different server, preferably in another region. If the whole group is affected on one region or server, check Saber’s current known-issues information before changing local settings.
- Measure the local link. Pause downloads, cloud synchronization, video streams, game updates and other heavy traffic. Steam’s lag guidance specifically calls out server latency, background applications and router conditions.
- Check for a service or route problem. A wired test, a different region and a short test at another time help separate your home network from an ISP route or remote incident. A wired connection cannot fix a distant outage, but it is a useful isolation step.
Do not confuse a high in-game ping with low FPS. Ping is the time for traffic to travel to the server and back; FPS is how quickly your computer renders frames. They can occur together, but they require different fixes.
How do I fix high ping, packet loss and rubber-banding as a player?
Remove competing traffic
Stop or schedule large downloads and uploads on every device sharing the connection. Close launchers, browser streams, backup tools and voice or capture applications that are consuming bandwidth. Retest the same server after the link is quiet; if only that server remains bad, the route or server is more suspect than your connection.
Test Ethernet when Wi-Fi is questionable
Connect the gaming device directly to the router with a Cat6 Ethernet cable and repeat the test. Wi-Fi interference, distance and channel congestion can create variable latency and loss. Ethernet is an isolation test, not a guarantee: it will not repair an ISP route, a remote server or a server-wide incident.
Review firewall and DNS-blocking software
Saber lists firewall rules and DNS blockers as possible causes of connection trouble. Temporarily disable a third-party DNS filter only long enough to test, or allow the game and platform services through it. Restore protection after the test and create a specific allow rule rather than leaving a firewall disabled.
Synchronize the platform clock
On Windows, open Settings > Time & language > Date & time, enable automatic time if it is available, and select Sync now. Saber includes clock synchronization in its connection checklist because a badly skewed clock can interfere with authentication and service communication.
Use an Open or Type 1 NAT where supported
Saber’s stated target is: “Your NAT Type should be set to Type 1 (Open).” The label differs by platform and router. Look in the console network test or router status page, enable the platform’s supported automatic discovery or forwarding method, and avoid stacking two routers in a way that creates double NAT. Do not expose unrelated services or forward random ports just to change the label.
Retest by region and time
Write down the server region, approximate ping and whether packet loss appears during a match. A problem that follows one region is different from a problem that follows your account or every server. This small record is useful if you need to escalate.
Why is the server not showing, timing out, or stuck on “Preparing Server”?
These symptoms usually involve discovery, startup or compatibility rather than graphics quality. If you own the server, follow the owner checklist below. As a player, perform the filter and version checks first.
Clear browser filters and confirm the community-server view
Reset region, map, mode, password, full-server and empty-server filters. Make sure you are looking at the community-server list when the server is privately hosted. A restrictive filter can make a healthy server appear missing.
Try a direct IP connection
If the owner provides an address, test a direct connection. A successful direct join with no browser listing points toward the Steam query port, listing status or filter settings, not the game-traffic port. A direct timeout indicates a broader process, forwarding, firewall or version problem.
Confirm client and server versions
After an update, compare the player’s main-menu version with the version recorded by the server. Restart or update the server whenever the game client updates. A mismatch commonly causes join rejection or a load that never completes.
Allow time for listing propagation after a restart
A freshly restarted process may not appear immediately. Check that it remains running, wait briefly, then refresh the browser. If it repeatedly disappears, inspect the newest startup log instead of repeatedly restarting without reading the error.
How do I repair an Insurgency: Sandstorm server as the owner?
- Confirm the process and read the newest startup log. Look for fatal errors, a missing map, a failed mod download, an address already in use, or an early process exit. The newest log is more useful than an old configuration backup.
- Verify the actual ports. Common hosting defaults documented by community guides are listed below, but a host can change them. Use the values in the server’s configuration and control panel, then permit those exact values in the host firewall, operating-system firewall and router.
| Purpose | Common documented default | Protocol | What to verify |
|---|---|---|---|
| Game traffic | 27102 | UDP | Forward and allow the configured game port. |
| Steam query and browser listing | 27131 | UDP | Forward and allow the query port used for listing. |
| RCON administration | 27015 | TCP | Allow only if RCON is enabled; protect it with a strong credential. |
Those are common defaults, not universal requirements. Hosts may assign different values, and forwarding the game port while forgetting the query port can produce the classic “direct IP works, browser does not” situation.
- Check listing and filters. Confirm the server is configured as a community server where appropriate, that it is not hidden by a password or capacity filter, and that the query service is reachable. If direct IP works, concentrate on query-port and listing diagnostics.
- Check version parity after every update. Restart the process after updating files. Compare the startup log’s build information with the player’s main-menu version before troubleshooting mods.
- Isolate mods. Temporarily remove
ActiveModsor other mod entries, restart, and test an unmodded map. Failed mod.io downloads, invalid IDs, missing access tokens and a client’s stale authentication state can all block loading or joining. Add mods back one at a time after the clean test succeeds. - Validate maps and configuration placement. Check the exact map and scenario names. PlayNHost’s configuration guidance notes that a wrong map can fall back unexpectedly, Checkpoint has an eight-player limit in the documented setup, and
Game.inivalues can be ignored when they are separated from the section header they belong under. Tokens must also be valid. - Capture evidence before escalating. If instability continues, save the last 50–100 console lines and the relevant startup-log section. Include the configured ports, map, version and mod list so support can reproduce the state.
How do I fix mod.io authentication errors and mod loading failures?
For a common mod.io authentication failure, mod.io’s December 13, 2024 procedure resets the local Windows client settings without requiring a full game reinstall.
- Close Insurgency: Sandstorm.
- Open
%localappdata%InsurgencySavedConfigWindowsClient. - Rename
GameUserSettings.inito a backup name such asGameUserSettings.ini.old. Renaming preserves the original if you need to restore settings. - Restart the game and sign in again through the mod menu.
On a dedicated server, also test with ActiveMods removed. A client reset cannot fix an invalid server-side mod ID, a failed download, an expired access token or a server that cannot reach the mod service. Restore mods gradually and identify the first entry that makes the clean server fail.
Could the problem actually be low FPS or local freezing?
Yes. When only one machine freezes or stutters, use the performance branch rather than changing network settings. Saber’s official performance guidance says its minimum and recommended builds are benchmarked for 60 FPS or above more than 95% of the time in their respective low and medium-high settings targets; the guidance does not state a publication year.
Check the complete system requirement and software baseline
Verify every listed system requirement, including operating-system support, processor, graphics card, memory and available storage. Close overlays, capture tools, hardware-monitoring utilities and other software that may conflict with the game. Compare behavior in another demanding game: if several games stutter, investigate the driver, thermal or hardware layer rather than the server.
Lower the expensive settings first
Reduce resolution scale and demanding effects, then retest in the same location. A stable frame rate with lower settings confirms a rendering limit; it does not explain high ping. Keep a record of the setting changed so you can restore quality one option at a time.
Verify the installation
In Steam, open the game’s library entry, choose Properties, open Installed Files, and select Verify integrity of game files. Let the process finish and allow Steam to reacquire damaged or missing files. Saber recommends verification before a reinstall; reinstall only after system checks, graphics changes, conflicting-software tests and verification fail.
Run the requested diagnostics
If Saber support asks for it, run Windows DxDiag and attach the resulting report. Include whether the symptom is a crash, freeze or low FPS, the graphics settings used and whether another demanding game reproduces it.
What information should I send to support?
A precise escalation packet shortens the back-and-forth. Saber asks for the platform and region, when the problem began, the exact error, reproduction steps and whether other players are affected. Include the in-game KSIVA code and DxDiag when requested. Server owners should attach the relevant startup or console lines, especially the final 50–100 lines around a failure.
- Platform and game version
- Server name, region and whether it is official or community-hosted
- Exact wording of the error or the point at which “Preparing Server” stops
- Time and date, including your time zone
- Whether another server or another player reproduces the issue
- Recent update, configuration, map or mod changes
- For owners: configured game and query ports, startup log, console tail and mod list
Do not include passwords, RCON credentials or private access tokens in a ticket. Redact them from screenshots and configuration files.
Should I change server hosts to solve recurring lag?
Changing hosts is reasonable only after you establish that the process, ports, versions and mods are correct and that the problem follows the server rather than your player base. Compare the operational features that affect real-world stability instead of choosing on headline price alone.
- Location: choose a data-center region close to most players and compare routes from their actual ISPs.
- CPU and RAM allocation: confirm the resources are appropriate for the intended player count, map and mods.
- Network and DDoS protection: ask what mitigation is included and whether it changes latency during an attack.
- Port control: make sure you can set or inspect the game and Steam query ports required by your configuration.
- Mod.io support: verify that mod downloads, authentication and access tokens are supported in the host’s control panel.
- Logs and recovery: require readable startup logs, scheduled restarts, backups and a way to restore a known-good configuration.
- Support and cancellation: check response times, escalation options and cancellation terms before moving a live community.
Current prices, regional performance and promotional terms change frequently. Treat any host list or old benchmark as a starting point and verify those details directly before migrating.
What fixes should I avoid?
- Reinstalling first: a reinstall cannot repair a regional incident, bad routing, a blocked query port or an invalid mod token.
- Forwarding random ports: use the configured values and protocols; unnecessary exposure creates security risk.
- Disabling the firewall permanently: test briefly, then restore protection with a narrow allow rule.
- Deleting configuration without a backup: rename files first so you can recover settings and compare changes.
- Changing graphics for group-wide lag: graphics settings affect rendering on one machine, not other players’ ping.
- Adding every mod back at once: reintroduce mods individually so the failing entry is identifiable.
What should you do first?
Start by deciding whether the symptom is shared network lag, a one-machine FPS problem, or a discovery/timeout failure. Test another server, quiet the local connection, check firewall and DNS behavior, synchronize the clock and confirm an Open/Type 1 NAT. If you run the server, read the newest startup log, verify game and query ports, match versions, then isolate mods and validate map configuration. Keep the exact error, timing and console evidence; that record is more valuable than repeated blind restarts.
Frequently Asked Questions
Can a VPN reduce Insurgency: Sandstorm ping?
A VPN can change the route, but it can also add distance and encryption overhead. Use it only as a controlled comparison: test the same server with and without the VPN, record the route and packet loss, and keep the lower-latency path.
Why can my friends join a server while I cannot?
That pattern points toward your local firewall, DNS filter, NAT or ISP route rather than a server-wide outage. Compare your platform clock, NAT status and network path with a direct Ethernet test, then provide your platform and exact error to support.
How long should I wait for a server to appear after restarting it?
A restarted process may need a short propagation period before the browser lists it. If it still does not appear after refreshing filters, test the direct address and inspect the query-port and startup-log status instead of repeatedly restarting.
Will deleting GameUserSettings.ini remove my mods?
Renaming the file resets local client settings and authentication state; it does not remove the server’s mod configuration. Keep the renamed backup, sign in through the mod menu, and let the client rebuild its settings before testing again.