---
title: "Palworld \"Connection Timed Out\": Every Cause and Fix (1.0)"
description: "Palworld connection timed out? It means the server never answered. Fixes by join method: invite code, IP and port, community list, and self-hosted NAT."
url: "https://www.gameserverkings.com/knowledge-base/palworld/palworld-connection-timed-out/"
category: "Palworld"
category_url: "https://www.gameserverkings.com/knowledge-base/palworld/"
published: "2026-10-28T03:25:57.460Z"
updated: "2026-10-28T03:25:57.460Z"
source_format: "markdown"
site: "GameServerKings"
---

# Palworld "Connection Timed Out": Every Cause and Fix (1.0)

"Connection timed out" in Palworld means your game sent a join request and got no answer in time. Either the server isn't running at that address yet, the address or port is wrong, or something between you and the server is dropping its UDP traffic. It is a reachability error, not a save or account problem. The fix depends on how you are joining: by invite code, by IP, or through the community server list.

Players report the full message in slightly different words depending on platform and language, most often as *"Connection timed out"* followed by *"Either the server destination is down or its IP address has changed."* If you see that, work through the section below that matches your setup.

> [!NOTE] Checked against Palworld **v1.0.5** (15 September 2026)
> Since v1.0.4, Pocketpair says a version mismatch shows its own error that names the server's version. So if you get a plain timeout, the build is usually not the problem. Check reachability first.

## First, how are you joining?

| How you join | Who hosts the world | Most common timeout cause |
|---|---|---|
| **Invite code** (co-op) | A friend's PC or console | The code is from an old session, or the host's own network |
| **IP and port** (dedicated server) | A server: rented, or one you run yourself | Wrong port, server still starting, or UDP blocked |
| **Community server list** | A dedicated server started with `-publiclobby` | The server advertises the wrong public IP or port, or you are on the same home network as the server |

Xbox, PS5 and Game Pass PC players can't type an IP. They can only reach a dedicated server through the **Community server** tab. If a console friend times out, the community-list row is the one that applies to them.

## Joining a hosted server

On a rented server, port forwarding is already done. When one of our Palworld servers times out, it is almost always one of these, in this order:

1. **The server is still starting.** A fresh boot downloads any game update and then loads the world. If you join before that finishes, you time out. Watch the **Console** tab and join once the world has loaded. A first-ever boot takes longer, because it downloads the full server files.
2. **The port is wrong.** Palworld's default is UDP `8211`, but a host can give each server its own port. Copy the full **Address** from the top of your server page, IP *and* port, for example `203.0.113.10:8211`. A missing or wrong port is one of the most common causes of a timeout on a server that is otherwise healthy.
3. **The server crashed or is stopped.** If everyone times out at once, open the Console. A crash usually leaves the last lines of the log there, and a restart brings it back. If it keeps crashing, the log is what we need in a ticket.
4. **A console friend searched in the wrong place.** They need the **Community server** tab and your exact server name. Also check that `CrossplayPlatforms` in `PalWorldSettings.ini` still lists their platform. The default is `(Steam,Xbox,PS5,Mac)`. [Is Palworld Crossplay?](/knowledge-base/palworld/palworld-crossplay/) has the platform matrix.
5. **Only one player times out.** Then the server is fine, and the problem is on that player's side: a VPN, a firewall, or antivirus filtering the game's traffic. One Steam forum report after 1.0 traced this to Malwarebytes blocking the connection, and nothing showed up in the server log. Have them try once from a phone hotspot. If it works there, the problem is on their network.

Our Palworld servers start with `-publiclobby` and pass their own port as `-publicport`, so the community list points at the right address. If the server shows up in the list but joining from it times out, connect by IP once. If that also fails, it is one of the causes above, not the listing.

## Self-hosting: ports, firewalls and NAT

Pocketpair's requirements page lists **UDP port 8211** (default, changeable with `-port=`) and says router configuration is required. In practice, most self-hosted timeouts come from these:

- **Forwarding TCP instead of UDP.** Palworld's game traffic is UDP. Forward UDP `8211`, or whatever you set with `-port=`, to the machine running PalServer.
- **The OS firewall.** Pocketpair notes that the Windows options need separate Windows Firewall settings, and that on Linux "in some cases, Linux security settings may also need to be changed". On Windows, allow `PalServer` (or UDP 8211 inbound). On a Linux box running `ufw`, that is `sudo ufw allow 8211/udp`.
- **Joining your own server through your public IP.** Pocketpair says: "If your router does not support Hairpin NAT, you will not be able to connect to community servers hosted within the same network." Friends outside can join, but you time out. On a PC, connect by the server's **LAN** IP (for example `192.168.1.50:8211`) instead. Consoles can't type an IP, so a console on the same network as a home-hosted server depends on the router. One self-hoster on the CubeCoders forum (July 2026) reported this with two PS5s on the same network: the first connected and the second timed out.
- **The community list shows the wrong address.** The server detects its public IP and port automatically. If that comes out wrong, behind a proxy or a second router for example, set `-publicip=` and `-publicport=` at launch. Pocketpair says `-publicport` "does not change the port number itself that the server uses for listening".
- **CGNAT.** If the WAN IP on your router's status page doesn't match what an "what is my IP" site shows, your ISP is sharing one public IP between several customers. Port forwarding can't work behind that, whatever you configure. You'll need a public IP from your ISP, or a host.
- **Not enough RAM.** Pocketpair recommends 16 GB, and 32 GB for larger servers. It warns that 8 GB "is also bootable, but increases the possibility of server crashes due to out of memory". A server that crashes under load looks exactly like a timeout to everyone still trying to connect.

Pocketpair also deprecates running its official Docker image under **Docker Desktop**, citing storage performance and a higher risk of save corruption. If you run it in Docker, run it on a Linux host.

## Co-op invite codes

In co-op the "server" is the host's game, so the host's connection and the host's session decide everything.

- **Use the code from the current session.** If the host restarted the game or reloaded the world, get the new code. [Palworld Multiplayer](/knowledge-base/palworld/palworld-multiplayer/) walks through hosting and joining step by step.
- **Check Multiplayer is on** in the host's world settings.
- **Co-op holds four players, host included.** A fifth player won't get in.
- **The host's network matters.** A strict NAT or a VPN on the host's side can stop friends connecting even when the code is right. If the same friends can join someone else's co-op world, the problem is the host's network.

If your group keeps fighting co-op connections, or needs more than four players, the world can move to a dedicated server that stays online on its own. [Managing your Palworld world and save files](/knowledge-base/palworld/managing-your-world/) covers the upload, and [Palworld Save Tools](/knowledge-base/palworld/palworld-save-tools/) covers the host-character fix that move needs.

## Timeouts in the middle of a session

Getting dropped with a timeout after playing for a while is a different problem from failing to join:

- **The server stopped or crashed.** Check the Console for a crash, then check memory use. See the RAM point above if you host it yourself.
- **The server is on an old build.** v1.0.2 fixed a bug where "all players could be disconnected during the Panthalus battle on dedicated servers". Restart the server so it updates, and update every client.
- **The connection is unstable.** Since 1.0, the game shows an icon when your connection to the server is unstable. If that icon appears before the drop, look at your own connection or route first. If it doesn't appear and the whole server is lagging, see [the performance section of our World Settings guide](/knowledge-base/palworld/world-settings/).

## Quick reference

| Symptom | Likely cause | Fix |
|---|---|---|
| Everyone times out right after Start | World still loading | Wait for the console to finish loading |
| Times out by IP, server is running | Missing or wrong port | Paste the full Address, IP and port |
| Everyone times out, server was fine before | Crash or stop | Check the Console log, then restart |
| Friends outside can join, you can't (self-hosted) | No hairpin NAT | Join by LAN IP from the PC |
| Nobody outside can join (self-hosted) | UDP not forwarded, firewall, or CGNAT | Forward UDP 8211, allow it in the firewall, check the WAN IP |
| Console friend times out from the community list | Listing advertises the wrong IP or port, or same-network NAT | Set `-publicip`/`-publicport`, or test from outside the network |
| One player times out, others are fine | That player's VPN, firewall or antivirus | Try a hotspot, then whitelist the game |
| Invite code times out | Old code, or the host's network | New code from the host's current session |
| Error names a version number | Version mismatch, not a timeout | Update the client, restart the server |

If you're on one of our servers and the list runs out, send us the last 50 lines of the Console in a ticket. The log usually shows whether the server ever saw your connection attempt.

## Common Questions

### Do I need to port forward to join a rented Palworld server?

No. Port forwarding is only for hosting at home. On a rented server the port is already open. You need the right IP *and* port, which is the full Address in your panel.

### What port does Palworld use?

UDP 8211 by default. A server can listen on another port with `-port=`, and hosts often give each server its own port. RCON and the REST API use separate ports and are not involved in joining.

### Why can my friends join my server but I get "connection timed out"?

If the server runs on your home network, your router probably doesn't support hairpin NAT. Pocketpair documents this exact limitation. Join with the server's LAN IP instead of the public one.

### Can a version mismatch cause "connection timed out"?

Not usually, since v1.0.4: a mismatch now shows its own error with the server's version. Restarting the server after a patch is still worth doing, so that the server and everyone's game are on the same build.

### Why does only my Xbox or PS5 friend time out?

Consoles can only join through the community server list, so they rely on the server advertising the correct public address. On a home-hosted server, a console on the same network can also hit the hairpin NAT limit. On a rented server, check that their platform is listed in `CrossplayPlatforms`.

## What to Read Next

- [Setting Up Your Palworld Dedicated Server](/knowledge-base/palworld/getting-started-with-your-server/): first boot and connecting by IP
- [Palworld Multiplayer](/knowledge-base/palworld/palworld-multiplayer/): co-op invite codes, dedicated servers and the community list
- [Is Palworld Crossplay?](/knowledge-base/palworld/palworld-crossplay/): which platforms can join which servers
- [Palworld Dedicated Server World Settings Explained](/knowledge-base/palworld/world-settings/): `CrossplayPlatforms`, `bAllowClientMod` and the rest of the file
- [Palworld server hosting](/games/palworld/): ports already open, and the address is in your panel

---

Made with 💜 by GameServerKings