
Valheim Connection Issues
Fix "connection could not be established", timeout errors, and crossplay connection problems on your Valheim dedicated server.
Quick Diagnosis
Before troubleshooting, verify these basics:
1. The server shows as Online in the GameGrid dashboard.
2. You know which connection method your server uses. Crossplay is on by default, and a crossplay server is joined by its six-digit Crossplay Join Code, not by address - the address has nothing listening behind it. Only a server with crossplay turned off is joined by IP:port. Connection Info on the Overview tab shows which you have.
3. You own Valheim on the platform you are connecting from.
4. The server password is correct (case-sensitive).
5. You have not been banned from the server, and the Permitted list is either empty or contains you.
If all of the above are correct, the issue is likely one of the specific cases below.
Steam Player: "Connection Could Not Be Established"
This is the most common error and has several causes:
You are typing an address at a crossplay server. This is the single commonest cause on GameGrid, because crossplay is on by default. Use the Crossplay Join Code from Connection Info instead - it works for Steam players too.
Server still starting: wait 60 seconds after the dashboard shows Online for the world to finish loading.
Cached connection: if you previously connected to this server on the other backend, Valheim caches the old one. Remove the server from your Join Game recent list and add it again.
Wrong address on a Steam-only server: enter host and port exactly as Connection Info shows them, e.g. 203.0.113.50:28000. GameGrid allocates the port from its own pool, so it is not 2456, and the port is required.
Server is full: Valheim stops at 10 players unless GameGrid has installed the MaxPlayerCount plugin on your server. Check the dashboard player count.
Network issue: if your own internet connection is unstable, the handshake will time out. Try a wired connection if on Wi-Fi.
Xbox or Game Pass Player: Cannot Connect via Join Code
Verify crossplay is enabled on the server. The Join Code only exists when crossplay is on - check Connection Info on the Overview tab.
If the server started less than a minute or two ago, PlayFab may not have issued a code yet. The row appears on its own once it has.
The Join Code changes on every server restart. Make sure you are using the current code, not an old one.
Ensure you are entering the six-digit code, not an IP address. Xbox and Game Pass clients cannot use addresses at all.
Game Pass players cannot disable crossplay on their end. They can only join crossplay-enabled servers.
If parental controls are enabled on the console account, crossplay may be blocked. Check the console's parental control settings.
"Disconnected" Shortly After Joining
Cause: the server's outgoing data rate is being exceeded, or a mod mismatch is causing the client to drop.
For vanilla servers: this is usually the data rate throttle. With 8+ players or large builds, the server cannot sync fast enough. See the Performance guide.
For modded servers: ensure all players have the same mods and mod versions installed. A mod version mismatch between client and server causes immediate disconnects.
For crossplay servers with mods: game-changing mods can crash Xbox and Game Pass clients, which cannot install BepInEx. Run vanilla for mixed-platform groups.
High Ping / Latency
Cause: the server region is far from the player, or the player's own connection is slow.
Choose the region closest to the majority of your players when you order. The order page lists the regions that currently have capacity - it only offers ones a server can actually be placed in.
If one player has high ping but others do not, the issue is that player's connection, not the server. Have them try a wired connection or a different network.
High ping (over 200ms) causes timeouts in Valheim. The game is not tolerant of high latency.
Every player on a crossplay server goes through the PlayFab relay, which adds some latency for everyone rather than only for console players. That is inherent to the backend; turning crossplay off removes the relay but also locks out Xbox and Game Pass players.
Server Shows Online but No One Can Connect
This is rare but can happen if the server process is alive but the world has failed to load.
Check the Console tab for errors. If you see "Failed to load world", or the log never reaches the "Session ... is active" line, the world may be corrupted.
Solution: stop the server, restore from the most recent GameGrid backup, and start again.
If the issue persists after restore, open a support ticket. Include the last 50 lines from the Console tab.
