Menu
  Log out
 

Palworld Connection Timeout Fix

Palworld Guide • Updated Jan 15, 2026

Palworld Connection Timeout: Fix "Failed to Connect"

When players see a connection timeout or "Failed to Connect" message, the server is usually reachable locally but not over the public internet. Use this checklist to restore access without wiping your save.

Recent Fix: If you started having timeout issues after a server update, ensure your server is running the latest version. The 0.2.0.6+ updates fixed many dedicated server connection timeout issues.

Quick Diagnostic Table

Check Why It Fails Fix
Port 8211 UDP Port not forwarded or blocked by firewall Open UDP 8211 and forward to server IP
PublicIP/PublicPort Wrong public IP or port in config Set correct values in PalWorldSettings.ini
Version mismatch Server and client on different versions Update both to the same version
Server not started Server process crashed or not running Check server logs and restart
VPN/Strict NAT VPN or router blocks inbound UDP Disable VPN, enable UPnP, or set NAT to Open
Windows Firewall Palworld not allowed through firewall Add exception for PalServer.exe

Step-by-Step Fix

  1. Confirm the server is running. Check your panel or use server logs to confirm it finished booting.
  2. Restart after updates. Palworld does not hot-reload. Restarting applies updates and settings.
  3. Open UDP 8211. Forward UDP 8211 to the server. Optional: forward UDP 27015 if you rely on server browser queries.
  4. Verify PublicIP and PublicPort. Incorrect values cause timeouts for remote players.
  5. Avoid VPNs and strict NAT. VPNs and strict NAT can block inbound UDP connections.
  6. Crossplay? If Steam and Xbox players mix, follow Crossplay Troubleshooting.

Verify PalWorldSettings.ini

Make sure the network values are correct in your server settings file:

PublicPort=8211
PublicIP="YOUR_PUBLIC_IP"
RCONEnabled=False
RCONPort=25575
bIsMultiplay=True
bUseAuth=True

Windows Firewall Configuration

If players timeout but the server appears to be running:

# PowerShell (Run as Administrator)
New-NetFirewallRule -DisplayName "Palworld UDP 8211" -Direction Inbound -Protocol UDP -LocalPort 8211 -Action Allow
New-NetFirewallRule -DisplayName "Palworld TCP 8211" -Direction Inbound -Protocol TCP -LocalPort 8211 -Action Allow

# Or: Windows Defender Firewall → Allow an app → Add PalServer.exe

Still Timing Out?

Advanced Troubleshooting:

  • Test connectivity: Use nc -zvu YOUR_IP 8211 from another machine to verify port is open
  • Check router: Verify port forward points to the correct internal IP (not just "any")
  • Reboot router: Some routers need restart after saving port forward rules
  • ISP blocking: Some ISPs block game server ports; try a different port like 27015
  • Wait 24 hours: Palworld sometimes has server connection issues after updates that resolve with patches

Pro Tip: If players can join via LAN but not remotely, this is almost always a port forwarding or firewall issue. Double-check your router's port forward is targeting the correct local IP.

Skip the networking hassle. Host your Palworld server with Supercraft for pre-configured ports and instant connectivity.

← Back to Palworld Guides
Top