Palworld Server Troubleshooting

Config File Resets on Restart

Cause: Editing PalWorldSettings.ini while the server is running.

Fix: Always fully stop the server before editing the config. The server overwrites the file on shutdown.

Server Not in Community Browser

Fixes:

• Set PublicIP and PublicPort in PalWorldSettings.ini
• Add -publiclobby to startup arguments
• Ensure port 27015 UDP is open
• Wait 2–3 minutes after startup
• This is a known issue — the devs are working on improvements

Memory Leak / Server Runs Out of RAM

Palworld has a known memory leak. Mitigations:

• Schedule restarts every 4–6 hours via Schedules in the panel
• Set bEnableInvaderEnemy=False — raids heavily impact RAM
• Reduce BaseCampWorkerMaxNum to 10
• See Performance Optimization for full guide

"Connection Timed Out"

• Verify port 8211 UDP is open
• Check the server IP is correct (find it on the panel Dashboard)
• Ensure the game version matches between client and server

Admin Password Not Working

• Must be at least 8 characters, alphanumeric only
• Set in PalWorldSettings.ini as AdminPassword="YourPass123"
• Authenticate in-game with /AdminPassword YourPass123 (with the /)

Settings Not Applying

If WorldOption.sav exists in your save folder, it overrides PalWorldSettings.ini. Delete WorldOption.sav to force the server to use your config file settings:

1. Stop the server
2. Navigate to Pal/Saved/SaveGames/0/[WorldID]/
3. Delete WorldOption.sav
4. Start the server

Console Players Can't Join

• Ensure crossplay is enabled: CrossplayPlatforms=(Steam,Xbox,PS5,Mac)
• Add -publiclobby to startup
• Port 27015 UDP must be open
• See Crossplay Setup

Server Not Showing in Steam Server List

This is not supported and may never be. Palworld uses its own community server browser, not Steam's server list. Connect via direct IP or the in-game browser.

Related Guides

• Performance Optimization
• Server Configuration
• Crossplay Setup
• Admin Commands