Palworld Server Not Showing Up? Here's How to Fix It

Most Common Cause: Incorrect Port Configuration

Palworld's dedicated server uses port 8211 UDP by default. This is the most frequent source of connection problems because many people either forget to open the port, open the wrong port, or configure TCP instead of UDP.

Your server needs port 8211 open for UDP traffic — not TCP. Palworld uses UDP for game communication. If your firewall or port forwarding rule only allows TCP on 8211, the server will start fine but nobody will be able to find or connect to it.

If you changed the port in PalWorldSettings.ini, make sure your firewall and port forwarding rules match the new port number. A mismatch between the config file and the firewall rules is a classic mistake.

Check 1: Port Forwarding and Firewall Rules

If you're self-hosting on your home network, you need to configure port forwarding on your router. Log into your router's admin panel (usually 192.168.1.1 or 192.168.0.1) and create a port forwarding rule:

External port: 8211
Internal port: 8211
Protocol: UDP
Internal IP: The local IP of the machine running the server (e.g., 192.168.1.100)

Also check your operating system's firewall. On Windows, you need to allow the Palworld server executable through Windows Defender Firewall. On Linux, check ufw or iptables rules. You can verify the port is open from outside your network using an online port checker tool — just make sure to test UDP specifically, as many port checkers default to TCP.

Check 2: Server Version Mismatch

Palworld updates frequently, and the server and client versions must match exactly. If your dedicated server is running version 0.3.2 and your client updated to 0.3.5, you won't see the server in the browser and direct connect will fail.

To fix this, update your server to the latest version. If you installed via SteamCMD, run the update command:

steamcmd +login anonymous +app_update 2394010 validate +quit

If you're using a hosting provider, check their panel for an update option. On kranky.io, server updates are handled automatically or through a one-click update in the dashboard.

Check 3: Community Server Toggle

When browsing servers in Palworld, there are two tabs: Official Servers and Community Servers. Your dedicated server will only appear under Community Servers, not Official. If you're looking in the Official tab, you won't find it — switch to Community.

Additionally, it can take several minutes for a newly started server to appear in the Community browser. The server needs to register with the master server list, which doesn't happen instantly. Wait 3-5 minutes after the server finishes loading before checking the browser.

Check 4: Direct Connect vs Server Browser

If the server browser isn't working, try connecting directly. In Palworld, select "Join Multiplayer Game" and use the direct connect option with your server's IP address and port:

your.server.ip:8211

If direct connect works but the server browser doesn't show your server, the issue is with the server browser registration — not with your server itself. This can happen when the master server list is under heavy load or when your server hasn't been running long enough to register.

For players on your local network, use your machine's local IP address (like 192.168.1.100:8211). For players outside your network, use your public IP address. You can find your public IP by searching "what is my IP" on Google.

Check 5: Server Still Starting Up

Palworld dedicated servers are resource-intensive and can take 2-3 minutes to fully boot, especially on first launch or after updates. During this time, the server won't accept connections and won't appear in the browser.

Watch the server console for the startup completion message. You'll see log output scrolling as the world loads. The server is ready when you see a line indicating it's listening for connections. Don't try to connect until this message appears.

If your server is taking more than 5 minutes to start, you might not have enough RAM. Palworld servers need at least 8 GB of RAM for a smooth experience. With 4 GB, the server might start but will be sluggish and could fail to register with the browser.

Still Not Working? Check These

Server password: If you set a server password in PalWorldSettings.ini, players need to enter it when connecting. An incorrect password won't show an obvious error — the connection just fails silently in some versions.
ISP blocking: Some ISPs block incoming connections on certain ports. If you've verified everything else, try changing the port to something like 27015 or 7777 in your config and port forwarding rules.
Double NAT: If your ISP provides a router and you have your own router behind it, you might be behind double NAT. You'll need to set up port forwarding on both routers, or put the ISP router in bridge mode.
VPN interference: If you or your players are using a VPN, it can interfere with direct connections. Try disconnecting the VPN and connecting with your raw internet connection.

The Easier Option: Use a Hosting Provider

Self-hosting a Palworld server means dealing with port forwarding, firewalls, dynamic IP addresses, keeping the server updated, and leaving your PC running 24/7. A dedicated hosting provider handles all of this for you — the server gets a static IP, ports are pre-configured, and updates are managed through a dashboard.

For a full walkthrough of Palworld server configuration, including PalWorldSettings.ini and admin commands, check our Palworld dedicated server setup guide.