Helldivers 2 Connection Timeout & Failed to Join Session Error Fix

What is the Helldivers 2 connection timeout / failed-to-join-session error?

Helldivers 2 routes matchmaking through Arrowhead's backend, then hands the actual gameplay session to a peer-to-peer (P2P) connection between the host and joining Helldivers. Two messages dominate post-patch reports: "Connection timeout" when boarding a friend's Super Destroyer, and "Failed to join game lobby" during quickplay matchmaking. After the May 2026 patch (01.003.X), both surged again because the patch tightened the PSN account-link check required for crossplay and bumped the netcode build, creating version mismatches that block joins until both players update.

The error normally fires within 10-30 seconds of clicking Join, sometimes after a brief loading screen that hangs on "Establishing connection." On PC this is almost always a NAT, port, or PSN-link problem — not a server outage. The Arrowhead status page on helldivers2.com/status is the first thing to check, but if the dashboard shows green, the fix is on your end.

When does it occur?

• When joining a friend's Operation through the Galactic War map
• During Quickplay matchmaking on any difficulty
• After the May 2026 patch when one player hasn't updated yet
• On Steam when PSN account linking expired or was never completed
• On strict NAT (Type 3 / Strict) networks behind CGNAT
• Around 10 seconds after entering the Super Destroyer (silent disconnect to ship lobby)

Common causes

• PSN account not linked or token expired — crossplay-required PSN linkage broke for thousands of accounts during the May 2026 server migration
• Game version mismatch — one player on 01.003.100, the other still on 01.003.000 after a hot-patch
• Strict NAT (Type 3) — your router blocks incoming UDP, killing P2P session handshakes
• Missing Steam + PSN port forwarding — the host's router never forwarded the ports the netcode needs
• IPv6 routing on the ISP — Helldivers 2's matchmaking still favors IPv4; an IPv6-preferred stack can silently fail
• Windows Firewall blocking helldivers2.exe — inbound rule missing or set to Block for Public networks
• CGNAT from the ISP (carrier-grade NAT) — common on mobile-hotspot, fiber-shared, and low-end residential plans

Step-by-step fixes

1. Confirm and re-link your PSN account in-game — Open Helldivers 2, go to the main menu, hover Options → Account → Link account. If you see "Linked" with no PSN ID, click Unlink, restart the game, and re-link. The May 2026 server migration invalidated linkage tokens silently — re-linking is the single most common fix for "Failed to join session" right now. Verify on the PlayStation web account portal at account.sonyentertainmentnetwork.com that Helldivers 2 / Arrowhead is listed under Connected Devices.

1. Force the game to launch with IPv4 only — In Steam, right-click Helldivers 2 → Properties → General → Launch Options, paste:

   -useIPv4 -networkthread 2

Then in Windows: Control Panel → Network and Sharing Center → Change adapter settings → right-click your adapter → Properties → uncheck Internet Protocol Version 6 (TCP/IPv6) → OK. Reboot. IPv6 routing is the single most common silent cause of timeouts on Spectrum, Free, AT&T, and other ISPs that hand out IPv6 by default.

1. Open the exact Steam + PSN crossplay ports on your router — Log into your router admin (typically 192.168.1.1 or 192.168.0.1), open Port Forwarding, and add these rules pointing to your PC's local IPv4 address:

- Steam TCP: 27015-27030, 27036-27037

- Steam UDP: 4380, 27000-27031, 27036

- PSN crossplay TCP: 80, 443, 3478, 3479, 3480, 5223

- PSN crossplay UDP: 3074, 3478, 3479

Restart the router after saving. This single step takes most users from NAT Type 3 to Type 2 and clears the "Connection timeout" message immediately.

1. Verify both players are on the exact same patch — Right-click Helldivers 2 in Steam → Properties → Installed Files → Verify integrity of game files. Both players must see the same build number (Options → About → Version) before joining. If one shows 01.003.000 and the other 01.003.100, the older client cannot join the newer one until Steam pulls the patch.

1. Whitelist helldivers2.exe in Windows Firewall — Settings → Privacy & security → Windows Security → Firewall & network protection → Allow an app through firewall → Change settings → Add another app → browse to C:\Program Files (x86)\Steam\steamapps\common\Helldivers 2\bin\helldivers2.exe. Check both Private and Public boxes. The default Steam-installed firewall rule only allows Private — joining over a hotspot or public Wi-Fi otherwise silently fails.

1. Use Friend Code joins instead of Quickplay — In-game, click your friend's banner → Generate Code (host) → share the 8-character code with the joining player → joining player clicks Join with Code in the main menu. This bypasses the broken Quickplay matchmaker and forces a direct P2P session through Steam Datagram Relay, which the May 2026 patch left intact even when matchmaking is degraded.

1. Flush DNS, reset Winsock, and switch to Cloudflare DNS — Open Command Prompt as Administrator and run, in order:

   ipconfig /flushdns
   netsh winsock reset
   netsh int ip reset

Reboot. Then Settings → Network & Internet → your connection → DNS server assignment → Manual → IPv4 → Preferred 1.1.1.1, Alternate 1.0.0.1. Cloudflare's anycast network resolves PSN endpoints faster than most ISP DNS, which prevents the timeout during the initial handshake.

1. Disable crossplay temporarily to isolate the cause — Helldivers 2 → Options → Gameplay → Crossplay → Off. If joins succeed with crossplay off, the issue is on the PSN-link side (step 1). If joins still fail, the issue is NAT/firewall (steps 3 and 5). This split is the fastest way to know which bucket your problem lives in.

If it still doesn't work

If you're still getting "Connection timeout" after all the above, your ISP is almost certainly putting you behind CGNAT (carrier-grade NAT). Run whatismyip.com and check whether your public IPv4 starts with 100.64.x.x through 100.127.x.x — those ranges are CGNAT and make incoming P2P connections impossible without ISP intervention. Call your ISP and request a public IPv4 address (often free, sometimes a $5/month add-on) or use a gaming VPN with port forwarding such as PIA or NordVPN's Meshnet. Mobile-hotspot players are almost always CGNAT'd and should switch to a wired or true-residential Wi-Fi connection before troubleshooting further.

For persistent issues after patch updates, monitor the [official Helldivers 2 Steam discussions](https://steamcommunity.com/app/553850/discussions/1/) — Arrowhead community managers regularly post mitigation steps for backend-side issues within hours of a patch. If your friend cannot join you specifically (but Quickplay works), see our guides on [Steam error code E87](/en/errors/steam-error-code-e87-connection-failed) and [CS2 failed-to-connect](/en/errors/cs2-failed-to-connect-to-match-error) — the NAT/port logic is identical.