War in the North Legacy Connection Failed Fix

Quick answer

“Connection failed” is a symptom, not a diagnosis. The safest first response is to close the game, confirm the platform service, recreate a private lobby, and reverse the host/invite direction. If the same pair still fails, capture the exact error and platform details for support. There is no verified one-click repair in the sources checked on 14 August 2026.

A three-pass test

Pass 1 — remove stale session state

Both players exit to the platform dashboard and close the game completely.
Check that both copies are updated and are the Legacy Edition product.
Sign in to the platform service again if prompted.
Reopen the game and create a private lobby. A private test removes public matchmaking and search from the equation.

If the lobby now works, the failure was likely transient session state. It is still not proof of a permanent fix; repeat the test after a normal exit.

Pass 2 — reverse the direction

Have the other player host and send the invite. Record four values: who hosted, who invited, whether the lobby was visible, and the exact error text.

Result	Next interpretation
Only one host direction works	Host/account/session state is a leading variable
Neither direction works on the same platform	Service, version, or local network remains possible
Same-platform pair works, mixed pair fails	Crossplay or store boundary becomes the leading question
Join succeeds, then disconnects in play	Session stability needs a short checkpoint test

Pass 3 — one network comparison

Use one known-good connection as a diagnostic comparison. Do not change router settings, DNS, ports, and security software at the same time. If the alternate connection works, restore the original network and keep that result in the support report; it is evidence, not a guaranteed home-router fix.

What to record for support

Include the platform and store for every player, region, game version, host and client, private/public lobby, time in UTC, exact error text, and whether the failure happened at lobby creation, invite acceptance, loading, or after gameplay began. A short screen recording is more useful than a statement that “online does not work.”

The current PS5 discussion contains players describing a losing-connection message when creating or joining a friend’s private match, but that is a dated community report, not a confirmed platform-wide outage. See the PS5 discussion and the broader multiplayer checklist.

Do not sacrifice save evidence

Connection troubleshooting should not begin with deleting local saves, deleting cloud saves, reinstalling the operating system, or changing several security settings. Those actions can turn a network question into a recovery problem. Preserve the last known-good save and change one reversible variable at a time.

Sources and evidence boundary

SteamDB feature record — current co-op metadata.
PS5 launch discussion — reported symptom only.
Aspyr support — escalation route.

This page calls the steps a diagnosis because no source checked here proves that any single step fixes every Legacy Edition connection failure.