Palworld "Connection Timed Out" on a Server: Causes and Fixes
A Palworld "connection timed out" error means the game sent a join request and never got an answer. It is a reachability problem, not a save or account problem. Check that the server is running, that the player entered the full address with the port (for example 203.0.113.10:8211), that the game and server versions match, and that the player's platform is allowed to join.
On a ChicagoServers server the panel assigns the port and handles forwarding, so the usual home-hosting causes do not apply. This guide covers what does. It was checked on 2026-11-15 against the official Palworld server documentation and host troubleshooting write-ups for version 1.0.4. Some behaviour, such as how consoles join, comes from host documentation, so confirm it in the game.
- Palworld's game port is UDP 8211 by default. Traffic is UDP, so forwarding TCP does nothing. On ChicagoServers the panel assigns the port and shows the address at the top of the server page.
- Join with the full address and port, such as
IP:8211. The port is required if it is not the default. - A plain timeout is usually not a version problem. Host documentation reports that recent versions show a version mismatch message instead.
CrossplayPlatformsinPalWorldSettings.inidefaults to Steam, Xbox, PS5 and Mac. A player on a platform that is not listed cannot join.PublicIPandPublicPortonly change what the community list shows.PublicPortdoes not change the port the server listens on.
On this page
Check these first
- Is the server running?
Open the panel and confirm the server is online. Look at the Console tab. A server still loading or stuck on a crash will time out.
- Use the full address
In Palworld choose to join a multiplayer game, then paste the address from the top of your server page. It includes the port.
203.0.113.10:8211 - Update both sides
The server and the game must be on the same version. After a Palworld update, use Update now on the Steam update bar and restart, and make sure the player's game is up to date.
- Check the platform
Open World settings (PalWorldSettings.ini) on the Configs tab and look at
CrossplayPlatforms. The player's platform has to be on the list. - Check the password
If the server has a password, set it on the Startup tab and give players the same one.
Ports and the address
- The default game port is UDP 8211. It is set with the
-portlaunch option. Our panel assigns it for you. - RCON and the REST API use separate ports and have nothing to do with joining.
- The address needs both parts: IP and port, joined by a colon.
- If you ever run a server at home, allow UDP 8211 in the firewall and forward it. Home servers also fail when the provider uses CGNAT, which blocks forwarding. Neither applies to a hosted server.
Crossplay and consoles
CrossplayPlatforms sets which platforms may connect. The official documentation gives the default as Steam, Xbox, PS5 and Mac. If a console player times out, check their platform is in that list. Host documentation says console players have to join through the community server list, so on ChicagoServers make sure List in community servers is on in the Startup tab if you want them to find the server. Host documentation describes direct IP entry as the PC route.
The settings file, its format and the other keys are explained in the server settings guide.
Symptoms and fixes
| What you see | Likely cause and fix |
|---|---|
| Connection timed out | The server is offline or not answering, or the address is incomplete. Confirm the server is running and use IP:port. |
| Version mismatch message | The server and game versions differ. Use Update now, restart, and update the player's game. |
| Console player times out | Their platform is not in CrossplayPlatforms, or they are not joining through the community list. |
| Wrong address in the community list | Check PublicIP and PublicPort. Contact support rather than editing ports yourself. |
| Server is not in the list | List in community servers is off, or the server has not finished starting. |
| Joins, then drops after a while | Check the Console tab for a crash or out-of-memory message. See lag and crash fixes. |
| Wrong password | Compare with the server password set on the Startup tab. |
| Only you cannot join, friends can | A local network issue on your side, such as NAT loopback. Try a different network or use your server's address from another device. |
What to send support
If none of this works, contact support with the exact error text, the player's platform, the address they typed, and the last lines of the Console tab. That is usually enough to tell a server problem from a client problem. Our general can't connect guide covers firewalls and VPNs on the player's side, and what a game server IP and port are explains the address format.
Want a Palworld server that just works? See Palworld server hosting.
Frequently asked questions
What port does a Palworld server use?
The default is UDP 8211. Traffic is UDP, so forwarding TCP does nothing. On ChicagoServers the panel assigns the port and shows the address at the top of your server page.
How do I join a Palworld server by IP?
Join a multiplayer game and enter the full address with the port, such as 203.0.113.10:8211, then the password if the server has one.
Why does Palworld say connection timed out?
The game sent a join request and got no reply. Common causes are a server that is offline, an incomplete address, a version mismatch, or a platform that is not allowed by CrossplayPlatforms.
Why can't console players join my Palworld server?
Check that their platform is in CrossplayPlatforms. Host documentation says console players join through the community server list, so make sure the server is listed.
Does PublicPort change the Palworld server's port?
No. Palworld's documentation says PublicPort only sets the port shown for community servers and does not change the port the server listens on.
Why can I not join my own Palworld server but friends can?
This is usually a local network issue on your side, such as NAT loopback. Try another network or ask support to check the server from outside.