Valheim server troubleshooting: crashes, lag, no console

A practical guide to Valheim server problems: crash-on-start, in-game lag, mod conflicts, and the no-console reality that catches new admins out.

Valheim server troubleshooting, in plain English

Valheim server problems tend to fall into four buckets: the server won't start, the server runs but feels laggy, a mod is misbehaving, or someone's trying to do something Valheim simply doesn't allow (like open a console). This doc walks each in turn.

Server won't start

Three causes cover almost every "stuck at boot" case.

A BepInEx mod is missing a dependency

By far the most common one. You installed Mod A, which needs Mod B (Jotunn, a Common library, or another framework mod). Without B, A throws on load and BepInEx stops the chain.

Look at the boot log in the dashboard. You'll see a red line like Plugin X requires Y v1.2.3 or later, found none. Install the missing dependency from the Thunderstore browser and restart. If you installed through the dashboard browser, it should have resolved this automatically, so this normally only bites manual installs.

World save corruption

Rare, but it happens, usually right after a big Steam patch or a hard crash mid-save. Valheim saves the world to /data/worlds_local/yourworld.db and .fwl; if either gets truncated, the server loops on start.

The fix: roll back to yesterday's automatic backup, or your most recent manual one. Dashboard → Backups → restore. We snapshot the volume before any restore, so you can undo the undo if it goes wrong.

Port collision

If you've spun up two Valheim servers and they ended up assigned the same port (extremely rare on Hostd because we auto-allocate), the second one will fail to bind. The boot log says Address already in use. Contact us via a ticket and we will sort through it with you.

Lag and rubber-banding

Valheim's lag patterns are different from Minecraft's. There are three that dominate.

Sail-induced lag

This is the classic. Long sailing trips force the server to generate and stream brand-new biomes as you cross the world. Players sailing into unloaded territory will see the boat juddering, fish popping in, and the occasional brief freeze. There's no real fix, it's how the engine works. Pre-generation isn't a thing in Valheim the way it is in Minecraft.

What you can do: build a hub of stone portals so your group only sails once per route. Subsequent journeys are instant.

A base that's outgrown its biome

Valheim tracks every build piece, every dropped item, and every container as a persistent object. A base with thousands of pieces and a floor covered in stray items will start hitching even on a fresh server. If your TPS-equivalent feels off when you're at base but fine in the wild, this is it.

Fixes, in order of effort: pick up dropped items, demolish unused outbuildings, split a megabase into two with a portal between them. The Valheim engine isn't designed for Minecraft-scale builds.

Portal spam

Every active portal pings the server. A dozen unused portals in a portal room each add load. Tear down the ones you don't actively use; tag the survivors clearly.

Mod conflicts

When the server starts but acts strangely (items missing icons, recipes broken, players invisible), the answer is almost always a mod conflict.

  1. Uninstall the most recently added mod from the dashboard.
  2. Restart.
  3. Watch the console panel for the Loaded N plugins line and any red Exception traces.
  4. If the problem goes away, you've found it. Check the offending mod's Thunderstore page for known conflicts.
  5. If it doesn't go away, repeat with the next-most-recent mod.

Don't uninstall all your mods at once; you'll lose track of which one was the culprit and have to rebuild the list from scratch.

For deeper guidance, see Installing Valheim mods with BepInEx and Thunderstore.

"There's no console available": yes, that's correct

This catches more new Valheim admins than anything else, so let's be upfront:

Valheim does not expose a server console or RCON. The game's engine doesn't have one. We don't hide it, we don't gate it; it simply doesn't exist. That means:

  • You cannot send admin commands to a running Valheim server from the dashboard.
  • You cannot kick or ban players from the dashboard, mid-game.
  • You cannot save the world on demand from the dashboard (the server auto-saves on a schedule and on graceful stop).
  • Scheduled "send chat message" or "run command" tasks don't exist for Valheim.

Some mods (like ServerCharacters or AdminCommands) add their own in-game admin tooling, but that runs through the Valheim client, not the host. If you need to kick someone, do it from your own client in-game using adminlist.txt and the in-game F5 console.

What you can schedule, because it's a container-level action:

  • Scheduled Restart (good for nightly maintenance).
  • Scheduled Stop (e.g. shut down overnight on weekdays).
  • Scheduled Start (pair with the above).

That's it. If you've used a Rust or Minecraft server before, this asymmetry will feel weird; it's just the game's reality.

See Why some scheduled commands are blocked for the general principle.

No crossplay attempts

Now and then someone tries to add an Xbox or PlayStation friend. Valheim doesn't support PC-to-console crossplay. Both ends must be on PC (Steam client). The game isn't even on consoles in the same shape, so there's nothing to configure on our side.

Before any risky change, back up

Modlist rewrites, big config edits, world imports: take a manual backup first. Dashboard → Backups → Take backup now. It takes seconds and it has saved more weekends than we can count. See Manual backups.

Next steps

Last updated 2026-05-20. Notice a mistake? Tell us.

Cookies

We use a few cookies that are strictly necessary to sign you in and keep your account secure. We do not load any advertising or third-party trackers. We would also like to run our own cookieless analytics so we can understand which pages are useful. See our Cookie Policy for the full list.