The short answer
Set the listening port with a launch argument such as -port=8211. PublicPort describes the externally advertised community-server port; it does not change the listening socket. Check startup, LAN access, firewall rules and any necessary router forwarding separately.
Different symptom or still not fixed? Find the next check →Key facts
- Listening-port argument
-port=8211- PublicPort
- Community-server public information; does not change the listening port.
- Test order
- Server startup → LAN connection → required external route
Find your symptom
Start with your symptom. Skip steps that do not apply to your setup.
| What you see | What to check | Go to |
|---|---|---|
| I want to change the listening port | Use the actual server launch arguments. | Step 1 |
| PublicPort did not change the connection port | Advertising and listening are separate. | Step 2 |
| LAN works but an outside player cannot connect | Compare the firewall, forwarding target and provider restrictions. | Step 3 |
Fixes, in order
Continue this issue
Private notes stay in this browser. Nothing is sent automatically. Back up important notes on My Page. PC settings are never changed by this site.
Step 1|Set the listening port at startup
Use the launch method for your installation.
Time: A few minutes
- Stop the dedicated server.
- For the Steam installation, open Palworld Dedicated Server Properties.
- Add -port=8211 to its launch options, or substitute your chosen port.
- For SteamCMD, add the argument to the command that launches PalServer.exe.
- Restart and confirm that the server is listening on the intended port.
Results that did not fix the problem help the next reader too.
Step 2|Check what PublicPort actually controls
Changing public information alone does not reconfigure the listening port.
Time: A few minutes
- Read PublicPort in the active PalWorldSettings.ini.
- To change the listening port, inspect the -port launch argument.
- For a community server, check that its advertised external port matches the intended external connection.
- Restart the server after changing configuration.
Results that did not fix the problem help the next reader too.
Step 3|Test local connectivity before external access
Avoid broad exposure while narrowing the failure.
Time: A few minutes
- Confirm the server starts without errors.
- From another PC on the LAN, try the server’s local IP and intended port.
- Check the Windows Defender Firewall permission for PalServer.
- Only if outside access is required, check the router’s forwarding destination IP and port.
- Compare the address and port entered by the player with the intended server endpoint.
Router screens and provider restrictions differ. Shared connections or CGNAT can prevent customer-controlled inbound access.
Results that did not fix the problem help the next reader too.
Important cautions
- Do not expose RCON or the REST API directly to the internet. The existing guide carries the official REST API warning to keep it on a LAN.
- Target only the required port; do not open a broad range as a shortcut.
- Keep administrator passwords and public IP addresses out of public articles and screen shares.
FAQ
Where do I change the server port?
Use -port=8211 in the dedicated server launch arguments, substituting the port you intend to use.
Why does PublicPort not change the listening port?
It supplies public community-server information. The listening port is controlled by the launch argument.
Why does LAN access work but outside access fail?
Check the forwarding destination, firewall rules and provider CGNAT or port restrictions. First verify that the local IP and chosen port match the running server.
Sources
English adaptation of the existing Japanese Windows Steam guide. Official server paths, port semantics and Steam requirements were rechecked. Existing save-layout and version-specific mod guidance is retained from the original review; this does not claim new game, restoration or network testing.
Pocketpair: server launch arguments (Japanese)Pocketpair: server configuration (Japanese)PalworldJapanese version of this page