PC joins but Xbox and PS5 cannot find your Palworld server

A successful PC connection proves one route into Palworld. It does not prove that the server registered a community listing or advertised an address a console can reach. Diagnose those separately before changing ports or rebuilding the world.

This guide assumes an existing, unmodded dedicated server that a PC player can already join. Linux commands use palworld.service and /srv/palworld/server from the installation guide. Substitute your actual service, account and installation. Sources were checked on October 17, 2026; Pocketpair's server guide currently displays 1.0.4.

Check the current platform rules#

Pocketpair's platform reference includes Steam, Xbox with Microsoft Store PC, Mac and PS5. Crossplay is enabled by default, but Xbox and PS5 need the dedicated process registered as a community server. An older guide saying PS5 can never join this server type is not the current reference.

A community server is a listing mode of the same dedicated process. It does not require migrating the save or creating a second world. The connection guide separates direct address entry from finding a server in Community server. First record which method the successful PC player actually used and whether that player was outside the host's LAN.

Inspect the running launcher#

On the host:

sudo systemctl cat palworld
sudo systemctl show palworld -p ExecStart -p User -p WorkingDirectory -p MainPID -p Restart
sudo journalctl -u palworld -n 100 --no-pager

Inspect the effective launch command, including any wrapper it calls. The community deployment guide requires -publiclobby. If the command lacks it, this explains why direct access can work without a community listing.

Add the flag to the existing launcher during maintenance; do not start another PalServer.sh alongside the managed process. Keep the existing installation path, port and other required options. A supervisor, container or panel can have its own launch settings; changing an unused unit will not affect that process. Keep command output private if it contains credentials.

For an INI or launcher change, have a connected administrator save and request shutdown using the documented commands:

/AdminPassword REPLACE_ADMIN_SECRET
/Save
/Shutdown 30 DiscoveryMaintenance

Wait for exit and check MainPID, logs and the restart policy. If the supervisor restarts the game automatically, deliberately stop the service and wait until the managed process really remains stopped. The earlier setup uses Restart=no. Preserve a private copy of the existing INI and any service file before changing them.

Give the listing a recognizable identity#

Edit the active Linux configuration under /srv/palworld/server/Pal/Saved/Config/LinuxServer/PalWorldSettings.ini. Keep its complete existing OptionSettings tuple. Within it, inspect ServerName and CrossplayPlatforms; do not replace the whole file with a small example. A distinctive name is easier to distinguish from another default-named server.

The configuration reference uses CrossplayPlatforms, whose default is (Steam,Xbox,PS5,Mac). The old AllowConnectPlatform setting is not the current control. Confirm that the actual client's platform remains allowed rather than assuming a copied historical template retained the defaults.

A December 2025 support discussion describes an administrator whose configured name did not take effect, making console discovery harder. If your list still shows a default name, investigate the active INI and syntax before repeatedly changing firewall rules. Do not remove an existing join password just to make the name appear.

After editing a systemd unit, run sudo systemctl daemon-reload. Then start the existing service and check its fresh log:

sudo systemctl start palworld
sudo journalctl -u palworld -n 100 --no-pager
sudo ss -lunp 'sport = :8211'
sudo ufw status verbose

These commands inspect startup, the example UDP port and host firewall state. They do not test a remote player's connection. Substitute the real listener if it is not 8211.

Match the advertised endpoint to the listening socket#

The argument reference distinguishes -port from -publicport: the former selects the local listener; the latter advertises a community endpoint. Automatic public address detection is the starting point. Override it only when you have identified the actual external mapping.

For example, a router could forward public UDP 18211 to host UDP 8211. In that case the listener remains 8211 while the listing must advertise the real public address and 18211. With no port translation, public and local port numbers usually match. Never advertise a documentation example address or the host's private LAN address to internet players.

Check the provider firewall, host firewall and router mapping against that same route. A TCP port-check website cannot validate Palworld's UDP gameplay path. RCON and REST administration ports are separate; opening them publicly does not repair discovery. A home connection behind carrier-grade NAT needs an actually reachable inbound route or different hosting/network arrangement; repeatedly forwarding ports on only the home router cannot create that route.

Use the symptom to select the next check#

Pocketpair explicitly documents the hairpin limitation. A test from inside the hosting LAN therefore cannot stand in for an external console test. Listing search results also do not provide a reason to change a working public port at random.

Finish with an actual Xbox or PS5 join from the intended player network. Record the displayed name, platform, client/server builds, public endpoint and whether the failure happened before discovery, during connection or after authentication. Redact join and administrator passwords. A process marked active, a UDP socket or a successful PC join is useful evidence for one layer; the console join is the final acceptance check.