Palworld friends can't join your dedicated server?

Quick answer

Palworld dedicated servers use UDP port 8211 for gameplay and UDP 27015 for the Steam query and community server list. Most join failures come from: 8211 forwarded as TCP (or not at all), the firewall or antivirus blocking PalServer.exe, CGNAT, a version mismatch after a patch, or console players trying to join by IP. Xbox and PS5 players can't type an IP; they find the server in Community Servers by its exact ServerName.

Ports

• 8211 UDP: Game traffic. Must be forwarded
• 27015 UDP: Steam query / community server list
• 8212 TCP: REST API. Never expose to the internet
• 25575 TCP: RCON (deprecated). Don't expose

How to fix it, step by step

1. Let the server finish starting. Watch the server console. If it reports a bad setting or a port already in use, fix that first; nobody can join a server that isn't running.
2. Forward UDP 8211. Forward UDP 8211 to the server PC's reserved local IP. If you created the rule as TCP, delete it and re-create it as UDP; TCP 8211 doesn't work.
3. Allow PalServer.exe through the firewall. Allow it in Windows Firewall. Third-party antivirus can block it even when Windows Firewall is set up correctly; add an exception or briefly disable it to test.
4. Test LAN first, then from outside. Join with the LAN address (for example 192.168.1.50:8211), then from a mobile hotspot. If LAN works and outside fails, it's the port forward, the firewall or CGNAT (see the CGNAT guide).
5. Join the right way for each platform. Steam and Mac players: Join Multiplayer Game (Dedicated Server), then enter public-ip:8211. Xbox, PS5 and Game Pass players: search Community Servers for the exact ServerName. Invite codes are for co-op worlds, not dedicated servers.
6. Update the server and every client. Versions must match exactly. Update the server with steamcmd +login anonymous +app_update 2394010 validate +quit. Steam and Game Pass builds can be briefly out of sync after a patch, which breaks crossplay until both update.
7. Check crossplay settings. In PalWorldSettings.ini, CrossplayPlatforms must include every platform your friends use (default (Steam,Xbox,PS5,Mac)). AllowConnectPlatform no longer exists.

Server not showing up in the community list

Launch with -publiclobby, open UDP 27015, and set ServerName, PublicIP and PublicPort. If PublicIP doesn't match your router's WAN IP, the list can send players to the wrong address. The list is slow anyway, so PC players should join by IP.

Settings that silently don't apply

Copy DefaultPalWorldSettings.ini to Pal/Saved/Config/WindowsServer/ (or LinuxServer/) as PalWorldSettings.ini and edit that copy. Editing the Default file has no effect. PublicPort doesn't change the port the server listens on.

Test it from the outside

Your own Wi-Fi can't tell you whether friends can reach the server. The free Server Doctor check contacts your server once from the internet, the way the game does, and tells you the most likely cause. The same check runs in Discord with /fix.

No PC to host 24/7?

A Palworld server is heavy to run on the PC you play on, and it has to stay on for friends to play. A hosted Palworld server gives you an address that works without port forwarding or CGNAT workarounds.

Related guides

• Friends can't join your Minecraft server? Here's the fix.
• Minecraft Bedrock: "Unable to connect to world"
• Valheim server not showing up, or friends can't join?
• Hytale friends can't connect to your server?
• Behind CGNAT? Host a game server without port forwarding.
• All guides

Sources: palworldservers.io/guides/ports-and-firewall · palworldservers.io/guides/connection-troubleshooting · docs.palworldgame.com/settings-and-operation/configuration · hostdservers.com/docs/palworld-1-0-crossplay-connecting · playit.gg/