Getting "Failed to connect" in Valheim right after the 1.0 launch is almost always one of three things: a version mismatch between you and your host, a firewall or port-forwarding gap on a Steam-backend server, or the Switch 2 crossplay outage that Iron Gate is still fixing. This guide walks every cause in order — from the 30-second checks to a full dedicated-server fix — using the official Iron Gate dedicated-server documentation, verified for patch 1.0.12 (2026-09-11).
Quick answer: the fastest fixes for "Failed to connect"
TL;DR — do these first, in order:
- Match versions. Every player must be on the exact same patch. Valheim 1.0 shipped Sept 9, 2026 and has already had hotfixes; if one person is on 1.0.10 and another on 1.0.12, the join can fail. Update Steam and restart the game for everyone.
- Restart the game and Steam (not just rejoin). Launch-week server load caused temporary join failures for many players — a clean restart clears a stale session.
- Use "Join IP" or a join code, not the server browser. The public browser often lags behind or times out under load; a direct IP:port or crossplay join code connects when the list won't.
- On a self-hosted Steam server, forward ports 2456–2457 (TCP/UDP) or switch the server to the crossplay backend, which needs no port forwarding at all.
- Playing on Switch 2? Crossplay with other platforms is temporarily unavailable as of 2026-09-11 — this is a known Iron Gate issue, not something you can fix on your end.
If those don't do it, work through the sections below by connection type.
Why does Valheim say "Failed to connect"?
Valheim's multiplayer is peer-to-hosted: someone runs the world (a player host or a dedicated server) and everyone else connects to it. A "Failed to connect" error means the handshake between your client and that host didn't complete. There are only a handful of reasons that happens, and in the 1.0 launch window they cluster hard around version drift and launch-day server load.
On r/Valheim right now the pattern is textbook. One player posting that friends "failed to connect after multiple tries" got the single most useful reply first: "All players are on the same patch?" Another added, "Maybe server issues — me and my wife can't connect together anymore either… literally just 15 minutes ago." Two players, same night, same error — that's a launch-load fingerprint, not a broken config.
Here is the full cause list, ordered by how often it's the real culprit at 1.0:
| # | Cause | Who it hits | Fix section |
|---|---|---|---|
| 1 | Version mismatch between players | Everyone | Version check |
| 2 | Launch-week server load / stale session | Everyone | Restart & reconnect |
| 3 | Firewall / no port forward (Steam backend) | Self-hosted servers | Ports & backend |
| 4 | Wrong backend (Steam vs crossplay) | Cross-platform groups | Ports & backend |
| 5 | Banlist / whitelist ID mismatch | Admin-run servers | Permission files |
| 6 | Switch 2 crossplay outage | Switch 2 players | Switch 2 |
| 7 | LAN / loopback join on a crossplay server | Same-house players | The local-IP trap |
Step 1: Make sure everyone is on the same version
This is the number-one fix in the launch window and the one people skip. Valheim clients on different patches can fail to connect to each other.
The live build as of writing is 1.0.12 on Steam and 1.0.10 on all other platforms (Xbox shows as 1.0.11 but is "identical to 1.0.10"), released 2026-09-11. Iron Gate has said the Steam-only fixes "will arrive to all other platforms shortly," so a Steam player and an Xbox player can briefly be a hotfix apart.
To force everyone onto the same build:
- Steam: right-click Valheim → Properties → Updates → set to "Always keep this game updated," then let Steam finish patching before launching.
- Restart Steam entirely so it re-checks for the update — Steam sometimes defers a patch until restart.
- Confirm the version in-game. The build number shows on the main-menu screen; compare it with your friends before trying to join.
- Dedicated server owners: the server must be updated too. It's a separate Steam Tool ("Valheim Dedicated Server") and does not auto-update while it's running — stop it, let Steam patch it, then restart.
If the version already matches on every machine and it still fails, move on.
Step 2: Restart and reconnect the right way
Launch-week congestion produces temporary, self-clearing failures. The fix is a clean restart, not a rapid retry loop.
- Fully quit Valheim and Steam on both host and client, then relaunch host first, client second. A stale login session is a common cause of a sudden "was working, now fails."
- Don't hammer Join. Repeated instant retries can leave a half-open session. Wait ~30 seconds between attempts.
- Prefer a direct join. On the main menu use Join Game → Join IP and enter the host's `publicIP:port` (default port `2456`), or paste the crossplay join code if the host is on the crossplay backend. Direct joins routinely succeed when the browser-listed entry times out.
- Check the host is actually reachable. A player-hosted world only exists while that player is in it — if the host alt-tabs to the main menu, everyone drops.
Step 3: Fix ports, or switch to the crossplay backend
If you run a dedicated server, connection failures almost always trace to the network layer. Iron Gate's official guide is explicit about how the two backends behave, and getting this right fixes the majority of self-hosted "Failed to connect" reports.
The two backends:
- Steam backend (default): "only Steam users can see and join the Server," and it requires port forwarding. Per the official guide: "the most important thing is to make sure that the Server uses a Port Range that has access to the Internet… The default Port Range that the Server uses is 2456-2457."
- Crossplay backend (`-crossplay`, PlayFab): "the server transmits data via a relay server and therefore does not require Port Forwarding to be accessible from outside of your local network." It also gives you a join code and lets players from any platform connect.
If you're on the Steam backend and getting failures:
- Forward ports 2456 and 2457 (the server uses the port you set and port+1) on your router, both TCP and UDP, to the server's local IP.
- Allow Valheim through the host's firewall. The guide notes: "If you get a Windows Firewall-popup please fill all checkboxes to allow the Server to communicate with the Internet."
- Double-check the port in your start script matches the port you forwarded.
The simpler fix for most home hosts: add the `-crossplay` flag and skip port forwarding entirely. Your start line lives on line 7 of `start_headless_server.bat` (Windows) or `start_server.sh` (Linux). A minimal crossplay launch looks like:
``` start valheim_server -name "My Server" -port 2456 -world "Dedicated" -password "vikings123" -public 1 -crossplay ```
One official tip that saves a lot of pain: copy the start script and edit the copy. Per Iron Gate, the original "will be reset each time it is updated in Steam" — so a hotfix silently wipes your settings and the server comes back up misconfigured, which reads to players as a connection failure.
Two more rules that block joins if you break them:
- Set a valid password. Valheim rejects a password that's too short or that contains the server name, and the server won't start — so nobody can connect. Use a simple 6+ character password that isn't your server name.
- `-public 1` lists the server in the browser; `-public 0` hides it and makes it Join-IP-only — great for a LAN game, but if you set it by accident, friends can't find the server and assume it's down.
Step 4: Check your banlist and permitted list
If a specific person can't connect but everyone else can, it's likely a permission-file issue — and 1.0 introduced a real one that a hotfix just fixed.
The 1.0.12 notes state, verbatim:
"Fixed a problem with banlist and whitelist that made them only compatible with new IDs (e.g. V_123456789) even though they should work with old IDs too (e.g. Steam_123456789)."
So if you're running an older server binary with a permittedlist.txt (whitelist) using classic `Steam_…` IDs, legitimate players could be silently rejected until you update to 1.0.12. Two things to know from the official guide:
- Permission files are `adminlist.txt`, `bannedlist.txt`, and `permittedlist.txt`, one Platform User ID per line, in the server's save folder.
- Adding anyone to the permitted list bans everyone else — the guide warns: "adding a person on the permitted list will ban everyone else from the server." An accidental single entry locks the whole server.
Grab the correct ID from the in-game F2 panel or the server log; it follows the format `[Platform]_[User ID]` and is case-sensitive.
The local-IP trap most people miss
Here's a genuinely non-obvious one that catches players trying to connect to a crossplay server on their own network. Straight from the official guide:
"You can connect to a Crossplay server using the public IP address and port number, a join code or via the server list, however it's not possible to connect using a local IP address or a loopback IP address."
Translation: if your dedicated server runs on the crossplay backend, you cannot join it by typing `192.168.x.x` or `127.0.0.1`. Use the public IP, the join code, or the server browser instead. Many "it works for my friend but not for me on the same wifi" reports are exactly this.
Is Switch 2 crossplay working?
Not right now. This is the one "Failed to connect" you can't fix yourself. In the hotfix post dated 2026-09-11, Iron Gate wrote:
"Due to an unforeseen issue, the patch was unable to be uploaded to Switch 2. Unfortunately this means crossplay is not currently supported between Switch 2 and other platforms. We are hoping to solve this as soon as possible and thank you for your patience."
So as of patch 1.0.12:
| - **Crossplay works fully between PC (Steam / Microsoft Store), Xbox One, Xbox Series X | S, and PlayStation 5.** |
|---|
- Switch 2 cannot currently crossplay with those platforms while the hotfix is held back. Switch 2 players can still play with each other; cross-platform is pending an Iron Gate fix.
Also keep two things straight, because they get conflated constantly: crossplay is not cross-save. Per Iron Gate's 1.0 FAQ, only Xbox↔PC (launched from the Microsoft Store) share save files — "Beyond this, there will be no cross platform sync for your save files." Your PS5 and Switch 2 saves stay on those consoles even though you can (usually) play together.
Still failing? A clean checklist
Run this top to bottom and one of them will be your culprit:
- Everyone on the same patch (1.0.12 Steam / 1.0.10 elsewhere) — recheck the main-menu version number.
- Restarted Valheim and Steam (host and client), host launched first.
- Tried a direct Join IP or join code, not just the browser.
- Dedicated server: ports 2456–2457 forwarded (Steam backend) or `-crossplay` enabled (no forwarding needed).
- Password is valid (long enough and not the server name); `-public 1` is set.
- Server updated to 1.0.12 and banlist/whitelist using IDs that resolve.
- Not joining a crossplay server via local/loopback IP.
- Not a Switch 2 cross-platform attempt (currently unsupported).
FAQ
Why can't my friend connect to my Valheim world after the 1.0 update? The most common reason is a version mismatch — make sure Steam has fully updated Valheim for both of you and restart the game so the build numbers match. During the launch week, temporary server load also caused join failures that cleared on a full restart. If you host a dedicated server, confirm ports 2456–2457 are forwarded (Steam backend) or add the `-crossplay` flag so no forwarding is needed.
What ports does Valheim use for a dedicated server? Per Iron Gate's official guide, the default port range is 2456–2457 — the server uses the port you specify (default 2456) and that port plus one. Forward both TCP and UDP to the server's local IP. If you enable the crossplay backend with `-crossplay`, you don't need port forwarding at all because traffic goes through a relay server.
How do I fix "Failed to connect" on a crossplay server? Make sure you're joining with the public IP, join code, or server browser — a crossplay server cannot be joined via a local (`192.168.x.x`) or loopback (`127.0.0.1`) address, which is a common mistake for players on the same network. Confirm the host launched the server with the `-crossplay` argument and that every client is on the same patch.
| Does Valheim crossplay work on all platforms in 1.0? Crossplay works fully between PC, Xbox One, Xbox Series X | S, and PlayStation 5. As of the 2026-09-11 hotfix, Switch 2 crossplay is temporarily unavailable because the patch couldn't be uploaded to Switch 2; Iron Gate says it hopes to fix it as soon as possible. Note that crossplay is not the same as cross-save — only Xbox and PC (via the Microsoft Store) share save files. |
|---|
Why can't anyone join my whitelisted server? Two likely causes. First, before patch 1.0.12 the whitelist/banlist only accepted the new `V_…` ID format even though old `Steam_…` IDs should work — update the server to 1.0.12. Second, remember that adding even one player to `permittedlist.txt` bans everyone not on that list, so an accidental entry locks the whole server. Use IDs from the in-game F2 panel in the exact `[Platform]_[User ID]` format.
Is the "Failed to connect" error a Valheim bug or my setup? In the 1.0 launch window it was often server-side load that resolved on its own, but the durable causes are almost always local: version drift, firewall/port forwarding, wrong backend, or permission-file mismatches. Work through the checklist above — if you're not on Switch 2, it's fixable on your end.
This guide applies to Valheim patch 1.0.12 (Steam) / 1.0.10 (all other platforms), released September 11, 2026. Server flags and defaults are from Iron Gate's official dedicated-server guide on valheimgame.com. Looking for more? See our other Valheim 1.0 guides:
