The Forest: "Server Timeout — Could Not Connect" Fix
If you and a friend can't get into the same The Forest co-op session, the cause is almost always one of five things: a stale Steam state, a stale game version, the host pre-starting the game, port forwarding, or general network. Work through them in order — don't jump to "reinstall the game."
Fix 1: Restart Steam — Both Sides
This is the single most reported fix on Steam community discussions. The Steam game-server backend can get into a bad state where the client times out on connect.
- Close The Forest entirely.
- Right-click the Steam tray icon > Exit Steam. Confirm the Steam process is gone in Task Manager.
- Re-launch Steam.
- Both host and joining player do this — not just the timing-out side.
- Try the connection again.
Fix 2: Update The Forest
If host and clients are on different versions, joins silently time out instead of failing with a useful error.
- In Steam, right-click The Forest > Properties > Updates.
- Confirm "Always keep this game updated" is selected.
- If still mismatched: Steam > Library > right-click The Forest > Verify integrity of game files.
Fix 3: Host Must Wait For Friends Before Starting
Common mistake: the host clicks Start Game before friends finish joining. Once started, the lobby closes for new joiners.
- Host creates the game and waits in the lobby.
- Friends invite themselves via Steam friends list (Join Game) or via direct invite from the lobby UI.
- All friends finish joining BEFORE the host hits Start.
Fix 4: Port Forwarding (Self-Hosting Only)
If you're hosting from your home connection without using a dedicated server provider, your router may need port forwarding. The Forest uses 27015 (default Steam game port) by default. Without forwarding, friends outside your LAN may time out.
- Forward UDP
27015–27020to your host PC's local IP. - Verify with
portchecker.coor similar. - If your ISP uses CGNAT, port forwarding cannot work — use a dedicated server.
Fix 5: Network Hygiene
- Pause large downloads and streams during connect — packet loss kills lobby handshakes.
- If on Wi-Fi, switch to wired briefly to rule out signal as the cause.
- Reset your router (full power-cycle, 30 seconds off) — fixes stuck NAT translations.
- Disable your firewall briefly to test (re-enable immediately after the diagnostic).
Fix 6: Switch to a Dedicated Server
If "Could Not Connect" keeps recurring, the steady solution is a dedicated server instead of player-hosted. Dedicated servers don't depend on the host's PC being online and bypass NAT/CGNAT problems entirely. See Dedicated Server Setup for the walkthrough.
Diagnostic Cheat Sheet
| Symptom | Most Likely Cause |
|---|---|
| Friend hangs on "Connecting..." then drops | Steam state stuck — restart Steam both sides. |
| Friend gets "Server timeout" | Host pressed Start too early OR port forwarding missing. |
| Some friends can join, others can't | The ones who can't have a different game version. Verify integrity. |
| Worked yesterday, broken today | Game updated; both sides need to update. |
| Internet looks fine but lobby never appears | CGNAT — switch to a dedicated server. |
Stop fighting timeouts. Host a The Forest server with Supercraft — your friends connect by Steam invite, no port-forwarding required.