I had the container already, playing again for the first time in a while. I had this error message, which persisted even after deleting the appdata/valheim folder and letting it redownload:

---Start Server---

Stack overflow in unmanaged: IP: 0x14617238590a, fault addr: 0x55827ebb072b

[S_API] SteamAPI_Init(): Loaded local 'steamclient.so' OK.

Setting breakpad minidump AppID = 892970

SteamInternal_SetMinidumpSteamID: Caching Steam ID: 76561197960265728 [API loaded no]

[S_API FAIL] Tried to access Steam interface SteamNetworkingUtils004 before SteamAPI_Init succeeded.

I fixed by changing the Container Variable: WORLD_NAME to a different name (I kept the same Container Variable: SRV_NAME ) then restarted the container. Server now starts with no errors, and I am able to connect.

14 hours ago, squanky said:

this server

About what container are we talking?

10 hours ago, sirphr said:

Fresh Install.. nothing changed.

What container? When we are talking about Valheim, this isn't an error, the server is running as it should, this is just a warning and the Steam API was initialized correctly.

1 hour ago, BeeMan said:

Also seeing the same error as @sirphr on a fresh install

What exact error, this isn't an error, have you yet tried to connect to the server?

This is my server and it is working perfectly fine, three people are playing on it:

---Prepare Server---

---Server ready---

---Starting Backup daemon---

---Update check deprecated!---

---Start Server---

[S_API] SteamAPI_Init(): Loaded local 'steamclient.so' OK.

Setting breakpad minidump AppID = 892970

SteamInternal_SetMinidumpSteamID: Caching Steam ID: 76561197960265728 [API loaded no]

[S_API FAIL] Tried to access Steam interface SteamNetworkingUtils004 before SteamAPI_Init succeeded.

32 minutes ago, shikinami said:

I fixed by changing the Container Variable: WORLD_NAME to a different name (I kept the same Container Variable: SRV_NAME ) then restarted the container. Server now starts with no errors, and I am able to connect.

Please don't, this is wrong advice and you basically created a new world.

Also this is not an error message, this is just a warning that pops up too late, as you can see first it says that the Steam API was initialized successful and the last message is just a warning that it tried to initialize the Steam API before it even was initialized.

This message is shown on almost every Steam Dedicated server in that order or vice versa.

Please use the container variable WORLD_NAME, not SRV_NAME, my container doesn't support SRV_NAME.

As I already said, a re-download is recommended by the game devs, see my post here:

5 minutes ago, ich777 said:

About what container are we talking?

What container? When we are talking about Valheim, this isn't an error, the server is running as it should, this is just a warning and the Steam API was initialized correctly.

Im talking about the valheim server. I fixed the restarts. Guess it was a server password less than 6 letters. Now the container is up for more than a couple seconds. Still the server dont seem to start correct.

Steam Console Client (c) Valve Corporation - version 1788292693

-- type 'quit' to exit --

Loading Steam API...OK

Connecting anonymously to Steam Public...OK

Waiting for client config...OK

Waiting for user info...OK

Success! App '896660' already up to date.

Unloading Steam API...OK

---Prepare Server---

---Server ready---

---Starting Backup daemon---

---Update check deprecated!---

---Start Server---

Stack overflow in unmanaged: IP: 0x1471a3b8590a, fault addr: 0x557e83ff6bdb

[S_API] SteamAPI_Init(): Loaded local 'steamclient.so' OK.

Setting breakpad minidump AppID = 892970

SteamInternal_SetMinidumpSteamID: Caching Steam ID: 76561197960265728 [API loaded no]

[S_API FAIL] Tried to access Steam interface SteamNetworkingUtils004 before SteamAPI_Init succeeded.

Tried to connect to the server with the local IP of the unraid server. Im in the same network. Do I need to use br0 custom IP for the server to work? At the moment I use the bridge mode.

20 minutes ago, squanky said:

Stack overflow in unmanaged: IP: 0x1471a3b8590a, fault addr: 0x557e83ff6bdb

This is the only thing that is a real error.

May I ask on what Unraid version are you?

Please also try to restart your whole Unraid server.

I'm not to sure what causes this line but something is definitely off, the other lines are fine.

17 minutes ago, ich777 said:

This is the only thing that is a real error.

May I ask on what Unraid version are you?

Please also try to restart your whole Unraid server.

I'm not to sure what causes this line but something is definitely off, the other lines are fine.

It's working now. I was on unraid 7.1.2. Updated to 7.3.2. The stack overflow error still appeares but the server worked. I will test it futher

Since valheim doesn't have your stereotypical server config file, where would i go about changing settings such as normal, hard, no portals etc? I thought you changed the parameters in the .sh file, but cant seem to find the currect one

I'm also getting this:

steamcmd.sh[17]: Starting /serverdata/steamcmd/linux32/steamcmd

steamcmd.sh[45]: Starting /serverdata/steamcmd/linux32/steamcmd

Stack overflow in unmanaged: IP: 0x(something), fault addr: 0x(something)

[S_API] SteamAPI_Init(): Loaded local 'steamclient.so' OK.

Setting breakpad minidump AppID = 892970

SteamInternal_SetMinidumpSteamID: Caching Steam ID: 76561197960265728 [API loaded no]

[S_API FAIL] Tried to access Steam interface SteamNetworkingUtils004 before SteamAPI_Init succeeded.

src/clientdll/cminterface.cpp (2253) : !BLoggedOn()

The gameserver is running fine (unraid 7.3.2), but the stack overflow message always pops up when I start the container. 🤔

Edited September 12Sep 12 by DogeKitteh007
additional info

11 hours ago, schindlj said:

Since valheim doesn't have your stereotypical server config file, where would i go about changing settings such as normal, hard, no portals etc? I thought you changed the parameters in the .sh file, but cant seem to find the currect one

You can add it in the GAME_PARAMS variable field.

For example:

-modifier combat hard -modifier resources more -setkey playerevents

Just do a google search to find all the different modifiers and such.

Correct me if I'm wrong though. Can't test it right now. 🥲

The only way I could get v1.0 to work was by forcing the update from GAME_PARAMS: steamcmd +force_install_dir "/home/steam/steamapps/valheim1.0" +login "anonymous" +app_update "896660" -beta public validate +quit

I had a fresh install and tried all of the above suggestions and none of them worked. ich777 said their server is running "AppID = 892970" (the non-server version?) which isn't the AppID used in the container (896660). I did a fresh install with AppID 892970 and added my steam credentials but that caused the container to infinitely restart.

I'm not sure why there's a mismatch between the public releases since it shows them releasing within the same minute from each other. Dedicated server last public release: 11 September 2026 – 13:08:29 UTC, Base game last public release: 11 September 2026 – 13:08:45 UTC

Edited September 13Sep 13 by Oroshi
I was incorrect about game release times.

6 hours ago, Oroshi said:

I had a fresh install and tried all of the above suggestions and none of them worked. ich777 said their server is running "AppID = 892970" (the non-server version?) which isn't the AppID used in the container (896660). I did a fresh install with AppID 892970 and added my steam credentials but that caused the container to infinitely restart.

Please don't change the AppID just leave the credentials out, you are making your life harder that it is.

When the credentials marked as not as required (with the red asterisk) then they aren't needed and therefore they broke the game download because you've specified them.

Again, if the download fails or the container won't upgrade, simply:

1. Stop the container

2. Delete the steamapps folder

3. Start the container again

As for Valheim make also sure you are using at least a six character password and also make sure that the password only consist of alphanumeric characters and letters.

I can't seem to connect to my valheim server anymore from the game after the 1.0 update.

I've tried the suggestions of deleting the steamapp folder, I've removed and reinstalled the Valheim server docker. Updated the Unraid version from 7.2.3 to 7.3.2. Removed the mods I had on client and in game (BepInEx remained enabled however). Verified the map converted successfully on singleplayer, regardless trying a new map with no mods installed (just bepinex enabled) doesnt let me connect either. Both versions of BepInEx are matching.

Password is over 8 characters.

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.

The behaviour is I get the spinning connecting screen then boots me back to the main menu. No password Screen.

DockerLog.txt

Edited September 14Sep 14 by Deeppurp

re:Valheim, if you're having trouble I'd suggest putting -logFile log.txt in your GAME_PARAMS. seems that the actual server output doesn't make it to the container log, and it's hard to debug anything if you can't tell what it's doing :)

3 hours ago, buck2202 said:

re:Valheim, if you're having trouble I'd suggest putting -logFile log.txt in your GAME_PARAMS. seems that the actual server output doesn't make it to the container log, and it's hard to debug anything if you can't tell what it's doing :)

Appreciate this! Will give it a try and see what its putting out.

Edit: attached

Game_paramlog.txt

Edited September 15Sep 15 by Deeppurp
attaching log after adding log string to game param

I think FoodCustomizer is a mod, looks like it's still loading and is throwing errors? unsure if its issue is fatal to the server, but it's throwing a NullReferenceException near the end of your log. I'd probably try to track that down

Hey all,

Been having this issue with the Palworld version for the last two big updates. When I restart the container to grab the latest version, I get a failure with this error message. Creating a new one sometimes fixes it, but today it didn't. Obviously making a new container and porting things over isn't the best, so I'd be curious on what the issue might be and if anyone else has dealt with this. Thanks!

Connecting anonymously to Steam Public...OK

Waiting for client config...OK

Waiting for user info...OK

Update state (0x0) unknown, progress: 0.00 (0 / 0)

Error! App '2394010' state is 0x26 after update job.

Unloading Steam API...OK

Sometimes the error is 0x226. Previously my whole app got wiped out, but the backups and saves were safe, but this time it looks like it's still installed and just defaulting to the old version (v1.0.4.102642).

I've got steamcmd in /mnt/user/appdata/ and palworld in /mnt/cache/appdata/, per the defaults from the container. Plenty of space in the array, so I don't think that's it.

28 minutes ago, GamingADHD said:

Hey all,

Been having this issue with the Palworld version for the last two big updates. When I restart the container to grab the latest version, I get a failure with this error message. Creating a new one sometimes fixes it, but today it didn't. Obviously making a new container and porting things over isn't the best, so I'd be curious on what the issue might be and if anyone else has dealt with this. Thanks!

Connecting anonymously to Steam Public...OK

Waiting for client config...OK

Waiting for user info...OK

Update state (0x0) unknown, progress: 0.00 (0 / 0)

Error! App '2394010' state is 0x26 after update job.

Unloading Steam API...OK

Sometimes the error is 0x226. Previously my whole app got wiped out, but the backups and saves were safe, but this time it looks like it's still installed and just defaulting to the old version (v1.0.4.102642).

I've got steamcmd in /mnt/user/appdata/ and palworld in /mnt/cache/appdata/, per the defaults from the container. Plenty of space in the array, so I don't think that's it.

I made a new container, copied the v1.04 Palworld server files to /mnt/user/appdata, and deleted the appmanifest file. That all seems to have worked perfectly. I'm patched to v1.05 and off to the races. At this point, I'm thinking I'm just a doofus for not noticing /mnt/cache/ was a bad idea at install time.

If so, I will acknowledge the failure. I will live in the failure. And I will let the failure make me stronger.

Otherwise, I am definitely open to suggestions.

17 hours ago, buck2202 said:

I think FoodCustomizer is a mod, looks like it's still loading and is throwing errors? unsure if its issue is fatal to the server, but it's throwing a NullReferenceException near the end of your log. I'd probably try to track that down

Happening regardless, however does not affect the map or client game. I've attempted without mods installed.

On 9/10/2026 at 4:59 AM, ich777 said:

This is the only thing that is a real error.

May I ask on what Unraid version are you?

Please also try to restart your whole Unraid server.

I'm not to sure what causes this line but something is definitely off, the other lines are fine.

I think I am having the same issue that Squanky described. My logs also have the line that starts with "Stack overflow in unmanaged:

When I try to connect to the server I get a few seconds of the game trying to connect, then get booted back to the main menu without a password box ever popping up.

I reset my Valheim server after the 1.0 launch and have been playing on the server with a few friends without issue until today (it was working fine just yesterday).

We are all connecting via Tailscale.
I'm currently in the process of updating from Unraid 7.2.4 to 7.3.2 since that worked for Squanky, will report back with results of that.
Appreciate that you're still active on these forums and helping us folks troubleshoot, ich777!

edit:
Updating to Unraid 7.3.2 didn't fix things.
I also stopped the Valheim container, deleted the steamapps folder, started the container again, as you suggested earlier. That didn't seem to help either.

Not sure if this will help or not, but here are what my logs look like when I try to connect to the server.
I've noticed that the logs window auto-closes itself after my game has tried to connect to the server and failed, is that normal behaviour? I'm managing things via remote access on my windows PC using the Unraid webGUI.

Edited September 17Sep 17 by Falzaren

Also having the same issue with the Unmanaged IP error. Running Unraid 7.3.2 and running the container in Bridge mode. Client refuses to connect either via Local IP or WAN

I also get the unmanaged IP error, however it doesn't prevent anyone from joining. I am running with BepinEx set to true, I had mods installed, the error pops up on occasion but I have had multiple people play without issues at all.

34 minutes ago, MrBeardSmith said:

I also get the unmanaged IP error, however it doesn't prevent anyone from joining. I am running with BepinEx set to true, I had mods installed, the error pops up on occasion but I have had multiple people play without issues at all.

Strange. I, and others, can't get anyone to join - yet you have no issues with the same error......

Update from my post yesterday re: being unable to connect to my Valheim server.
Without changing anything since I last tried troubleshooting yesterday without success (see my earlier post for details), I am now able to connect.
However, the server that we've been playing on all week seems to be deleted; I loaded into a brand new server. (ouch).

The only thing that I did, which I am clueless whether it had any impact, was in Undraid under Settings, then Tailscale, then Status tab, I clicked "Ping" beside the line entry for my Valheim server.
Before I clicked ping, the server status was listed as Idle. It immediately established a connection and changed to Active, showing a Direct connection.
The status returned to Idle fairly shortly after I logged out of the server.

Here are my logs from today, after I successfully logged into the server.


I had the foresight to copy + paste everything I could find stored under /mnt/cache/appdata/valheim to my windows PC yesterday, so hopefully I can restore the server and not lose out on a half dozen or so hours of game progress.
I did notice that the most recent tar.gz files (someone please correct me if these are not the server backup files) had been saved Sept 13th, despite us playing on the server up until Sept 15th. I'm not sure what to make of that.

edit: the tar.gz files were NOT on mnt/cache, I found them under mtn/user/appdata/valheim.
I have just discovered a whole bunch of files in /mnt/cache/appdata/valheim/.config/unity3d/IronGate/Valheim that look like backups to my non-tech-savvy eye.
These files date back months. Now I'm unsure how to go about moving any files to restore the server we were playing on earlier this week.

If anyone could offer some suggestions I would greatly appreciate it!

edit 2: we're back! Successfully restored the world we were playing on earlier this week. For anyone who stumbles across this in the future, and is a Linux/Unraid newbie like me, here's what I did:

Stop all docker containers. Disable docker in settings.

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).
In my case, I had some backup files that were created AFTER my server was wiped and a new server was created (just today), so I deleted those files. Just use the date/timestamps as your guide.
Hope this can help someone!

edit 3: per the reply from @altrusimo below, the above steps could cause data loss and are not the recommended way to go about things. See their post for more details, as well as the post from @MrBeardSmith below for a simpler way to have your backups set up.

Edited September 20Sep 20 by Falzaren
adding additional information for troubleshooting

1 hour ago, Falzaren said:

edit: the tar.gz files were NOT on mnt/cache, I found them under mtn/user/appdata/valheim.
I have just discovered a whole bunch of files in /mnt/cache/appdata/valheim/.config/unity3d/IronGate/Valheim that look like backups to my non-tech-savvy eye.
These files date back months. Now I'm unsure how to go about moving any files to restore the server we were playing on earlier this week.

If anyone could offer some suggestions I would greatly appreciate it!

You should be able to just name the world the same thing as what your .config folder is called and have it automatically picked up.

Right now my game is pointed at "/mnt/user/USERNAME/valheim(1.0)" and within that folder I have exactly what you have a .config folder that leads up to "valheim(1.0)\.config\unity3d\IronGate\Valheim\worlds_local\GAMENAME"

So you should again, in theory set up a docker to point to your Valheim folder with the same gamename and it will sort itself out for you.