Update Failure with Palworld - Can't update Palworld instance

Technical Support
, ,
1

System Information

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

Problem Description

Issue

I can’t seem to update my palworld instance.
At first it asked me to log into steam and get through steam guard, but that didn’t work as my steam guard blocked the connection.
Now upon retrying a few days later, it asked me to login to steam again to do the update but it just fails without asking about steam guard.

Something of note, for previous updates I have done I did not need to log into steam to update the instance. Why do I have to do this now? Also I can’t seem to make a new palworld instance either I assume for the same reasons.

Reproduction Steps

  • Not played for a while
  • Logged into Hostinger
  • Stopped palworld instance
  • Clicked the update instance button
  • Also tried the update button in the instance status
2

When you click the update instance button (the down arrow), what is in the deployment log? Any git errors?

3

Upon relooking at the console logs, I am now noticing it is showing incorrect password so I may have put it in wrong at the time. But its not letting me put the password back in, it doesn’t ask at all it just retries with the current info I have put in when it asked earlier.

Do keep in mind if I do put in the correct password I assume it would still fail steam guard because steam sees it as being in a different location than where I am in. I suppose I will update the ticket when it lets me put the info in again and see what happens then.

Here are the pop ups and logs within the console anyways:
This task could not be completed: Running Update Tasks - - State: 3.

**Failed to request app info update, not online or not logged in to Steam.
**
Redirecting stderr to ‘/home/amp/Steam/logs/stderr.txt’

Logging directory: ‘/home/amp/Steam/logs’

[ 0%] Checking for available updates…

03:58:24

[----] Verifying installation...

UpdateUI: skip show logo

Steam Console Client (c) Valve Corporation - version 1769026246

-- type ‘quit’ to exit –

Loading Steam API…OK

force_install_dir “2394010”

Cached credentials not found.

password:

Proceeding with login using username/password.

03:58:26

Logging in user '' [U:1:0] to Steam Public...ERROR (Invalid Password)

app_update 2394010 -beta public validate

ERROR! Failed to request app info update, not online or not logged in to Steam.

quit

Unloading Steam API…OK

4

I asked about updating the instance, not the server

Click Return to Instances, stop the instance, click the down arrow on the instance tile, check the Deployment Log

You shouldn’t be prompted any more for Steam login, which suggests to me your instance is out of date, possibly due to not updating properly

Checking the Deployment Log when updating the instance should reveal any issues

5

This is what I got for doing that, my bad on not realizing you meant the instance instance update:

Upgrading instance Shortsarecomfyandeasytowear01
05:30:24
Updating remote source CubeCoders/AMPTemplates:main
Updating existing remote source https://github.com/CubeCoders/AMPTemplates.git...
No stash entries found.
05:30:25
Refreshing instance config for Shortsarecomfyandeasytowear01 with source CubeCoders-AMPTemplates-main
6

No obvious issues there. That means the instance should now be updated, and no longer require steam login to update the server - unless you are downloading steam workshop items, then login will be required for those

But who knows with AMP?