Troubleshooting Palworld Server Connection Issues

Troubleshooting Palworld Server Connection Issues

Connection problems usually come from a small set of causes. Working through this checklist resolves most issues quickly, whether you are hosting or joining a server.

Check the server status

First make sure the server is fully booted. A Palworld dedicated server can take a few minutes before it accepts connections. Next, confirm that your game version matches the server version exactly. Patches often break connections until both sides update.

If you are the host, check the server console for errors. A crash during startup usually prints a message about a bad setting or a port already in use.

Port forwarding and protocol

The most common failure is a closed or misconfigured UDP port. Palworld gameplay uses UDP 8211. Make sure your router forwards UDP, not TCP. Steam query traffic uses UDP 27015. If you cannot see the server in the browser, open that port too.

Some routers have a separate protocol selector for each rule. If you pick TCP/UDP combined, it usually works, but UDP-specific forwarding is safest.

Carrier-Grade NAT and public IP

If your home or office connection uses Carrier-Grade NAT, external players cannot reach your server without help from your ISP or a hosting provider. Also compare your router's WAN IP to the PublicIP value in PalWorldSettings.ini. If they do not match, the public server list may send players to the wrong address.

Update and validate

A version mismatch after a patch is easy to fix. Update the server with:

steamcmd +login anonymous +app_update 2394010 validate +quit

Then restart and test again. Console players on Xbox and PS5 can only join through the Community Servers list, while Steam users can use direct IP.

Crossplay quirks

Crossplay between Steam, Xbox/Game Pass PC, and PS5 is supported, but Steam and Game Pass builds may differ temporarily. If crossplay fails, check that both clients and the server have updated to the same build.

Testing on your local network

If external players cannot connect, test from the same LAN first. Join using the server's local IP address, such as 192.168.1.50:8211. If local joining works but external players fail, the problem is almost certainly port forwarding, the firewall, or CGNAT.

Disable third-party antivirus or firewall software temporarily during testing. Some security suites block unknown executables like PalServer.exe even when Windows Defender is configured correctly. If your router supports hairpin NAT, you can test the public IP from inside your network; without it, use a mobile hotspot or ask a friend to test from outside.

Still stuck?

Verify your firewall allows PalServer.exe or the Linux PalServer.sh process. Use an external UDP port checker to test 8211. Most problems are a closed port, wrong protocol, CGNAT, or version mismatch. Work through the checklist methodically and you will usually have the server reachable again within minutes.