Valheim 1.0 Won't Connect? Here's the Fix
Since the Valheim 1.0 launch (v1.0.7, 9 Sep 2026) and hotfix 1.0.12 on 11 Sep, almost every 'failed to connect' or 'incompatible version' report is one thing: your client updated to 1.0.12 before the dedicated server did (a build mismatch). Match both sides to 1.0.12, forward UDP 2456-2457, and — if the browser list is empty — join by direct IP. The exact steps are below.
Valheim 1.0 launch build timeline (verified 25 Sep 2026)
Last verified: 2026-09-25
Error codes
Incompatible version / "Failed to connect"
Your client and the server are on different Valheim builds, so the handshake is rejected before you get in.
Cause: After the 1.0 launch (v1.0.7, 9 Sep 2026) and hotfix 1.0.12 (11 Sep 2026), a client that auto-updated to 1.0.12 cannot join a dedicated server still on 1.0.7, and vice-versa.
- Match builds first: the server and every client must run the identical version (1.0.12). Update the dedicated server via SteamCMD (app 896660) and restart it after any patch.
- If you must stay on an older build, use Steam > Valheim > Properties > Betas to pin the same version on client and server.
- Check the server console/log for the version line and compare it to the version shown on the Valheim main menu (bottom-left).
Server not showing in the Community/Friends list
The dedicated server is running but never appears in the in-game browser.
Cause: UDP ports not forwarded, or the listing query port (2457) blocked; the server can be running yet invisible.
- Forward UDP 2456 and 2457 (game + query) to the server's local IP and allow them through the firewall; 2458 is used by some setups.
- Join by direct IP: in-game use Join > enter IP:2456 instead of the browser list.
- Confirm the server was launched with a public flag if you want it listed; otherwise use direct-IP or invite.
Disconnected / connection timed out mid-session
You reach the world, then drop after seconds or minutes.
Cause: Unstable UDP path/NAT, server on a different build after a silent update, or steamclient session desync.
- Fully restart Steam on the client (clears a stale steamclient session) and relaunch Valheim.
- Restart the dedicated server once after any patch so it pulls the current build (1.0.12).
- Verify UDP 2456-2457 forwarding is stable; a flaky port-forward drops sessions intermittently.
Fixes that work for most Valheim errors
- Match builds first: client (main-menu bottom-left) must equal the dedicated-server version — the #1 cause after the 1.0.7 -> 1.0.12 patch chain.
- Update the dedicated server through SteamCMD (app id 896660) and restart it after every Valheim update.
- Forward UDP 2456 and 2457 (game + query ports) to the server's local IP; open them in the firewall.
- Use a direct IP:2456 join as a reliable fallback when the browser list is empty.
- Restart Steam on the client to clear a stale steamclient session before assuming the server is down.
- Pin the same build on client and server via Steam Betas if you need to delay an update.
FAQ
Why does Valheim say 'incompatible version' after the 1.0 update?
Your client and the dedicated server are on different builds. After the 9 Sep 2026 launch (1.0.7) and the 11 Sep hotfix (1.0.12), a 1.0.12 client cannot join a 1.0.7 server. Update the server via SteamCMD (app 896660) so both sides run 1.0.12, then restart it.
Which ports does a Valheim dedicated server need?
UDP 2456 (game) and 2457 (Steam query), forwarded to the server's local IP and opened in the firewall. Some setups also use 2458. Forward UDP, not TCP.
My server runs but nobody can see it — what now?
Forward UDP 2456-2457, confirm the query port isn't blocked, and have players join by direct IP:2456 instead of the community browser while you sort the listing out.
How do I stop random disconnects in Valheim multiplayer?
Restart Steam on the client to clear a stale session, restart the dedicated server after any patch so it's on 1.0.12, and make sure your UDP 2456-2457 port-forward is stable.
Other games
- Apex Legends Error Codes — Code:Leaf, Code:Wheel, Code:Net, Engine Error & More
- Elden Ring Error Codes — Inappropriate Activity Detected, Failed to Join Session, EAC & More
- Final Fantasy XIV Error Codes — 90002, 2002, 3102, 90006, i2501, 4006 & More
- Genshin Impact Error Codes — 4201, 31-4302, 9908, 4206, 1041, 10108 & More
- League of Legends Error Codes — Error Code 003, 004, 0, Bugsplat & More
- Overwatch 2 Error Codes — LC-208, BC-153, BN-564, LC-202, BLZBNTBNA & More
- Rainbow Six Siege Error Codes — 2-0x0000C015, 3-0x0001000B, 8-0x00003700, Vulkan & More
- Valorant Error Codes — VAN 9003, VAL 43, VAN 152, VAN 68, Error 29 & More