This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

Frequently Asked Questions (FAQ)

This page answers common questions about installing, running, updating, modding, and backing up the Managed Valheim server. It is designed to help new users and administrators quickly resolve typical issues.

General Questions

What is Managed Valheim?

Managed Valheim is a fully automated, self-updating Valheim dedicated server container with built-in BepInEx support, modding compatibility, and automated world backups. It is designed for TrueNAS SCALE and other OCI platforms.

Does the server update automatically?

Yes. Every time the container starts, SteamCMD installs or updates Valheim in /opt/valheim_base, then copies updated files into the modded runtime directory /opt/valheim.

Does the server support mods?

Yes. BepInEx is installed automatically, and mods can be placed in:

/opt/valheim/BepInEx/plugins

Installation & Configuration

Which volumes are required?

/config — configuration and metadata
/backups — world backup storage

Which ports need to be exposed?

Valheim requires three UDP ports:

2456/udp
2457/udp
2458/udp

Which environment variables are required?

At minimum:

SERVER_NAME
WORLD_NAME
SERVER_PASSWORD
PUBLIC

Modding

Where do I install mods?

Mods go into:

/opt/valheim/BepInEx/plugins

Will mods break updates?

No. The clean install directory (/opt/valheim_base) is kept separate from the modded runtime directory (/opt/valheim), so SteamCMD updates are always safe.

Where are mod configuration files stored?

Many mods generate configs under:

/opt/valheim/BepInEx/config

Backups

Does the server create backups automatically?

Yes. The container creates timestamped ZIP backups at a configurable interval and prunes old backups based on retention settings.

Where are backups stored?

Backups are stored in:

/backups

Does Valheim create its own backups?

Yes. Valheim maintains up to 5 rolling internal backups in:

/root/.config/unity3d/IronGate/Valheim/worlds_local/<WORLD_NAME>

These include files like:

<WORLD_NAME>.db
<WORLD_NAME>.fwl
<WORLD_NAME>_1.db
<WORLD_NAME>_2.db
<WORLD_NAME>_3.db
<WORLD_NAME>_4.db
<WORLD_NAME>_5.db

Restoring Worlds

How do I restore from a container backup?

Stop the TrueNAS SCALE app.
Extract the ZIP file from /backups.
Copy the world directory into:
/root/.config/unity3d/IronGate/Valheim/worlds_local/<WORLD_NAME>
Start the app.

How do I restore from Valheim’s internal backups?

Stop the app.
Choose one of the numbered _X.db files.
Replace the main .db and .fwl files.
Start the app.

Connectivity

Why can't players join?

Check firewall rules for UDP 2456–2458.
Verify the server password.
Ensure PUBLIC=1 if using public listing.

Why doesn't the server appear in the browser?

Public listing may take time to propagate.
Use direct connect via IP and port.
Check NAT or port forwarding.

Performance

Why is the server lagging?

Too many mods or heavy plugins.
Insufficient RAM or CPU on the host.
Mod conflicts causing errors in BepInEx logs.

Updates

Do I need to manually update the server?

No. SteamCMD updates Valheim automatically on each container start.

Do I need to update BepInEx manually?

No. The container downloads and installs the latest BepInEx pack automatically.

Next Steps

This FAQ will expand as new features and versions are released.