palworld-server-docker: RCON with adminPassword doesn't work in CLI

Describe the bug

If you have an ADMIN_PASSWORD set for the server RCON will not accept any authorization.

I’ve tried wrapping the password in quotes, both double and single, without quotes, touching the -p switch, using the --password long form. No matter what I try the RCON server always returns: cli: execute: auth: rcon: authentication failed. If you set the ADMIN_PASSWORD to empty string, then the rcon-cli works as expected. It’s only when it is password protected that the CLI will not work.

To Reproduce

Steps to reproduce the behavior:

Set the ADMIN_PASSWORD to something.
Start the docker instance.
Run `docker exec -it <containerID> rcon-cli --password <ADMIN_PASSWORD> info
See authorization failed message.

Expected behavior

The provided admin password should be accepted if it matches what was set in as the docker environmental variable.

Desktop (please complete the following information)

Ubuntu 22.04.3 LTS
Docker image 0.19.0

docker-compose.yml contents

version: '3.9'
services:
  palworld:
    image: thijsvanloef/palworld-server-docker:latest
    restart: unless-stopped
    container_name: palworld-server
    ports:
      - 8211:8211/udp
      - 27015:27015/udp
    environment:
     - PUID=1000
     - PGID=1000
     - PORT=8211 # Optional but recommended
     - PLAYERS=4 # Optional but recommended
     - MULTITHREADING=true
     - RCON_ENABLED=true
     - RCON_PORT=25575
     - ADMIN_PASSWORD='test1234'
     - COMMUNITY=false  # Enable this if you want your server to show up in the community servers tab, USE WITH SERVER_PASSWORD!
     volumes:
      - ./game:/palworld/
  image_updater:
    image: containrrr/watchtower
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock

Important context

The world the server is running is a migrated single player save.

About this issue

Original URL
State: closed
Created 5 months ago
Comments: 24 (3 by maintainers)

Most upvoted comments

@thijsvanloef, issue resolved.

I don’t know if @bdelwood’s fix also helped contribute to the solution, but what finally got it to work for me was doing what this Redditor mentioned here.

By deleting the WorldOption.sav file I was able to get the rcon to work properly from docker exec AND in game. As always, be sure to backup the file before deleting it, just in case, but for me deleting the file and restarting the server did the trick.

(This also resolved a number of server status issues for me as well, like the server name not showing correctly nor the max number of players.)

For anyone else who stumbles across this issue please be aware that after you delete the WorldOption.sav file you’ll be prompted to pick a spawn location again once you connect to the server. This is normal and fine. All my bases, production progress and pals were still present and fine.

Thank you all again for your help with this issue – closing!

sethicis on Jan 31, 2024