Valheim Server Not Showing or Failed to Connect: Fixes
A Valheim dedicated server that does not appear or returns “Failed to Connect” should be checked for startup status, network backend, game version, address, ports and firewall rules before reinstalling anything.
Why a Valheim dedicated server does not show up
A Valheim server can be online but absent from the expected browser when its visibility setting, networking backend, address or game version differs from the player’s connection method. The Steam and PlayFab backends do not behave identically, so first identify which one the server is running.
The fastest way to diagnose the problem is to separate server not running, server running but not listed, and server listed but connection failing. Each points to different settings; blindly changing ports can make an otherwise working server inaccessible.
First checks: is the server actually running?
A Valheim dedicated server must finish startup and load the expected world before clients can join reliably. Open the hosting console or local terminal and look for a completed startup message, rather than relying only on a panel’s green status indicator.
- Confirm that the hosting process is running and there is no repeating crash or restart loop.
- Check that the dedicated server and game clients use compatible versions, especially after a major update.
- Verify the configured world name loads an existing world, not an unintended new one.
- Check the password and that nobody is unintentionally excluded by
permittedlist.txt. - Try joining with the provider’s current public address or join code instead of an old saved favourite.
If startup fails after enabling community mods, consult our BepInEx troubleshooting steps first.
Steam versus PlayFab: check the networking backend
Valheim uses the Steam backend by default and switches to PlayFab when the server starts with -crossplay. Crossplay supports compatible non-Steam players and uses a relay-based connection flow.
| Backend | Typical use | Most relevant checks |
|---|---|---|
| Steam | Steam-only group | Public IP, UDP port pair, router/firewall |
PlayFab (-crossplay) | Supported mixed platforms | Join code, platform services, public address, relay connectivity |
A Steam-only dedicated server will not necessarily be discoverable by players using other platforms. Similarly, a previously saved server address may not work after changing the backend. Remove the old favourite and add the server again if it has changed.
See Valheim crossplay setup for backend configuration and platform-specific joining instructions.
Which ports does a Valheim dedicated server use?
Valheim’s normal dedicated-server base port is UDP 2456 and the following port, UDP 2457. On a self-hosted Steam-backend server, your firewall and router usually need to allow traffic to that port range.
Default base port: 2456/UDP
Additional port: 2457/UDP
Join target: public-server-IP:2456
Do not forward those ports on a rented server unless your provider specifically instructs you to manage firewall settings. Managed hosts normally handle their network edge; their assigned port may differ from 2456.
For the PlayFab crossplay backend, Iron Gate documents that port forwarding is not required in the same way. If crossplay connections fail, check platform availability and the join code before making router changes.
Server is online but missing from the browser
An online Valheim server may be hidden intentionally or may take time to appear in the community list. The -public 1 option enables listing; -public 0 disables public discovery but can still allow a direct connection according to the backend and address available.
Ask the host which networking backend the server currently uses, then try the appropriate connection method. For a Steam-only server, confirm the port and public IP. For PlayFab, try the current join code. If the provider recently moved the instance between locations, old favourites may point to the wrong server.
Failed to Connect after an update
A “Failed to Connect” error after a Valheim update can come from an out-of-date dedicated-server build, a client/server version mismatch, an incompatible mod loader or a previously cached address. These checks are safer than deleting world files.
Compare the game versions, restart the dedicated server using the provider’s update mechanism, then test with an unmodded compatible client if practical. If the server runs only with mods disabled, add plugins back in small groups to identify the incompatible one. Back up the world before altering any content mods.
Password, allowlist and administration issues
Server access can fail even when the network works if a user’s ID is absent from the allowlist or their credentials are wrong. Valheim uses the permittedlist.txt file to restrict access to listed IDs; it is not merely a list of preferred players.
Temporarily review the list and the password from the server’s management interface. Avoid weakening permissions on a public server as a shortcut. Our server settings and commands guide explains visibility, allowlists and administrative files.
Latency, disconnections and rubberbanding
A successful connection with frequent disconnections or rubberbanding is different from a missing server listing. Look at player region, network stability, server CPU contention, excessive world activity and plugin behaviour before blaming the game browser.
For UK players, choosing London or a nearby European location can reduce geographic network distance. However, distance-based latency estimates are not a substitute for a measured round-trip-time test from players’ actual connections. Our Valheim hosting comparison distinguishes host locations and plan resources so you can choose a suitable region.
A quick decision table
This table maps common dedicated-server symptoms to the first diagnostic check and the safest next step, so you can isolate the fault before changing a working configuration.
| Symptom | Check first | Next step |
|---|---|---|
| No server process | Crash log and startup script | Fix startup before networking |
| Process runs but not listed | -public, Steam/PlayFab | Join directly or by code |
| IP join fails | IP, port, firewall | Confirm public endpoint and UDP access |
| Cross-platform join fails | -crossplay, join code | Verify platform/back-end compatibility |
| Only modded clients fail | BepInEx and plugin versions | Align required modlist |
| Connection works but lags | CPU, region, mod load | Diagnose server performance |
When to contact your hosting provider
Contact your host after confirming the server version, backend, public address and startup status. Share the time of the failed connection, the relevant error, the assigned server port and a short console excerpt, but never your password or administrator credentials.
A host with readable console logs, straightforward region changes and dependable support is easier to troubleshoot. Compare those features alongside RAM and pricing in our best Valheim server hosting guide.
Sources
The technical settings and procedures in this guide are based on the game developer documentation and named community tooling linked below.
