Valheim Network Troubleshooting

Fix common Valheim connection issues — server not in browser, can't connect, crossplay problems, mod conflicts.

Server Not Appearing in the Community Browser

Check	Fix
Public flag set	Ensure `-public 1` in Startup. See Make Server Private — this controls visibility
Server still starting	Wait 1–2 minutes after startup. The server takes time to register with Steam
Crossplay enabled	Crossplay servers register through PlayFab relay, which can take longer to appear
Ports open	Verify UDP 2456, 2457, and 2458 are accessible

Open Console in the XGamingServer Panel and look for "Game server connected" or similar in the startup log.

Common gotcha: the password must be at least 5 characters AND must NOT match the world name. The server refuses to start otherwise.

In Network, confirm the IP and game port. The default is 2456 (UDP).

If the player gets "Version mismatch", update the server. See Update Guide.

These platforms use the PlayFab relay which requires crossplay to be enabled.

In Startup, set the Crossplay variable on. See Crossplay Setup.

After restart, check Console for the 6-character join code. Share this with console players — they connect via the join code, not direct IP.

Important: Crossplay servers cannot use client-side mods. Console players can't install mods, so they'll be rejected from modded servers.

Cause	Fix
Server out of RAM	Check Activity in the panel for memory usage
Network timeout	Player's connection is unstable — not a server issue
Server crashed	Check Console for the crash log. Often caused by a mod incompatibility
Steam outage	Rare, but Steam authentication outages can cause mass disconnects