Valheim Server Not Showing Up? Ports, Crossplay, and Server List Fixes

A Valheim dedicated server can be running normally and still be invisible or unreachable. The most common causes are a missing second UDP port, checking the wrong server list, a mismatch between Steam and crossplay networking, or a client and server on different versions.

Work through this checklist in order. It separates a server process problem from a network or discovery problem, so you do not reinstall a healthy world while chasing the wrong symptom.

Run Valheim with both ports, crossplay controls, and managed backups configured for you

1. Confirm that the server finished starting

A process existing is not the same as a joinable server. Read the live output and wait for Valheim to report that the game server connected. If it exits earlier, fix the first error in the log before changing router or firewall rules.

Frequent startup failures include a password shorter than five characters, a password contained inside the server name, missing Linux libraries, an invalid save path, and a world created by a newer game version. Keep the matching .db and .fwl world files together.

2. Open both UDP ports

Valheim uses the port passed to -port and the next port. With the default base port, that means UDP 2456 and UDP 2457. A rule for 2456 alone is incomplete even though the launch command contains only -port 2456.

Apply the pair at every layer between the internet and the process: cloud firewall, host firewall, router port forwarding, container or virtual-machine mapping, and Docker publishing if you use Docker. Forward both ports to the same internal machine. Do not change the launch command to 2457 just because one browser view displays the second port.

3. Choose Steam or crossplay deliberately

Without -crossplay, Valheim uses the Steam backend. Steam players can join, and public servers are discovered through the Steam-backed list. Add -crossplay to use PlayFab when Xbox, Microsoft Store, and Steam players need to share a world.

Crossplay provides a join code and can relay connections without home-router port forwarding. It also changes how you test the server. A crossplay server cannot be joined through a local or loopback address, even from the same home. Use its join code, public address, or public list entry. Looking in Steam's own server browser for a PlayFab server can make a working server appear missing.

4. Check public visibility separately from reachability

-public 1 lists the server in Valheim's community browser. -public 0 keeps it unlisted but does not make it offline. Test an unlisted server with Join IP on the Steam backend, or with the appropriate public address or join method on crossplay.

New public listings may take a little time to appear. Search for the exact server name and clear filters. If direct joining works but search does not, the game port and process are healthy. Focus on the selected backend, public flag, list filters, and listing delay.

5. Rule out CGNAT and double NAT

Home-hosted Steam servers need unsolicited UDP traffic to reach the host. Compare the router's WAN address with the public address reported by an external service. If they do not match, your ISP may use carrier-grade NAT, or a second modem may be routing in front of your router.

For double NAT, forward the port pair through both devices or put one into bridge mode. For CGNAT, ask the ISP for a public address, use Valheim crossplay, or move the server to a datacenter host with a public address.

6. Match the client and server versions

Valheim clients usually update automatically. A manually operated dedicated server may not. If the server appears but joining fails after a game update, stop it cleanly, update Steam app 896660, and start it again. Updating while the process still owns the world files is unnecessary risk.

Public-test branches must match too. A stable client cannot join a server left on a test branch, and a test client cannot join the stable server simply because both say Valheim.

7. Test from outside the server's network

A test from the host itself does not prove that internet traffic reaches it. Ask a friend on another connection to join, or test from a phone hotspot. Some routers do not support NAT loopback, so the public address can fail inside the house while working for everyone outside it.

For Steam networking, the quickest clean test is an unlisted server with the correct public IP and base port. For crossplay, use the join code or public address rather than a private LAN address.

Fast diagnosis by symptom

• No connected message in the log: fix startup, password, library, save-path, or world-version errors first.
• Works on LAN but not from outside: inspect both UDP ports, firewall, forwarding, double NAT, and CGNAT.
• Direct join works but the list is empty: check -public, backend, filters, exact name, and listing delay.
• Xbox or Microsoft Store players fail: enable crossplay and restart, then use the PlayFab join path.
• Stopped working after a patch: update app 896660 and match branches.
• Only local public-IP tests fail: try another network before changing a working configuration.

How GHosting handles these details

GHosting allocates and proxies Valheim's complete two-port range, exposes Steam or crossplay mode in Settings, and keeps each world's files under its own jailed server directory. You can choose the world name, save interval, rolling-backup count, public visibility, world preset, and an optional daily restart from the panel.

Restarts send Valheim a graceful interrupt and allow time for a final save before the service comes back. Automatic version checks flag an available dedicated-server update, while the daily production verification provisions a disposable Valheim server, applies representative settings, restarts it, checks readiness, and removes it again.

The port pair, crossplay behavior, public flag, backup arguments, and world presets in this checklist come from Iron Gate's official dedicated-server guide.