Palworld connection timeout or server not found

Check startup and version alignment

Read logs through the completion of world loading. An active process repeatedly restarting is not a ready server. Compare client and server versions and release branches.

If the problem followed an update or import, retain those logs. Test a separate world only after backing up. If that works, investigate the original save, mods and imported settings.

Use the actual listening port

Official documentation distinguishes the listening port, illustrated by -port=8211, from the advertised public port. On rented hosting, use the panel's assigned value; not every plan uses 8211.

Changing PublicPort does not change the listening socket. Community announcements must match the reachable public address and port. On a self-hosted installation, check firewall rules, forwarding to the correct machine and access from another network.

Check visibility and platform access

The -publiclobby startup argument enables community-server mode. Inspect browser filters and the joining methods supported by your platform. If direct access succeeds but search fails, investigate listing and filters first.

Current CrossplayPlatforms settings control allowed platforms. The deprecated AllowConnectPlatform is not the fix. Platform interoperability is covered separately in our Palworld crossplay guide.

Distinguish rejection from timeout

A wrong password, a ban and a network timeout require different repairs. Compare the client message with server logs. An issue affecting only one player calls for checking that account and connection before reinstalling everyone's server.

For support, provide a timestamped example with version, platform, port and sanitized logs. If players on several networks all fail while the world loads normally, request a network-access check for the hosting instance.

Frequently asked questions