“Network Connection Lost” interrupts co-op in Dying Light: The Beast with dropped sessions, greyed-out public games, and “Session is no longer available” messages. Recent player reports indicate this can be server-side at times, while quick local actions like reloading your save have also cleared the error for some users.

Use the quick diagnostic below to pick the right path.

Symptom Likely Cause First Action
“Network Connection Lost” persists, public games greyed out. Matchmaking/backend outage or degraded service. Check for widespread reports; wait and retry later.
“Session is no longer available” when joining friends. Transient session mismatch or host issue. Reload save, restart game, try a different host.
High ping and frequent lag spikes in co-op. Local network congestion or routing/VPN issues. Use wired Ethernet, pause downloads, disable VPN/proxy.

Quick diagnosis (server-side vs local)

If a large number of players report the same error at the same time, co-op services may be unstable. In these cases, local tweaks won’t reliably fix disconnects until matchmaking stabilizes. When reports are isolated, local steps below typically help.

Step 1: Check recent community reports for the past few hours (Steam discussions or support megathreads) to see if disconnects are widespread. If many players confirm the same problem, treat it as likely server-side and continue to Method 8 (server-side actions).

Step 2: If reports are mixed or low-volume, proceed to Method 1 (reload save) and work down the list to identify a local fix.

1. Reload your save (fast workaround)

Several players have reported that fully exiting to the main menu and reloading the same save clears the persistent “Network Connection Lost” banner and allows co-op to function again.

Step 1: Exit your current session to the main menu. This forces the game to reinitialize your current world state and matchmaking hooks.

Step 2: Load the same save file from the main menu. After loading in, wait 30–60 seconds, then check co-op availability and try joining a friend.

2. Restart the game and Steam client

Restarting the game and client can clear a corrupted session or expired token that blocks matchmaking.

Step 1: Quit the game to desktop. Ensure it is fully closed in the Task Manager before proceeding to avoid leaving a stuck networking process.

Step 2: Exit and relaunch the Steam client. Reopen the game, wait at the main menu for 20–30 seconds, then enter your save and test co-op.

3. Verify game files (Steam)

File integrity checks replace missing or corrupted files that can disrupt online features after a patch or a crash.

Step 1: In Steam, open the game’s Properties and run a file integrity check. Allow all files to validate and download any replacements.

Step 2: After verification completes, restart the game and retest co-op joining or hosting.

4. Stabilize your connection (reduce ping and spikes)

High latency and jitter frequently trigger disconnects in peer-to-peer or relay-hosted sessions. The goal is to reduce contention and packet loss.

Step 1: Switch to a wired Ethernet connection. This removes Wi‑Fi interference, lowering latency and packet loss during co-op.

Step 2: Pause bandwidth-heavy tasks on your network (downloads, cloud sync, streaming). Reducing concurrent traffic stabilizes ping during gameplay.

Step 3: Disable any VPN or proxy. These add extra hops that increase latency and can trigger session timeouts.

Step 4: Power-cycle your modem and router. Unplug for 30 seconds, then reconnect to refresh your ISP session and routing.

5. Allow the game through your firewall

Windows Firewall or security suites that block the game’s executable can silently prevent session handshakes.

Step 1: Open Windows Security and add the game’s executable to the Allow list for both Private and Public networks. This ensures inbound and outbound traffic isn’t blocked.

Step 2: If you use a third‑party antivirus, add an exception for the game folder. Retest co-op after saving the exemption.

6. Wnable UPnP to avoid strict NAT

Strict NAT can block peer connections. Universal Plug and Play (UPnP) lets your router open required ports automatically for the session.

Step 1: Open your router settings and enable UPnP. Save changes and reboot the router to apply a clean NAT state.

Step 2: Reboot your PC, launch the game, and try hosting and joining co-op again. If UPnP was already on, toggle it off, save, then back on, and retest.

7. Ensure both players are on the same build

Version mismatches can prevent joining or cause the “Session is no longer available” error.

Step 1: Check for updates in the Steam client for both players. Install any pending updates to align builds.

Step 2: After updating, restart the game and have the other player host the session. If it still fails, swap host and try again.

8. Reset the Windows network stack

Refreshing DNS cache and Winsock can remove stale routes or socket errors that interfere with matchmaking.

Step 1: Open an elevated Command Prompt (Start > type cmd > right‑click Command Prompt > Run as administrator). This ensures the following commands can modify system networking.

Step 2: Flush DNS to clear cached entries.

ipconfig /flushdns

Step 3: Reset Winsock to rebuild the sockets catalog.

netsh winsock reset

Step 4: Restart your PC. Launch the game and test co-op connectivity.

9. When issues are server-side

During widespread incidents, co-op options may remain greyed out and sessions fail regardless of local changes. In these windows, local troubleshooting will have limited effect.

Step 1: Try again at a different time of day. Matchmaking often stabilizes after backend updates or load drops.

Step 2: If the problem persists across multiple sessions, document the exact error text and approximate timestamps. Keep this handy for support to accelerate triage once an official fix is available.

Most players get back into co-op by reloading their save, restarting the game/Steam, and stabilizing their network. If none of the above helps and reports are spiking, it’s likely a temporary server issue—give it a little time and retry.