Summer Sale   25% off with code 00d 00h 00m 00s


 
 
 
 
Knowledgebase Palworld Palworld Server: Common Issues & Fixes

Palworld Server: Common Issues & Fixes

This page collects the most common problems Palworld server owners run into, along with the fix for each. If your issue isn't covered here, it may be worth checking one of our more detailed guides linked throughout, or opening a support ticket directly.

Connection & Joining Issues

  • Can't connect at all: Double-check your IP address and port for typos, and confirm your server shows as fully started on the MintServers panel. See our guide to joining your Palworld server for the full process.
  • "Connection timed out" using Recent Servers: The Recent Servers tab has a known issue where it can fail to connect even to a server you've joined before. Use Direct Connect with the IP address and port instead, every time, until this is more reliable.
  • Password prompt doesn't appear: Make sure the Enter Password box is checked before clicking Connect. If it still doesn't prompt you, fully close Palworld and try again.
  • "The match you are trying to join is running an incompatible version of the game": Your server and your game client are on different versions. See our guide to updating your server.
  • Xbox or PS5 friend can't find the server: Console players can only join through the in-game Community Servers list, not by IP. See our crossplay setup guide for details.
🚀 Launch Your Unlimited RAM Game Server — Just $9.99/mo!

Server Won't Start Or Keeps Crashing

  • Server stuck starting, or stuck in a restart loop: This is almost always caused by a formatting mistake in a recently edited PalWorldSettings.ini, like a missing comma or quotation mark. Undo your last change, or restore a backup from the Backups tab, then try starting again.
  • Server crashes right after a game update: This is typically caused by outdated mods. Disable your mods and try starting again; if it comes up fine, your mods need to be updated individually before re-enabling them.
  • Random Steam-related errors in the console on startup: Messages mentioning things like a missing steamclient.so file are normal background noise from the Steam layer the server runs on top of, and can be safely ignored as long as the server actually starts.
  • Server appears stuck mid-update, or shows an error mentioning an "app state": Stop the server, then use the Reinstall option in the Settings tab to re-download the server files cleanly.

Save, World & Character Issues

  • Save appears corrupted or won't load: Restore your most recent working backup from the Backups tab. This is why keeping regular backups matters, especially before updates or big changes.
  • Host character lost levels and Pals after transferring a co-op save: This is expected behavior, not a bug with your specific transfer. See our guide to transferring a co-op save for why this happens and how to minimize the loss.
  • Raising BaseCampWorkerMaxNum or CoopPlayerMaxNum doesn't change anything in-game: This is a known limitation with those two settings rather than a configuration mistake on your part.
  • Players keep getting disconnected or losing guild access after a guild member logs off: This can happen if a guild member leaves while everyone else is offline. Having them rejoin the guild usually resolves it; if not, a server restart typically clears it up.

Commands Not Working As Expected

  • Command does nothing when typed in chat: Commands are case-sensitive, and admin authentication only lasts for your current session. Re-run /AdminPassword and double-check your capitalization.
  • Looking for the full command list, or how to run commands remotely: See our complete admin commands guide, which also covers RCON and the REST API.

If you're dealing with something that isn't listed here, no worries! Just open a support ticket and our team will be happy to help you track down the cause.

Was this article helpful?

The Last Minecraft Hosting You Will Ever Need!

Unlimited Slots, Unlimited RAM, One-Click Mods & Plugins