War in the North Legacy Multiplayer Not Working

Quick answer

There is no verified universal multiplayer fix yet. Launch-week reports show different failure points: some players cannot create or join a private match, some see a connection error immediately, and other players can play normally. Diagnose the first step that fails rather than applying a random list of router changes.

Status — checked 14 August 2026: community-reported, not a confirmed global outage. One PS5 thread describes losing connection while creating or joining a friend’s private match; replies report the same symptom.

Find the failure stage

Failure stage	First test	What the result tells you
No multiplayer option	Confirm the exact Legacy Edition product and update	You may be in the wrong application or an incomplete install
Lobby creates but friend sees nothing	Reverse the invite direction	Distinguishes host/session state from the joining account
Friend sees lobby but cannot join	Test same-platform, same-store pair	Separates a platform boundary from a general session failure
Join succeeds, then drops	Cross one checkpoint in a private lobby	Identifies session stability rather than discovery
Co-op works but progress disappears	Run the short persistence test	Move to the dedicated progress page instead of repeating network resets

Reversible checklist

1. Confirm the build. Every player should launch The Lord of the Rings: War in the North — Legacy Edition, not the old 2011 Steam application or a shortcut pointing at it.
2. Check service status. Look at the platform’s own network status page and sign in again if the service reports a problem.
3. Close the game fully. End the process, relaunch, and recreate a private lobby. Do not stack a reinstall or save deletion on top of this test.
4. Swap host and invite direction. Have the other player host the same short test. Record which direction worked.
5. Use one controlled network comparison. A phone hotspot or a known-good connection can show whether the home network is the leading variable. Stop after one comparison and restore the original setup.
6. Test a short session. Load into a safe area, cross one checkpoint, and exit normally. This catches a drop that happens only after the lobby starts.
7. Capture evidence. Save the exact error text, platform, store, region, version, host, time, and whether the lobby was public or private.

Avoid these early “fixes”

Do not delete local or cloud saves, disable console security, forward ports, or rebuild a database because a forum comment suggested it. Those actions can destroy recovery evidence and still do not prove the cause. Change one variable at a time and keep the last known-good configuration.

If a same-platform test works but a mixed-platform pair fails, read the crossplay evidence page. If a player can join but loses levels or gear, use multiplayer progress not saving.

Sources and evidence boundary

• Steam feature metadata — online and local co-op listings.
• PS5 launch discussion — dated connection-loss reports.
• Aspyr support — use the platform and version details when escalating.

The checklist is diagnostic guidance. It is not a claim that any one step repairs the underlying service or game defect.