Startup Issue with Palworld - Error code 125 on startup; Fails to start

Technical Support
, ,
1

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

Issue

When the server auto starts after I restart AMP, I get the error code 125 failed to start. When I start the server myself, the console/logs show that the application is updating and then after two updates the server just stops.

Reproduction Steps

  • Click the update button to update to the newest Palworld version
  • Click the start button
  • Check console to view the two updates
  • Server updates, then stops
2

I am not 100% sure, but I think the issue here is that AMP creates the ports right away when creating the instance, then when it comes time to set up the docker image, it tries to use port 27015, which is already created and in use by AMP.

3

I was able to fix this by updating the Palworld instance in the ADS instances screen instead of hitting the update button while in the Palworld instance:
image

4

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