Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[Support] ich777 - Gameserver Dockers

Featured Replies

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.

  • Replies 12.6k
  • Views 2.3m
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • Just thought I'd share my experience setting up a Valheim server with this docker app from @ich777(thank you!)   You don't need to worry about Steam authentication for Valheim, the default a

  • Dockers Available:   SteamCMD DedicatedServers: CounterStrike: Source CounterStrike 2 TeamFortress 2 ArmA3 - requested by @MrSage Deathmatch Classic

  • This will hopefully shed some light on the underside working bits of building a cluster of servers for ARK:SurvivalEvolved.   With the inspiration (read thievery) from @growlith I present th

Posted Images

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 by Falzaren
grammar

  • Author
On 9/15/2026 at 12:19 AM, Deeppurp said:

Attached is the docker log, I can't locate anything that indicates what the issue could be. Im on the same LAN and subnet as the server as well.

Please disable BepInEx.

18 hours ago, ich777 said:

Please disable BepInEx.

I had already tried turning it on/off... it didn't make a difference on mine. Still the same error message: Stack overflow in unmanaged: IP: 0x1465dab8590a, fault addr: 0x55fa7842d26b

As of today, my Valheim connection issues have returned.

Logs are still showing the line beginning with "Stack overflow in unmanaged..."

Very bizarre, for my server to go from being unable to connect, to working fine for several days, then back to being unable to connect again.

  • Author
6 hours ago, CoZ said:

I wiped out everything from ich777 container and pulled down the above. The server starts fine with no issue. Maybe @ich777 can take a look at the above container and see what is different between the two?

If my container isn't working for you please try the other one, I simply can't tell why it on some machines doesn't work.
Maybe it's the path or better speaking the mount point or something else, I really can't tell.

For me it works just fine.

6 hours ago, ich777 said:

If my container isn't working for you please try the other one, I simply can't tell why it on some machines doesn't work.
Maybe it's the path or better speaking the mount point or something else, I really can't tell.

For me it works just fine.

Using the other container almost feels like cheating on you...your Valheim Container and I have been together for so long. ;)

I do not WANT to use the other container.... but, it appears I HAVE to.

I get these errors as well:

Stack overflow in unmanaged: IP: 0x14dfe318590a, fault addr: 0x555a4ed4699b

But I have since start and I'm been using it for over a year. Despite the message, the server starts anyway. I never really cared about it and dunno if it matters P

I'm running two servers from two separate docker containers.

On 9/26/2026 at 5:32 AM, FlamongOle said:

I get these errors as well:

Stack overflow in unmanaged: IP: 0x14dfe318590a, fault addr: 0x555a4ed4699b

But I have since start and I'm been using it for over a year. Despite the message, the server starts anyway. I never really cared about it and dunno if it matters P

I'm running two servers from two separate docker containers.

That's crazy! You have the same exact error but yet your server starts and, is connectable. What in the Sam Hill is going on? LOL

  • Author
On 9/25/2026 at 2:24 PM, CoZ said:

Using the other container almost feels like cheating on you...your Valheim Container and I have been together for so long. ;)

I do not WANT to use the other container.... but, it appears I HAVE to.

Sorry but I can't reproduce this error nor do I know why this happens.

I run the container on my own Server (granted I'm not on Unraid anymore) and have no issues whatsoever.

On 8/26/2019 at 11:19 PM, ich777 said:

Yes, this is totaly possible and i think it was already requested but since the game files (or at least the server game files) are not opensource or to download for everyone i wouldn't do such a server. My dockers are built for easy use and not having to do much (except for FiveM, recently the developers added a captcha to the download so you must put the archive in the main directory of the server).

There are a bunch of dockers out there and you easily can get them to work with unraid.

is it possible to get an UT2004 Server, the game is officially free now

My server had an unexpected reboot last week, I could connect locally but looking on steam the server was not up. I am now getting the same Stack overflow error. Tried most things to resolve, real shame as was very much enjoying using valhiemPlus! Ive had to wipe and use a different application install from the app store for vanilla.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.