Valheim "Failed to connect" to a friend's server (fix)
Written by
Last checked
October 18, 2026
Joining a friend's world or a dedicated server ends in "Failed to connect", or sits on "Connecting" and never loads the world.
Also appears as: valheim failed to connect, failed to connect valheim, valheim failed to connect to server, valheim cant join friend, valheim can't connect to friend's server, valheim stuck on connecting, valheim cannot join server after 1.0, valheim connection failed, valheim couldn't resolve join code, valheim can't join dedicated server after 1.0.20
Valheim has no Iron Gate servers, so there is no studio server to be down: the connection runs to the person or company hosting the world. A December 2023 Steam Discussions thread has three players reporting "failed to connect" to a world that worked the day before; a Steam Community moderator (not Iron Gate staff) answered with the checks below, and the original poster had already reinstalled, verified files and opened the firewall without luck. A September 2026 thread from a player stuck on "Connecting" to a friend got no answer from Iron Gate. What Iron Gate itself has said: its Patch 1.0.14 notes (September 17, 2026) describe a cache bug that could leave players unable to join remote servers, and say the caching was turned off. Iron Gate has not said that bug is behind any particular "Failed to connect" report. After Patch 1.0.20, an October 18 r/valheim poster got a friend back onto their dedicated server by turning crossplay off and forwarding ports.
Fix it, step by step
Update the game, and ask the host to, to Patch 1.0.14 or later
Update the game, and ask the host to update theirs, to Patch 1.0.14 or later (1.0.20 is the newest as of October 18, 2026; neither it nor 1.0.17 lists a connection fix, so 1.0.14 is still the floor). Iron Gate's 1.0.14 notes say it disabled biomedata caching to fix a cache that could get stuck in an invalid state and make joining remote servers impossible. The notes do not say this is the cause of every failed connection, and Iron Gate says a patch can take a few days to reach every platform.
Join a crossplay-backend server by public IP and port, join code or server list
If the server runs on the crossplay backend, join it by public IP address and port, a join code, or the server list. Iron Gate's dedicated server guide says "it's not possible to connect using a local IP address or a loopback IP address" on that backend.
- NoteConfirmed
Iron Gate's patch notes for 1.0.14, 1.0.16 and 1.0.17 each say the patch takes a few days to reach all platforms, but "crossplay will still remain functional". Its September 11 hotfix notes apologised for a delayed Switch 2 patch and said "now all platforms should be compatible for crossplay again". A player on a platform still waiting for a patch is the likeliest place a version difference shows up, though Iron Gate has not tied that to "Failed to connect".
Forward ports 2456-2457 for a Steam-backend dedicated server
If the server is a dedicated server on the Steam backend (started without -crossplay), its port range, 2456-2457 by default, has to be reachable from the internet, which means forwarding those ports on the router. Iron Gate's dedicated server guide says a crossplay-backend server needs no port forwarding.
If everyone is on Steam, turn crossplay off (two reports)
If everyone in the group is on Steam, ask the host to start the world with crossplay turned off (the option sits next to the start button), delete the old server entry from your Favorites tab, and join through a Steam friend invite from the Friends tab. A Steam Community moderator gave this answer in the December 2023 thread, but that poster didn't report back. After Patch 1.0.20, the poster of an r/valheim thread (October 18), where one of six players got "Failed to connect" and "couldn't resolve join code", said: "I just turned off crossplay and port forwarded and now he can join again!" A dedicated server without crossplay needs ports forwarded (see the step above). Iron Gate hasn't commented.
Test the link with a buffer-bloat test and /ping (one report)
Test the link: the same moderator suggested running a buffer-bloat test (speed.cloudflare.com) and typing /ping in the Valheim chat once you get in, to see whether latency is high or unstable, and noted that Wi-Fi connections are more often problematic than wired ones.
Sorted. Glad that worked.
Nothing worked. Here's what to do next.
You've ruled out every step on this page, which is useful. Send this to support or drop it in the community Discord so nobody makes you repeat yourself.
Hit this error? Leave a comment
Say where you are, what you see on screen, and whether any fix worked for you.
No links. Anonymous, no account. Keep it about the game.
What people are saying
Notes from players who've hit this one — no time limit, an answer from months ago is still an answer.
- Nothing reported here yet.
From isthisgamedownMatched on ""
From isthisgamedownMatched on ""
From isthisgamedownMatched on ""
Other Valheim error codes
Recently added
- AION 2 "insufficient gameplay record" market listing block
- ARC Raiders error ARMR0014 on Storms and Night Raids
- Enshrouded server exits 0xC0000135 on Windows Server Core (fix)
- Gears of War: E-Day stuck on "Fetching Data" (fix)
- Gears of War: E-Day lucas-gnasher: reward expired
- Gears of War: E-Day reaver-tyrus: can't queue ranked
- Valheim server "App 896660 state is 0x6" after update (fix)
- Valheim Unity crash error (0xc0000005): what to try