Quick answer
Current live-game guidanceWhat to do first
First confirm that the server is running and the host and clients use compatible game versions and branches. Then check the backend: a crossplay server accepts a join code, public IP or server-list entry, not a local or loopback IP. A Steam-backend server has different networking requirements. Do not delete your world or disable security software as a first fix.
Identify the backend before changing ports
| Server setup | Join and network check |
|---|---|
| Crossplay / -crossplay enabled | Use the current join code, public IP plus port, or server list. Local and loopback addresses are not supported for this backend. The relay does not require router port forwarding. |
| Steam backend / no -crossplay flag | Only Steam users can join. The host must make the selected port and the following port reachable; the default pair is 2456–2457. |
| A hosting provider's panel | Check the panel's actual backend and connection details. A generic tutorial may describe a different setup. |
Work through low-risk checks first
- 1
Ask whether anyone else can join. If nobody can connect, start with the host; if one player fails, compare that player's setup with a working client.
- 2
Have the host confirm the server is ready. The official dedicated-server program reports Game server connected when it is accepting connections.
- 3
Compare the exact game version and branch on server and client. Public Test is not interchangeable with live just because both say Valheim.
- 4
If mods are involved, compare the required mod setup with the host. Back up first and avoid loading a valuable modded world in an incompatible configuration.
- 5
Recheck the address, join code and password. Do not use a local address for a crossplay relay connection.
- 6
Ask the administrator to inspect access lists if only selected people fail. A permitted list restricts access to the listed users; a typo in a platform user ID can exclude someone.
If the basic checks do not explain it
Record the exact error, time, platform, game version, backend and whether other players can connect. That gives the administrator or official support something concrete to compare. Remove passwords, private addresses and account identifiers before posting logs publicly.
For a Steam-backend networking problem, use the router's documentation or hosting provider's instructions for the configured ports. Do not open a wide range of unrelated ports or turn off your entire firewall.
Disabling crossplay is not a neutral fix for a mixed-platform group: it can remove the ability for non-Steam players to join. Change it only if the host understands which players the new setup will exclude.
A connection failure does not prove a corrupted world. Preserve saves and investigate the server log before attempting any rollback.
Version & sources
Sources & what may change
- Applies to
- Live 0.221.12 through Ashlands; check world settings and mods.
- Last verified
- September 4, 2026
- When to check again
- Recheck after the September 9 release, a relevant patch, or a change to the linked documentation. This page is not yet verified for 1.0.