Valheim Connection Troubleshooting — Fix Failed Joins, Lag and Crossplay Drops

Start here: what kind of session are you in?

Most Valheim multiplayer problems fall out of three situations, and the fix depends on which one you are in:

Situation	Where the problem usually lives
A player hosts a peer session	Host version, host crossplay setting, host network
A self-hosted dedicated server	Port forwarding, double NAT, server crossplay flag
A rented dedicated server	Version parity, the panel’s port/crossplay config

If you have not set the session up yet, read the crossplay guide first — this page assumes a session already exists and is misbehaving.

Rejected join codes

Being verified: exact error strings differ by build and platform. The mechanism below is stable; the wording is not. See /about/ for how we verify.

Work through these in order:

1. Compare version numbers in each player’s main menu. A mismatch is the single most common cause and the one nobody checks first.
2. Confirm crossplay is enabled on the host. On PC it lives in the multiplayer options; on console it is in the world/session settings.
3. Restart the session to regenerate the code. Join codes are session-scoped — an old code from a previous evening will always be rejected.
4. Re-enter the code carefully. Codes are easy to mistype; paste or read them back digit by digit before blaming the network.

Crossplay players can’t see each other

Steam, Microsoft Store / Game Pass, Xbox, PS5 and Switch 2 only appear to each other when every side is on the same version and the host has crossplay on. When one condition fails, the session is hidden, not shown as full or locked — which is why “I can’t find it” and “it says full” are two different problems. If the host is a self-hosted dedicated server, its own crossplay flag must also be on for it to issue a usable code.

Dedicated server nobody can reach

A dedicated server needs three UDP ports reachable from the internet: 2456 plus 2457 and 2458. The usual failure points:

• Ports forwarded to the wrong internal IP. The server machine’s LAN address must be the one the router forwards to; DHCP can change it after a reboot.
• Double NAT. A router plugged into another router (common with ISP gateway + own router, or mesh setups) means the outer device also has to forward. If you cannot fix it, put the inner router in bridge/DMZ or forward on both.
• Crossplay flag off on the server. Without it the server cannot issue a join code, so code-based joins fail even with perfect ports.
• Version drift. Servers are not always updated the moment a client patch lands; match the client version.

Full setup walkthrough: dedicated server guide.

Lag and rubber-banding

In a peer-hosted game, the host’s connection is everyone’s connection. Your own hardware is rarely the bottleneck; the host’s upload speed and line stability set the ceiling for the whole session.

• Host on the most stable uplink available, ideally wired rather than Wi-Fi.
• Close bandwidth-heavy apps on the host (streaming, cloud backups, large downloads).
• For an always-on or larger group, move off peer hosting to a dedicated server or a rented host, so no single home line carries everyone. Hosting options are compared in the dedicated server guide.

Being verified: tick-rate and latency figures are not published here — they vary by host, region and build. We describe the direction of each fix rather than quote numbers. See /about/.

Worlds and progression when you switch hosts

Worlds are files (.db and .fwl), so a world can be copied between a peer session and a dedicated server. Back the world up before every version update and before any host change, and check your platform’s account rules if progression is tied to a platform account rather than the world file.