Palworld server problems

Common Palworld server problems and how to fix them. Settings named here are on your Startup page, see Palworld settings.

I cannot connect to my Palworld server

Why it happens: The server is still loading, the address or port is wrong, or the game and server are on different versions.

How to fix it:

1. Wait until the panel status says Online. Palworld can take a few minutes to load.
2. Use the address and port from the Network page, in the form address:port.
3. If you set Server Password (SERVER_PASSWORD), enter it exactly.
4. Check the Connection Platform (ALLOW_CONNECT_PLATFORM) setting matches how you play: Steam for Steam players, or the Xbox option if the Startup page offers it.
5. See Can’t connect to any game.

Version mismatch after a Palworld update

Why it happens: Palworld patches often change the network version, and players on the new version cannot join an old server.

How to fix it:

1. Make sure Auto Update (AUTO_UPDATE) is 1 on Startup.
2. Restart the server so it updates on start.
3. Ask players to update Palworld in Steam.
4. If the server is still older than the game after a restart, open a ticket.

Server does not show in the community server list

Why it happens: Palworld only lists servers that are started as a public community server, and the list can be slow or full. There is no variable on the Startup page for this.

How to fix it:

1. Join with direct connect instead, using the address and port from Network.
2. Search for the exact Server Name (SERVER_NAME) in the list.
3. To ask us about the public listing, open a ticket. Editing the startup command by hand is possible on Startup, but do that only with our help.

Memory keeps growing, then the server is killed or restarts

Why it happens: Palworld servers are known to use more memory the longer they run, and in many cases it climbs until the server runs out.

How to fix it:

1. Restart the server regularly with a Schedule, for example once a day at a quiet time. Add a step to send a warning message first if you can.
2. Lower Max Players (MAX_PLAYERS).
3. If the Console shows “Out of memory: true”, see Out of memory or upgrade.

Server crashes when saving or the world will not load (save corruption)

Why it happens: A crash or a forced stop while saving can leave a broken save file.

How to fix it:

1. Always use Stop, not Kill, so the server can save.
2. Restore your latest good backup from Backups.
3. Take a backup before every update and before changing settings.
4. If you have no backup, open a ticket.

What is the admin password and how do I use it?

Why it happens: Palworld has no admin accounts. It uses one shared password, set by Admin Password (ADMIN_PASSWORD).

How to fix it:

1. On Startup, set Admin Password and restart the server.
2. In game, open chat and type /AdminPassword yourpassword. Then you can use admin commands.
3. Do not share it. Change it if it leaks.

How do I use RCON?

Why it happens: Palworld’s RCON uses the admin password. The RCON port is optional and does not have to be allocated for normal play, and there is no Startup variable that turns RCON on here.

How to fix it:

1. Set Admin Password on Startup and restart.
2. In your RCON tool, use your address, the RCON port, and that password.
3. If no RCON port is listed on Network or you cannot connect, open a ticket and we will check.

World settings do not apply (XP rate, difficulty, and others)

Why it happens: Most Palworld world settings are in a config file, not on the Startup page. The community egg’s notes say the file can be reset if you edit it while the server is running, so edits made while running can be lost.

How to fix it:

1. Stop the server first.
2. In Files, open PalWorldSettings.ini. It is inside the game’s Pal/Saved/Config folder, in a subfolder named for the platform (LinuxServer on a native Linux server, WindowsServer on a Proton one).
3. If the file only has a blank options line, copy the defaults from DefaultPalWorldSettings.ini or the Palworld documentation and edit values there.
4. Save and start the server.
5. A change on the Startup page like Server Name is handled by the panel and can overwrite that value. Use the Startup page for those.

My settings keep resetting to default

Why it happens: The panel writes a few values on start, and Palworld overwrites its config if you edit while running.

How to fix it:

1. Stop the server before editing.
2. For Server Name, Server Password, Max Players, Admin Password, use the Startup page and not the file.

Player limit and max players

Why it happens: Max Players is set on Startup. It is capped by what your plan’s memory can handle.

How to fix it:

1. On Startup, change Max Players (MAX_PLAYERS, default 32).
2. Restart the server.
3. If the server runs poorly with many players, see the memory item above.

Password prompt when I did not set a password

Why it happens: Server Password is blank by default, but a leftover value may exist.

How to fix it:

1. Check Server Password on Startup. Clear it to remove the password.
2. Save and restart.

Standard egg or Proton egg: which am I on?

Why it happens: Some Palworld setups run through a compatibility layer (Proton). The Startup page settings shown for your server are the ones that apply to you.

How to fix it:

1. Open Startup and use the variables shown there.
2. If you see missing options, or a change asks for a different egg, open a ticket. Do not change the egg on your own, since it switches software immediately. See Startup settings.

Server will not start after a change

Why it happens: A bad value in a config file or the startup command.

How to fix it:

1. Read the last lines in the Console.
2. Use Reset to Egg Default on Startup if you changed the startup command.
3. Restore an older config or a backup.
4. See Server keeps restarting.

Still stuck?

Open a ticket or ask on Discord. See Contact support.