Palworld: SteamCMD updates fail with "No Connection" (Workaround included)

Technical Support
,
1

Hi,

I’m posting this in case someone else runs into the same issue.

I’m running AMP Release Proteus v2.8.0.4 (built 24/07/2026 17:13) on Debian 13 with rootless Podman 5.4.2.

The built-in scheduled SteamCMD update task for my Palworld instance worked fine for quite a while. At some point it stopped working and every automatic update failed with:

FAILED (No Connection)
ERROR! Failed to request app info update, not online or not logged in to Steam.

AMP also logged HTTP errors while trying to reach cdn-downloads.c7rs.com.

I found a couple of older topics that appeared to describe the same issue, but they were already closed, so I decided to document what I found.

After some troubleshooting, this is what I discovered:

  • Running the exact same SteamCMD command on the host worked perfectly.

  • Running the same command inside the AMP container consistently failed with “No Connection”.

  • Inside the container, /etc/resolv.conf was completely empty, so there was no working DNS configuration.

  • Commands like getent hosts api.steampowered.com returned nothing.

  • As soon as I added DNS servers manually, SteamCMD immediately started working again.

Temporary fix inside the container:

nameserver 1.1.1.1
nameserver 9.9.9.9

After that:

  • DNS resolution started working.

  • SteamCMD connected successfully.

  • The server updated successfully.

As a permanent workaround, I created:

~/.config/containers/containers.conf

with:

[containers]
dns_servers = [
  "1.1.1.1",
  "9.9.9.9"
]

After recreating the container, the automatic scheduled updates started working again.

I’m not sure whether this is an AMP issue, a Podman issue, or something specific to my environment. I just wanted to share my findings in case they help someone else or help identify the root cause.

If anyone from CubeCoders would like additional logs or wants me to test something else, I’d be happy to help.

:victory_hand:mars