Startup Issue with Palworld - Multiple Instances of Palworld Fails to start after todays update

System Information

Field Value
Operating System Linux - Debian GNU/Linux 12 on x86_64
Product AMP ‘Decadeus’ v2.4.8.0 (Mainline)
Virtualization Docker
Application Palworld
Module GenericModule
Running in Container Yes
Current State Stopped

Problem Description


After the 2024/02/27 Update Patch v0.1.5.0 update. All palworld instances will not start.

Is there a way to roll back the build? I do not see any options in the SteamCMD and Updates for specifying a specific build number.

Reproduction Steps

  • Stop the application and then run a steam update
  • Start the application and watch it stall on starting during ram allocation
  • force stop the instance and application and try starting it again.

I hade the same issue with my Windows Palworld Instance. What I had to do to fix it:

! first make sure to have a backup incase something breaks !

  1. Fully stop the palworld instance at the Instances screen, make sure its not running on the host anymore
  2. go to Configuration → Instance Deployment and press “Fetch Latest” under Configuration Repositories, wait for it to finish
  3. at the Instances screen click on “Update” under Actions, wait for it to finish

after that the rcon port went green again and the instance is up and running.

Its always a good idea to have an eye on the official repo on Github for updates on the Templates:

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.