Most Sons of the Forest server problems become easier to fix once you identify the failing layer. Rubber-banding and delayed actions usually indicate high latency or an overloaded host; a server that does not appear in the browser points to query traffic or public discovery; an immediate timeout usually involves gameplay traffic; and a join that hangs while the island loads often involves BlobSync or a problematic save. Check those paths in that order, then verify the dedicated server’s build, JSON configuration, firewall, NAT, password, and player limit.
How can I tell whether the problem is lag, a bad connection, or a server failure?
Start by asking whether the symptom affects everyone or only one player. If every player sees delayed interactions, teleporting enemies, or repeated rubber-banding, investigate the server host, its Internet connection, and the route to the server. If one player is affected while the others play normally, begin with that player’s Wi-Fi, VPN, firewall or antivirus, background traffic, and local game files.
Latency is the time information takes to travel between a player and the server. Higher latency increases the likelihood of lag, while an unstable connection can produce short bursts of loss that feel like freezes or rubber-banding. A server can also be reachable yet too busy to process simulation and saves promptly, so “the server is online” does not prove that its hardware or connection is healthy.
Use a controlled first test
- Have one affected player test with a direct Ethernet connection instead of Wi-Fi. Wireless and powerline links can suffer interference; changing to a wired link without changing anything else is a useful comparison.
- Stop downloads, cloud synchronization, video uploads, and other bandwidth-heavy programs on both the server network and the test player’s network.
- Ask whether the issue began after a game update, a dedicated-server update, a configuration edit, or loading a particular save.
- Record the exact symptom, who is affected, the time it occurs, and the last useful line in the server console or log. This prevents unrelated fixes from being mixed together.
If the wired test fixes one player’s problem, repair that player’s local network or security software before changing server settings. If everyone is affected, continue with the server and port checks below.
Which UDP ports does a Sons of the Forest dedicated server need?
A documented dedicated server uses three separate UDP paths. Check the active dedicatedserver.cfg rather than assuming the defaults, because a custom value must be allowed and forwarded instead of the default.
| Default UDP port | Config name | What it carries | Typical symptom when blocked |
|---|---|---|---|
| 8766 | GamePort |
Gameplay traffic during an active session | Immediate timeout, failed join, or severe in-game interruption |
| 27016 | QueryPort |
Steam query, browser listing, and discovery traffic | Server does not appear in the browser or cannot be discovered publicly |
| 9700 | BlobSyncPort |
BlobSync data exchange while the world is loading | Join begins but hangs during loading or never reaches the island |
All three entries are UDP, not TCP. Permit them in the host operating system’s firewall. When the server is behind a home router, forward each active UDP port to the server machine’s current private IP address. A forwarding rule aimed at an old DHCP address can look correct while sending traffic to the wrong computer.
The documented defaults are three UDP ports, and the server supports up to eight players. The dedicated-server guide does not publish a universal CPU, memory, or disk requirement. Measure the actual host while the full group is connected and the real save is loaded rather than copying the requirements for the player game.
How do I fix an immediate connection timeout?
An immediate timeout most often means that gameplay traffic on UDP 8766 cannot complete its path. Work from the server outward so you do not mistake a listing problem for a gameplay problem.
- Confirm the process is running. Check the dedicated-server console or service manager and make sure it has finished starting instead of exiting after a configuration error.
- Read the active configuration. Find
GamePortin the user-data directory actually used by the service. If it is not 8766, use the configured value in every firewall and forwarding rule. - Allow the port in the host firewall. Create an inbound UDP rule for the active game port and ensure a security suite is not applying a second block.
- Forward the port to the correct private address. Reserve the server computer’s DHCP address or otherwise keep it stable, then forward UDP 8766 on the router to that address.
- Test from outside the home network. A friend on another connection is a better test than a device on the same Wi-Fi, because some routers cannot reflect a public address back into the LAN.
If the external test still times out, check whether the Internet provider places the router behind carrier-grade NAT (CGNAT) or supplies no usable public IPv4 address. In that situation, a rule on your own router cannot receive an unsolicited inbound connection; you need a provider option that supplies reachability or a managed server in a network that accepts the traffic.
Why is my server missing from the Sons of the Forest browser?
A missing listing is primarily a discovery problem, not proof that gameplay traffic is broken. Check UDP 27016, the public-server setting, and the address visible from the Internet.
- Verify that
QueryPortis 27016 or note the custom value in the active JSON file. - Allow and forward that UDP port exactly as you did for the game port.
- Set
LanOnlytofalsefor Internet players. A value oftrueintentionally restricts the server to the local network. - Confirm that the advertised public address belongs to the router or host that receives the forwarding rule, not a private address such as 192.168.x.x.
- Test from an external network. A server may be healthy on the LAN while public discovery fails because of CGNAT, an upstream modem, or a provider firewall.
Players on the same LAN can have a different experience from Internet players. If the router lacks NAT loopback (hairpin NAT), a local player may need to connect using the host computer’s private IP while remote players use the public address. That distinction does not repair public access; it only avoids the router’s inability to loop a local request through its public address.
What should I do when joining starts but the server stays on the loading screen?
A loading hang points first to UDP 9700, the BlobSync path used while the world is transferred and initialized. It can also be a save-loading problem, so do not repeatedly overwrite the only copy of the world while testing.
- Read
BlobSyncPortin the active configuration and allow and forward its UDP value (9700 by default). - Watch the server console while a player joins. Wait for the island and save to finish loading; a long initial load is not the same as a network timeout.
- Try a different save slot or a known-good save. If another save loads normally, the failure is probably specific to the original save rather than to all three network paths.
- Back up the active user-data directory and saves before changing
SaveMode, replacing files, or performing recovery work. - If every save hangs, return to the firewall, forwarding, and build checks instead of treating one world as corrupt.
A loading failure can therefore have two independent causes: blocked BlobSync traffic and a save that cannot complete initialization. Test them separately and keep the original data untouched until you know which branch you are addressing.
How do I fix connection failures that began after a patch?
The dedicated server is a separate SteamCMD application, app ID 2465200. Updating the game client does not automatically update that headless server.
- Stop the dedicated-server process cleanly.
- Use SteamCMD to update app
2465200. - Start the server again and allow it to complete initialization.
- Confirm that every player is on a compatible client build and that nobody is on an unmatched beta branch.
- Retest one player before inviting the whole group.
A newer client cannot join an older dedicated server reliably. If everyone is rejected immediately after an update, establish version parity before changing router rules or deleting saves. Restarting after the update also ensures that the process is not still using files loaded by the previous build.
Why can only one friend not join?
When the rest of the group can play, the server’s basic reachability is already demonstrated. Have the affected player restart Steam, verify the game files, temporarily test without a VPN, and inspect local firewall and antivirus rules. Their Wi-Fi path or security software can fail while the server and other clients remain healthy.
Ask that player to try a direct wired connection and to close bandwidth-heavy applications for one session. If the problem follows the player to another network, keep investigating the local client and account environment. If the same player succeeds elsewhere but fails only from one home connection, the home router, ISP filtering, or local NAT is more likely than the dedicated server.
How do I repair a server that will not start after editing the config?
dedicatedserver.cfg is strict JSON. One missing quote, comma, or brace can prevent startup, and editing a file that the service does not actually read produces no useful change.
- Validate the file as JSON and remove comments or trailing commas that a strict parser rejects.
- Confirm the service’s user-data path and edit the configuration in that active directory, not a similarly named installation folder.
- Check that every configured port is numeric and that no other process already occupies it.
- Restore the last known-good backup if the service still exits, then make one change at a time.
- Read the first configuration or bind error in the console; later messages may only be consequences of the initial failure.
Do not change several settings at once. A one-variable edit makes it possible to identify whether the parser, the port binding, or the network policy caused the startup failure.
How do NAT, the accessibility test, and LanOnly affect connections?
The server performs a network-accessibility check during startup. A router without NAT loopback can make that self-test fail even when forwarding works for players outside the home. Setting SkipNetworkAccessibilityTest to true allows the process to start without that diagnostic, but it does not make an unreachable server reachable.
Use LanOnly: true only when every player is on the local network. For Internet play, set LanOnly: false, forward the three active UDP ports, and verify the public address from an outside connection. If the home router is behind another modem/router, both layers may need forwarding, or the upstream device must be placed in bridge mode. CGNAT is different: there is no inbound mapping to configure on the customer router, so a provider change or managed host is required.
Could a password or player limit reject a healthy connection?
Yes. Password and capacity checks happen after basic networking, so a working port does not guarantee admission.
- Passwords are case-sensitive. Re-enter the exact value and remove accidental spaces when testing.
- The documented ceiling is eight players. A lower
MaxPlayersvalue intentionally rejects the next player even when the server and network are healthy. - Check the active configuration rather than a template file; only the file loaded by the running service controls the session.
If the first players can join but the next one is refused, compare the current player count with MaxPlayers before touching firewall rules.
How can server performance cause rubber-banding?
Network latency is not the only source of delayed movement. A host that cannot process simulation, networking, and saves promptly can make every player see pauses even with low Internet latency. Monitor CPU and memory while the full group is connected and while the actual save is active; there is no published universal hardware requirement for the headless server.
| Setting | Documented behavior | What to watch |
|---|---|---|
ActiveTargetFramerate |
Default target of 60 while occupied | Whether the host can sustain the target with the full group |
IdleTargetFramerate |
Default target of 5 while empty | Whether the server recovers normally when players return |
SaveInterval |
Default interval of 600 seconds | CPU, disk activity, and pauses around save operations |
These controls describe server timing; they are not a substitute for reachable ports or a stable route. If lag appears only during saves, observe disk and CPU activity at that moment and preserve the world before experimenting with save-related settings.
What is the safest way to troubleshoot a possibly damaged save?
Copy the active user-data directory and save files before every recovery attempt. Keep the backup outside the live directory so an automatic save cannot overwrite it. Then load an alternate or fresh slot once. A normal load there narrows the issue to the original world; a failure across all slots points back to networking, version compatibility, configuration, or host performance.
Do not infer corruption from a long first load alone. Watch the console for progress, allow sufficient time for the island to initialize, and compare the result with a second save. Only after the comparison should you consider changing SaveMode or replacing files, and keep the untouched backup available for rollback.
What order should I use for a complete fix?
The following sequence minimizes wasted changes and preserves evidence.
- Record who is affected, the exact symptom, the last console or log line, and whether the issue follows an update or configuration edit.
- Check Steam service status, test one player on a wired connection, and close bandwidth-heavy background applications.
- Confirm that the server process is running and that the active configuration parses as strict JSON.
- Update SteamCMD app
2465200, restart the server, and confirm compatible client and server builds. - Compare the active values for
GamePort,QueryPort, andBlobSyncPortwith host-firewall and router/provider rules. Allow and forward all three UDP paths. - Check
LanOnly, the public address, the case-sensitive password, andMaxPlayers. - Wait for the save to finish loading. If only one save fails, stop and protect the data before recovery work.
- If the home network uses CGNAT or cannot accept inbound forwarding, decide whether a managed server is more practical than changing the connection.
Retest after each stage with one player. When the symptom changes—for example, from “not listed” to “loading”—you have identified a layer that is now working and can focus on the next one.
Should I self-host or use managed hosting?
Self-hosting is viable when you control a reachable public connection and are comfortable maintaining the process. Managed hosting can remove home-router exposure and CGNAT obstacles, but it does not eliminate version, configuration, log, performance, or backup responsibilities.
| Decision factor | Self-hosting | Managed hosting |
|---|---|---|
| Reachability | Requires public IPv4 or equivalent inbound access, correct NAT, and UDP forwarding | Provider supplies the network path; verify that the service supports the required UDP ports |
| Control | Direct access to the Windows process, JSON configuration, logs, and saves | Control depends on the provider’s panel and file access |
| Maintenance | You perform SteamCMD updates, restarts, firewall edits, and backups | Some operations may be managed, but confirm who handles updates and backups |
| Latency | Depends on the host’s physical region, ISP route, and local load | Choose a region close to most players and verify the route during a real session |
| Cost and effort | Uses an existing computer and connection but requires administration | Adds recurring cost in exchange for less home-network administration |
Before migrating, copy saves and document the active JSON values. After deployment, test listing, joining, loading, and saving with one player before inviting the whole group. A provider that hides logs or prevents backups can make future troubleshooting harder even when the initial connection works.
When should I stop changing settings and escalate?
Escalate after you have recorded the build numbers, active port values, exact symptom, console error, NAT arrangement, and whether an external player can reach the server. That evidence lets a host, Internet provider, or game support team distinguish a blocked path from a parser error or save-specific failure.
Do not leave SkipNetworkAccessibilityTest: true enabled as a supposed fix, do not expose extra ports beyond those required by the active configuration, and do not discard the only copy of a save while testing. A reachable, version-matched server with correct UDP rules and a protected save gives you a stable baseline for any remaining fault.
Frequently Asked Questions
Does changing SaveInterval stop rubber-banding?
Not by itself. The documented default is 600 seconds, and changing the interval only changes how often saves are scheduled; it cannot repair blocked UDP traffic, high latency, or an overloaded host. Observe whether pauses coincide with saves, then back up the world before experimenting.
Is a Cat6 Ethernet cable required to fix lag?
No. The useful test is any reliable direct wired connection, because it removes Wi-Fi or powerline interference from the comparison. Cat6 is a practical cable choice, not a documented Sons of the Forest server requirement.
Why can the server accessibility test fail even when a friend can join?
Some home routers do not support NAT loopback, so a local self-test cannot reach the public address from inside the same network. An external player’s successful join is stronger evidence of Internet reachability than that local diagnostic alone.
What information should I include when asking for technical support?
Include the client and dedicated-server build numbers, the exact UTC time of a failed join, the symptom (timeout, missing listing, or loading hang), the active UDP port values, the last console line, and whether the test was performed from outside the host’s LAN. Mention any CGNAT or double-router arrangement and whether another save loads normally.