If your Palworld server is not showing up, it may still be joinable by direct IP. Two Depresso Pals in an icy Palworld cave with glowing blue mushrooms.The community server list and direct connection are related, but they are not the same thing. A server can fail to appear in search because of public lobby settings, ports, firewall rules, public IP detection, version mismatch, password settings, platform limits, or simple list delays.
Start with direct connection first. It tells you whether the Palworld server itself works before you spend time fixing the public list.
Confirm The Server Is Actually Running
Check the console or hosting panel first. The server should be started, not updating, crashed, or stuck during launch.
If you self-host on Windows, make sure PalServer.exe is still running. Open Task Manager and look for the Palworld dedicated server process. You can also check from PowerShell with:
Get-Process PalServer -ErrorAction SilentlyContinue
If nothing appears, the server is not running. Start it again from the server folder and watch the console for errors. Do not change ports, delete saves, or edit multiple settings until the server can stay online normally.
Try Direct IP Connection
Ask one player to connect directly with:
public-ip-address:8211
The default Palworld server port is UDP 8211. If you changed the port, use your custom port instead.
This is usually the best way to test a Palworld server. The in-game server list can be limited to a certain number of results, so your server may still not appear even when it is online and configured correctly. Direct IP connection avoids the search list and tells you whether players can actually reach the server.
If direct IP works, the server is running and reachable. The issue is probably the community listing, search delay, platform requirement, or server name.
If direct IP does not work, focus on Windows Firewall, router port forwarding, version mismatch, password settings, or server startup issues.
When testing from the same home network as the server, remember that some routers cannot connect back to a server hosted inside the same network. Ask someone outside your network to test too. You can also test locally with the server PC’s private IP, such as:
192.168.1.50:8211
That local address only works inside your own network. Players outside your home need your public IP or community server listing.
Use The Public Lobby Startup Option
To make your Palworld server appear in the in-game community server list, start it with the -publiclobby option.
On Windows, open PowerShell or Command Prompt, go to your Palworld server folder, and start the server like this:
cd "C:\steamcmd\steamapps\common\PalServer"
.\PalServer.exe -publiclobby
If you normally use performance arguments, keep them in the same startup command:
.\PalServer.exe -publiclobby -useperfthreads -NoAsyncLoadingThread -UseMultithreadForDS
Restart the server after changing startup options. The community list may take a little time to update, so do not assume it failed instantly if your server does not appear right away.
Check Public IP And Public Port
If the server starts as a public lobby but still does not list correctly, try setting the public listing values manually. These help the server report the correct public address.
Example:
.\PalServer.exe -publiclobby -publicip=203.0.113.25 -publicport=8211
Replace 203.0.113.25 with your real public IP address. Do not use a private address like 192.168.1.50, 10.0.0.25, or 172.16.0.10. Those only work inside your own network.
If your public IP changes often, your Palworld server listing may stop working later. This is one of the common problems with self-hosting from home.
Open UDP Port 8211
For self-hosting, allow UDP 8211, or your custom -port value, through Windows Firewall and your router.
Open PowerShell as Administrator and run:
New-NetFirewallRule -DisplayName "Palworld UDP 8211" -Direction Inbound -Protocol UDP -LocalPort 8211 -Action Allow
Then log in to your router and forward UDP 8211 to the private IP address of the server computer.
For example:
- External port:
8211 - Internal port:
8211 - Protocol: UDP
- Destination IP: your server PC’s local IP address
Only forward the ports you need. Avoid exposing admin tools like REST API or RCON directly to the internet unless you have secured them properly.
Check Platform And Version
Palworld servers can support multiple platforms, but some players may need the server to be available as a community server instead of relying only on direct IP.
Everyone should also update Palworld. A version mismatch can make a server look missing or cause connection failures.
If you installed the server with SteamCMD on Windows, update it with:
cd "C:\steamcmd"
.\steamcmd.exe +login anonymous +app_update 2394010 validate +quit
After the update, restart the server and test again. Make sure the game client and server are both on the same version before changing more settings.
Review Server Name And Password
Stop the server before editing settings. Then open:
C:\steamcmd\steamapps\common\PalServer\Pal\Saved\Config\WindowsServer\PalWorldSettings.ini
Check these settings:
ServerNameServerDescriptionServerPasswordServerPlayerMaxNum
Keep the OptionSettings=(...) format intact. Do not remove commas, quotes, or brackets unless you know exactly what you are changing. If the formatting breaks, the server may ignore the settings or fail to start.
Choose a unique server name too. Generic names are harder to find in a busy community list.
How Palworld Server Hosting Avoids Home Network Problems
When self-hosting, server visibility depends on startup arguments, router forwarding, Windows Firewall rules, IP detection, public lobby settings, and your home network setup. One small mistake can make the server disappear from search or stop direct IP connections from working.
Dedicated Palworld server hosting removes most of those home network issues. You do not need to expose your home IP, fight router menus, or guess whether your port forwarding rule is correct.
With Pine Hosting, you can manage your Palworld server through a panel with console access, restarts, file manager, server configuration options, schedules, DDoS protection, and support. That makes troubleshooting easier because you can quickly check whether the server is online, restart safely, update settings, and confirm the correct connection details.
What To Do If It Still Does Not Show
Keep direct IP available as a backup while you troubleshoot the list. Record your startup command, public IP, port, platform, password setting, server version, and whether direct IP works.
If the list still fails but direct IP works, tell players to join by address temporarily. That lets people keep playing while you fix the community listing.
The goal is not just appearing in search. The goal is making sure players can reliably reach the Palworld server without risking the save or changing random settings.
Make Your Palworld Server Easier To Find
If your Palworld server keeps disappearing from search, direct IP tests fail at home, or port forwarding feels too confusing, Pine Hosting’s Palworld server hosting gives you a cleaner way to run your world.
With Pine Hosting, you get a dedicated Palworld server that is easier to manage from the start. You can restart the server, check the console, access files, update settings, schedule tasks, and manage important options through the panel instead of jumping between Windows Firewall, router settings, and public IP checks.
That is especially useful for a multiplayer Palworld server with friends or a growing community. If you are looking for the best Palworld hosting for easier management and more reliable connections, a hosted setup helps avoid common home network issues while giving you support when connection problems happen.
Instead of spending hours troubleshooting why your Palworld server is not showing up, you can focus on keeping the server online, sharing the right connection details, and giving players a smoother place to play.
