Removed container, removed template, removed /appdata/valheim. Pulled down a new container let it install.

Still get the same error:

Stack overflow in unmanaged: IP: 0x147ca418590a, fault addr: 0x555e3bcb582b

Using the server browser in-game, there is a red X over both the WAN and Local IP of the server. So it is for sure not starting.

13 hours ago, Falzaren said:

Open terminal, type mc then hit enter to open midnight commander.

Find where your server files are backed up to (for me, it was /mnt/user/appdata/valheim/.config/unity3d/IronGate/Valheim).

Copy those files to where Valheim files are stored on your cache (for me, identical path as above but /mnt/cache instead of /mnt/user).

may as note, this is NOT a good idea as this can end in a ... lets say "complete loss or desaster"

you where lucky now as the files where on /mnt/user0/ (array hdd only) and you moved them back to /mnt/cache/

for the future, only use /mnt/user0/ <> /mnt/cache/ instead, or even better /mnt/diskN/ while N is the real disk like 1, 2, 3, ...

and even better, read the manual to understand your Share settings and your mover settings, prolly the mover has kicked in and moved data from /mnt/cache > /mnt/user0/ and your docker is "hard" configured to /mnt/cache only instead /mnt/user/...

if you hard set your docker to /mnt/cache/... make sure the Share is also a primary only /mnt/cache/ Share with no secondary array or pool setup, otherwise data will be moved (scheduled) and your docker which is looking in /mnt/cache/ only ... wont find them anymore ...

I've set the container to host from bridge and still getting the error(s). I've also re-booted the Unraid server... .still same errors.

On 9/18/2026 at 2:21 AM, alturismo said:

may as note, this is NOT a good idea as this can end in a ... lets say "complete loss or desaster"

you where lucky now as the files where on /mnt/user0/ (array hdd only) and you moved them back to /mnt/cache/

for the future, only use /mnt/user0/ <> /mnt/cache/ instead, or even better /mnt/diskN/ while N is the real disk like 1, 2, 3, ...

and even better, read the manual to understand your Share settings and your mover settings, prolly the mover has kicked in and moved data from /mnt/cache > /mnt/user0/ and your docker is "hard" configured to /mnt/cache only instead /mnt/user/...

if you hard set your docker to /mnt/cache/... make sure the Share is also a primary only /mnt/cache/ Share with no secondary array or pool setup, otherwise data will be moved (scheduled) and your docker which is looking in /mnt/cache/ only ... wont find them anymore ...

Thanks for the help!
I do need to spend more time learning more about how shares and the mover works on Unraid, as well as generally how to work with the filesystem structure on Linux.
I'll edit my post to reflect your advice so that future readers don't unintentionally lose data.

Edited 20 hours ago20 hr by Falzaren
grammar