Valheim Troubleshooting
This guide covers common issues you may encounter when running a Valheim dedicated server, including connection problems, world loading failures, and mod-related errors. For initial server configuration, see Valheim Dedicated Server Setup Guide. For mod installation steps, see Valheim Mod Installation Guide.
Server Not Showing in the Server Browser
Cause: The Steam server browser discovers servers via the query port, not the game port. If the query port is blocked or not correctly mapped, the server will not appear in any server list even if players can connect directly.
Solution: Open GPanel and go to the Network tab. Confirm that both your game port and query port are listed and correctly assigned. If you are unsure of your ports, see How to Find Your Server IP and Port. Use the Steam Favorites method (described in the setup guide) to connect directly while troubleshooting server list visibility.
Solution: Open GPanel and go to the Network tab. Confirm that both your game port and query port are listed and correctly assigned. If you are unsure of your ports, see How to Find Your Server IP and Port. Use the Steam Favorites method (described in the setup guide) to connect directly while troubleshooting server list visibility.
Server Refuses to Start Due to Password Error
Cause: The password is fewer than 5 characters, is empty, or contains the server name as part of the password string.
Solution: Go to the Startup tab in GPanel and update the
Solution: Go to the Startup tab in GPanel and update the
Password variable. Ensure it meets all of the following requirements:
- At least 5 characters long
- Does not contain the
ServerNameas a substring - Not left blank
World Not Loading / New World Generated Instead
Cause: The
Solution:
WorldName startup variable does not match the filename of the world files, or only one of the two required world files (.fwl or .db) is present.
Solution:
- Connect via SFTP and navigate to:
/.config/unity3d/IronGate/Valheim/worlds_local/ - Confirm that both
<WorldName>.fwland<WorldName>.dbare present. - Verify that the
WorldNamestartup variable in GPanel exactly matches the filename (case-sensitive, no extension). - If a new world was generated, stop the server, delete or rename the newly created world files, restore your backup files, and restart.
Players Cannot Connect
Cause: There are several possible reasons players cannot connect to a Valheim server.
Solution: Work through the following checks:
Solution: Work through the following checks:
- Server is still starting: Valheim can take several minutes to fully start, especially with mods. Wait until the console shows the server is ready before connecting.
- Wrong port: Players connecting via the in-game browser should use the game port. Players adding the server through Steam Favorites should use the query port. Check the Network tab in GPanel for your assigned ports.
- Password mismatch: Ensure players are entering the correct server password. Passwords are case-sensitive.
- Mod version mismatch: If Valheim Plus or other enforced mods are installed, all players must have the exact same version. See the Mod Installation Guide for details.
BepInEx Mods Not Loading
Cause: BepInEx files were placed in the wrong directory, or the doorstop library is missing from the server root.
Solution:
Solution:
- Verify via SFTP that the
BepInEx/folder is in the server root directory alongsidevalheim_server.x86_64. - Verify that the
doorstop_libs/folder also exists in the server root and containslibdoorstop_x64.so. On Pterodactyl-based panels the doorstop is loaded via environment variables — arun_bepinex.shscript is not used and does not need to be present. - Check that your mod
.dllfiles are insideBepInEx/plugins/, not in the root or any other subdirectory. - Restart the server and check the server console log for BepInEx initialization messages or error output.
The expected directory layout is:
/ (server root)
valheim_server.x86_64
BepInEx/
plugins/ ← mod .dll files go here
config/
patchers/
doorstop_libs/
libdoorstop_x64.soServer Crashing or Unstable After Adding Mods
Cause: A mod is incompatible with the current Valheim version, conflicts with another mod, or is misconfigured.
Solution:
Solution:
- Check the server console output in GPanel for error messages that reference a specific mod or plugin name.
- Remove all mods from
BepInEx/plugins/and restart the server to confirm it runs cleanly without mods. - Re-add mods one at a time, restarting between each, to identify which mod causes the crash.
- Check the mod's Thunderstore or Nexus page for compatibility notes and required dependencies.
After a Valheim game update: Mods may break until their authors release updated versions. If your server was stable before an update and crashes after, temporarily remove mods until updated versions are available.
Crossplay Not Working
Cause: The crossplay startup variable is not enabled, or mods are interfering with crossplay functionality.
Solution:
Solution:
- Go to the Startup tab in GPanel and set
ENABLE_CROSSPLAYto1. - Restart the server.
- Note that most BepInEx mods are not compatible with crossplay. If you have mods installed and crossplay players cannot connect, you may need to choose between mods and crossplay support.
Related Articles
- Valheim Dedicated Server Setup Guide — Startup configuration, connecting, and world saves
- Valheim Mod Installation Guide — BepInEx, Thunderstore, and Valheim Plus
- How to Find Your Server IP and Port
- How to Upload Files via SFTP
If you continue to experience issues after following this guide, our support team is available to help. Open a support ticket and include your server's GPanel details, a description of the problem, and any error messages from the server console.
