Troubleshooting Palworld Connection Timed Out Errors

If you're seeing "Connection Timed Out" when joining a Palworld server, it usually comes down to one of these:

The server is offline or stuck while starting.
You're connecting to the wrong IP:PORT.
A firewall/router/security group is blocking the UDP game port.
You're self-hosting behind CGNAT (your ISP won't allow inbound connections).

60-second triage (do this first)

Confirm the exact connect string

Ask the server owner for the IP and port they expect you to use (example: 203.0.113.10:8211).
If you're on a managed host (like LOW.MS), the panel will show the correct IP:PORT.

Try a different network

If you're trying to join from the same LAN as the server, your router might not support NAT loopback.
Test by joining from mobile data (phone hotspot) or ask a friend outside your network to try.

If you can join locally but not remotely

That's almost always port forwarding / firewall / CGNAT.

Server-side troubleshooting

1) Check the server is actually running

Restart the Palworld server and wait for it to fully boot.
If you have console access, check for errors during startup and confirm it stays running (not crashing/restarting).

2) Confirm the server is listening on the expected port (UDP)

Default listen port is 8211, unless changed via startup arguments. The official server arguments include -port=8211 to set the listening port.

Windows (PowerShell / CMD):

netstat -ano | findstr :8211

Linux:

ss -lunp | grep 8211

If you changed the port (example -port=8000), substitute that value everywhere below.

3) Open the correct ports (don't use random ranges)

The most common ports you'll need are:

UDP 8211 = game traffic (or whatever you set with -port=)
UDP 27015 = Steam query / listing (often required for visibility in lists)
TCP 25575 (optional) = RCON, only if you enable it

Linux (UFW)

sudo ufw allow 8211/udp
sudo ufw allow 27015/udp
# Optional (only if using RCON):
sudo ufw allow 25575/tcp
sudo ufw reload
sudo ufw status

Windows Firewall (quick rules)

Run PowerShell as Administrator:

New-NetFirewallRule -DisplayName "Palworld UDP 8211" -Direction Inbound -Action Allow -Protocol UDP -LocalPort 8211
New-NetFirewallRule -DisplayName "Palworld UDP 27015" -Direction Inbound -Action Allow -Protocol UDP -LocalPort 27015
# Optional (RCON):
New-NetFirewallRule -DisplayName "Palworld TCP 25575" -Direction Inbound -Action Allow -Protocol TCP -LocalPort 25575

You can also do this via Windows Defender Firewall with Advanced Security:

Windows Defender Firewall

4) If you're self-hosting at home: check port forwarding & CGNAT

A) Port forward to the correct machine

Forward UDP 8211 to your server PC's LAN IP (example: 192.168.1.50).
If you want community listing / query, forward UDP 27015 too.
Make sure the server PC has a static LAN IP (or DHCP reservation), otherwise the rule can break after a reboot.

B) Check if you're behind CGNAT

If your router's "WAN IP" doesn't match what websites show as "your public IP", you're likely behind CGNAT and inbound connections will time out unless your ISP provides a public IPv4.

5) If you're on a VPS / datacenter host: check the provider firewall too

Even if Windows/UFW is open, many VPS providers have an extra "security group" firewall. Make sure inbound UDP 8211 is allowed.

6) Docker / container hosting gotcha

If you're running Palworld in Docker, you must publish UDP ports explicitly (TCP-only publishes won't work for the game port).

Server configuration (important details that trip people up)

PalWorldSettings.ini location

Common paths:

Windows: ...\\Pal\\Saved\\Config\\WindowsServer\\PalWorldSettings.ini
Linux: .../Pal/Saved/Config/LinuxServer/PalWorldSettings.ini

"PublicIP" / "PublicPort" are NOT the listening port

PublicIP and PublicPort are intended for community server listing, and PublicPort does not change the port the server listens on.

For direct connecting, players must still use the actual listen port (default 8211, or whatever you set with -port=).

If you don't need community listing, you can often leave PublicIP / PublicPort alone.

Client-side troubleshooting

1) Join using the right method

Prefer Direct Connect using IP:PORT (example 203.0.113.10:8211).
If you're on the same LAN as the server, try the LAN IP instead (example 192.168.1.50:8211) to avoid NAT loopback issues.

2) Match game/server versions

Make sure the server and client are on compatible versions (especially after a patch). If the server hasn't updated yet, you can get timeouts or failed joins.

3) Verify game files (Steam)

Steam Library -> right-click Palworld -> Properties
Installed Files -> Verify integrity of game files

4) Reset Windows networking (when nothing else makes sense)

Run in an elevated Command Prompt:

ipconfig /flushdns
netsh winsock reset
netsh int ip reset

Reboot afterwards.

5) VPN / antivirus checks

Temporarily disable VPNs (they can break UDP routing).
If disabling antivirus "fixes" it, add an allow rule/exception instead of leaving it off.

LOW.MS quick path

If your Palworld server is hosted on LOW.MS:

Use the IP:PORT shown in your panel (copy/paste into Direct Connect).
Restart the server once after any port/config changes.
If it still times out, send support your service ID, the time of your last join attempt, and whether anyone outside your network can connect.

Still stuck? Send these details (it speeds up the fix)

Are you self-hosting (home) or using a host?
The exact IP:PORT you're joining.
Whether the server owner can join locally.
Whether a friend on a different network can join.
The server OS (Windows/Linux), and whether you changed the port with -port=.

Categories