47 minutes ago, kerpster said:

Palworld docker not updating
any idea what is holding up the docker from updating to the latest version? i have tried stopping and restarting the docker as well as removing the steamcmd folder so it rebuilds and updates but it wont but from the pre 1.0 version.

Just came here to say this. Docker will not update Palworld to 1.0. Note: It is out of early access and 1.0 now. Did all the things (restart docker, stop/start, validate)

13 minutes ago, scubafossil said:

Just came here to say this. Docker will not update Palworld to 1.0. Note: It is out of early access and 1.0 now. Did all the things (restart docker, stop/start, validate)

Also getting the same all day but just fixed it, delete the container and appdata and it forces it to fully reinstall/update.

4 hours ago, JButcher said:

Also getting the same all day but just fixed it, delete the container and appdata and it forces it to fully reinstall/update.

Specifically, you should only need to delete appmanifest_2394010.acf from the palworld container's steamapps folder then restart the container. That's all I deleted and got mine updated to 1.0.

23 hours ago, bamcgregor89 said:

Specifically, you should only need to delete appmanifest_2394010.acf from the palworld container's steamapps folder then restart the container. That's all I deleted and got mine updated to 1.0.

you are an absolute genious.... i love you!

I was looking around for a Palworld Docker container and found this.

I just wanted to add, we were having the same issues with SteamCMD not recognizing updates for a Windrose docker container, and having to also delete the Appmanifest_*.acf however after adding a Validate variable to the container, it forces a refresh check for updates each time the server is restarted .

Not saying it will be the solution here, but it might, and won't hurt anything to add:

Seeking your guidance.
I have downloaded Palword from Apps with no modifications.  
Gave it time to download and watched it in the logs -- no issues.
The Docker is up and running.
I have stopped it to change the ini files:
    hoping to change teh Server Name, Password, Admin Password -- then planned on logging in.

Well, I went to where the files should be and I am baffled.

/mnt/cache/appdata/palworld

I can not seem to find this folder.

I do fave the shares set for primary storage to Cache-nvme -- and other apps do appear here get moved appropriately, I think.

Secondary storage is set to Array 
Mover action is set to Array -> Cache-nvme

Yet for the life of me I can not find my Pal

I have removed it and have reinstalled and continue to have the same issue, cant seem to find the folder so I can access the ini file.

Appreciate any help you can give.

I hope I can get some help. I installed the palworld docker. I have it set to bridge and can connect once but then I cannot reconnect until I restart the docker. If I set it to br0 and set a static IP it will not connect at all. How can I set it so that I can log out of the game and back in without restarting the docker?

I am having issues with Palworld as well. Started a fresh docker this morning, and when connecting directly via LAN IP im stuck at a black screen. Any recommendations?

EDIT: I got it working. in the PalWorldSettings.ini the bIsMultiplay was set to false. Needed to change to true (bIsMultiplay=True).

Edited July 13Jul 13 by IaMs12

My palworld dedicated server is not updating to latest version is there something i can type into the palworld docker console or something i can do to FORCE UPDATE the app inside the docker. (I have shut down and rebooted the server multiple times) The docker/server just wont update. How can i force the update please ?

I have tried this "steamcmd +login anonymous +app_update 2394010 validate +quit" but it does nothing....

Game version is v1.0.0.100427 (old version) NOW UPDATED > Game version is v1.0.1.100619

EDIT: SO I DID WHAT THIS PERSON SUGGESTED AND IT WORKED, I WENT INTO THE APPDATA, WENT INTO PALWORLD, FOUND THE STEAMAPS AND RENAMED IT TO OLD_STEAMAPPS AND THEN TURNED ON THE SERVER AND FIXED...

"I had this issue and read somewhere to delete the "steamapps" folder in appdata. I just renamed it and restarted container and it pulled the new version. All save data and settings remained."

Palworld server wont Update : r/unRAID

Edited July 15Jul 15 by kaaizen

22 minutes ago, kaaizen said:

My palworld dedicated server is not updating to latest version is there something i can type into the palworld docker console or something i can do to FORCE UPDATE the app inside the docker. (I have shut down and rebooted the server multiple times) The docker/server just wont update. How can i force the update please ?

Ditto on this.
Game Version v.1.0.1.100619
Server Version v1.0.0.100427

Have tried to change my GAME-ID tag in the docker container to 2394010 -beta 24181105 (latest version on here: https://steamdb.info/app/2394010/patchnotes/)

Edited July 15Jul 15 by TCW_NZ

Does some found a solution for the update? ... I want to play Palworld 😅🥲

SOLUTION FOUND:

1. Stop Server

2. Rename under ".\appdata\palworldServer\steamapps --> "appmanifest_2394010.acf" to "_appmanifest2394010.acf_temp"

3. Start Server - Update will be installed🥰

Edited July 15Jul 15 by Schmidij_ch

Palworld will not auto update when i restart the docker container.

Hopefully my issue is more fun to resolve
I have 2 palworld instances. First one runs just fine. Second one, I have set to port 8213 as I want to run more than one world. I have the port set both in docker settings and the .ini file. However when it launches, the logs say it's still running on port 8211. How can I correct that? Thanks.

3 hours ago, Schmidij_ch said:

Does some found a solution for the update? ... I want to play Palworld 😅🥲

SOLUTION FOUND:

1. Stop Server

2. Rename under ".\appdata\palworldServer\steamapps --> "appmanifest_2394010.acf" to "_appmanifest2394010.acf_temp"

3. Start Server - Update will be installed🥰

3 hours ago, whitewraith said:

Palworld will not auto update when i restart the docker container.

inside Palworld container --> advanced view (if u using unraid) --> then look for parameter called validate set it to "true" once you enable it then apply changed your container will restart and download the updates forcibly, once its done better to disable so the server wont take long to restart later if you have scheduled daily restart.

Could you add tailscale support to the palworld container?

idk if anyone will see this. But, has ANYBODY figure out how to update the games? I downloaded the Palworld docker steamcmd app. It wont update when I restart the game.

On 7/18/2026 at 12:48 AM, mehmeh123 said:

idk if anyone will see this. But, has ANYBODY figure out how to update the games? I downloaded the Palworld docker steamcmd app. It wont update when I restart the game.

There is a solution like 3 messages above your question.

I can't seem to get my Palworld docker to work correctly.
I get it setup where it shows up on the community server list but it does not allow me to connect from the community server list. I can not connect via the public ip:8211 the only connection I get is via local Ip for the container (192.168.1.05:8211).

I have deleted the directories and freshly installed them. I changed the "PalworldSettings" and set "bIsMultiplay=True" and changed the server name and password.

I have changed the Port in my port settings, server settings etc. My port settings set to my local Unraid device's Ip (192.168.1.10) which is running the docker on a container (192.168.1.05:8211).

Attached is my docker settings, my router port fowarding settings, the message I get when i try to join via community servers, and the Server config file.
Any help is greatly appreciated. Thank you :)

On 5/25/2024 at 4:17 AM, vollekanne said:

 

Finally, i got it 😀

 

the guides want you to add the workshop folder inside your galaxie

appdata/avorion/galaxies/yourgalaxyname/workshop

 

but this did not work

after i created the workshop folder in appdata/avorion/workshop/

and added modLocation = "workshop" to the modconfig.lua

 

the server startet download mods

 

Sorry for the necro, but curious if anyone else has run into the same issue. I tried to use the solution here, but I'm still getting the same "Found 0 mods in "AvorionDocker/AvorionDocker/modconfig.lua"" error. File structure matches the guide and your post, file matches the guide (and is confirmed working on a Windows dedicated server), but I just haven't been able to find a fix and can't think of anything else to try.

21 hours ago, Ks7 said:

Sorry for the necro, but curious if anyone else has run into the same issue. I tried to use the solution here, but I'm still getting the same "Found 0 mods in "AvorionDocker/AvorionDocker/modconfig.lua"" error. File structure matches the guide and your post, file matches the guide (and is confirmed working on a Windows dedicated server), but I just haven't been able to find a fix and can't think of anything else to try.

make sure permission are applied to th4 docker and taht the notepad items are being saved.

general steam cmd stuff and mods for the avorion
https://aleforge.net/help/how-to-install-mods-on-your-avorion-server/

That file looks correct, but an item option or line spacing may be causing problems. lua is YAML syntax and is space-sensitive.

Per the link above on the file make sure the line 15 doesn't have the ","

Edited July 21Jul 21 by bmartino1

On 7/20/2026 at 4:20 AM, BDKaleb said:

I can't seem to get my Palworld docker to work correctly.
I get it setup where it shows up on the community server list but it does not allow me to connect from the community server list. I can not connect via the public ip:8211 the only connection I get is via local Ip for the container (192.168.1.05:8211).

I have deleted the directories and freshly installed them. I changed the "PalworldSettings" and set "bIsMultiplay=True" and changed the server name and password.

I have changed the Port in my port settings, server settings etc. My port settings set to my local Unraid device's Ip (192.168.1.10) which is running the docker on a container (192.168.1.05:8211).

Attached is my docker settings, my router port fowarding settings, the message I get when i try to join via community servers, and the Server config file.
Any help is greatly appreciated. Thank you :)

this is an issue i had a while back... i changed Privilebed to On and mine worked immediately

On 7/20/2026 at 3:20 AM, BDKaleb said:

I can't seem to get my Palworld docker to work correctly.
I get it setup where it shows up on the community server list but it does not allow me to connect from the community server list. I can not connect via the public ip:8211 the only connection I get is via local Ip for the container (192.168.1.05:8211).

I have deleted the directories and freshly installed them. I changed the "PalworldSettings" and set "bIsMultiplay=True" and changed the server name and password.

I have changed the Port in my port settings, server settings etc. My port settings set to my local Unraid device's Ip (192.168.1.10) which is running the docker on a container (192.168.1.05:8211).

Attached is my docker settings, my router port fowarding settings, the message I get when i try to join via community servers, and the Server config file.
Any help is greatly appreciated. Thank you :)

I was having the same issues. Previously I had been running my server off of my PC with Steam's "Palworld Dedicated Server" tool. I ended up fixing the issue by going into my router's port forwarding settings for 8211 and changing the device IP from my PC's local IP to my unraid server's local IP. Now I can connect to the palworld docker server with both the public IP & through the community server browser.

On 7/16/2026 at 6:17 PM, whitewraith said:

Could you add tailscale support to the palworld container?

You can already enable Tailscale in the Unraid template.

On 7/21/2026 at 10:59 PM, kerpster said:

this is an issue i had a while back... i changed Privilebed to On and mine worked immediately

This is actually the worst idea, don't add privileged, you basically now allow the container to have access to your whole server and not much isolation going on.