Palworld 1.0: Can't connect to server — every fix
Fix a Palworld 1.0 connection in the right order. Match client and server versions, use the Steam IP or the Xbox and PS5 community name, wait until the world is ready, open UDP 8211, share or clear the password, and drop mods that block consoles.
If Palworld says it failed to connect, work through these checks in
order. Do not wipe the world or delete PalWorldSettings.ini first.
After a Palworld 1.0 patch, the usual cause is a client that updated
before the dedicated server.
Stop as soon as one fix works. If you are helping somebody else, test with one player before asking the whole group to retry.
1. Match the client and server versions
If you see a version mismatch, or Xbox shows:
Sorry, you're currently prevented from playing with people on platforms other than the Xbox network.
the dedicated server is behind the player's game. Steam, Xbox, and PlayStation can ship a Palworld patch hours before a self-hosted server takes the matching dedicated build.
Update the player's game
Close Palworld completely, install every available update from the platform store, and relaunch it. Do not leave an old game process suspended in the background.
Update the dedicated server
Stop the server cleanly. On berrybyte, Auto update on start installs the current dedicated-server build when the process starts. Restart once after the patch is live. If you self-host through SteamCMD:
steamcmd +force_install_dir /path/to/palworld +login anonymous +app_update 2394010 validate +quitStart the server and compare versions
Wait until the world has finished loading. Compare the version on the player's title screen with the version in the server startup log or Settings → Game Settings. They must match.
On berrybyte, one restart after Pocketpair ships the patch is the whole update. See Update your Palworld server and Fix the Xbox platform error. If you do not want to run SteamCMD after every hotfix, rent a Palworld server that handles updates.
2. Use the right join path
Steam and PC can join by IP. Xbox and PS5 cannot. They search Community Servers by the exact ServerName. Mixing those two paths looks like a dead server.
Steam and PC: paste host:port
On berrybyte, copy Server address from Overview. In Palworld, open Join Multiplayer Game, click the connect field at the bottom of the list, paste the address, and press Connect. Do not retype the port by hand.
Xbox and PS5: search the server name
Open Join Multiplayer Game → Community Servers and search the exact name from Settings → Game Settings. Wait a minute after a restart. The community list lags behind a fresh boot.
Confirm the server is listed for consoles
Allowed platforms must include Xbox or PlayStation (Crossplay on
berrybyte). Self-hosters also need -publiclobby so the name
appears in Community Servers. See
Set up an Xbox dedicated server.
The full Steam walkthrough is How to join a Palworld server. The console walkthrough is Join a Palworld server on Xbox. A hosted panel keeps the Steam address and the community name in one place. Rent a Palworld server if you would rather not assemble both yourself.
3. Wait until the world is actually ready
A Palworld dedicated server can accept a process start long before the world is joinable. Connecting during that window returns Failed to connect to server even when the address is correct.
Confirm the process is running
On berrybyte, Overview must show the server as running, not stopped or still installing an update.
Read the console
Wait until the startup log finishes loading the world. A first boot after a Palworld 1.0 patch can sit there for several minutes.
Retry one client
Test with one Steam or one console client. Do not ask the whole group to mash Connect while the world is still generating.
4. Check the UDP game port
Palworld speaks UDP on the game port. The documented default is 8211. Steam's browser also needs a query port, commonly 27015. TCP on the same numbers does not create a working game path.
Use the port the server bound
On berrybyte, copy the address on Overview (IP before the colon, port after). That allocated UDP port is the one that matters. Do not assume 8211. On a self-hosted server, forward the listen port from the launch arguments plus the query port.
Forward UDP, not only TCP (self-host)
Every firewall and router between the machine and the internet must allow UDP on that game port. If Steam players time out while the process looks healthy, port forwarding failed somewhere.
berrybyte opens the allocated game and query ports for you. Self-hosters who are fighting NAT can rent a Palworld server that already has those ports reachable.
5. Share or clear the server password
A Palworld password is optional. If it is set, every player must enter that exact string. A wrong password often looks like a failed connection rather than a clear "access denied" dialog.
See whether a password is actually set
On berrybyte, open Settings → Game Settings and read the server password. The dedicated walkthrough is Set a Palworld server password.
Send the exact string, or clear it
If you want a public test, clear the field, save, and restart. If you want it private, send the string again and check capitalisation, spaces, and characters that chat apps rewrite.
Restart, then test one player
Password changes are read at boot. Test with one client at the password prompt before the rest of the group retries.
6. Remove mods from a console server
Xbox and PS5 cannot install Palworld .pak mods. A plugin that
requires the same file on every client makes the server PC-only in
practice, even when Crossplay is enabled.
Test with a clean vanilla server
Stop the server, move the mods out of Paks, and start the
same world vanilla. Back up the save first if it contains items
added by mods.
Retry from the console
If the Xbox or PS5 player can now join, one of the removed files required a modded client.
Choose one audience
Keep an unmodded crossplay world for PC and console, or maintain a separate modded PC world. Do not promise both from one server unless every file is explicitly server-side-only.
See Install mods on a Palworld server. If your group includes consoles, rent a vanilla crossplay server that keeps the compatible setup separate.
If none of the six fixes worked
Confirm the dedicated server reached a ready state before testing again. Then check the leftover causes:
- Copy Server address again. A stale Discord pin after a port change is a common miss.
- Steam players can use the in-game browser while the community list is still catching up. Console players cannot.
- Check berrybytestatus.com and steamstat.us if every Palworld server disappeared at once.
- Check console parental and privacy controls permit online and cross-network play.
- Try Cloudflare WARP or another VPN if only one ISP path times out.
Paste host:port from Overview into Join Multiplayer Game.
Join from XboxSearch Community Servers by the exact ServerName.
Update the dedicated serverPull the matching Palworld 1.0 dedicated build after a patch.
Fix the Xbox platform errorThe prevented-from-playing dialog is usually a version gap.
Set up Palworld hostingAutomatic updates, Crossplay, community listing, and support.
Frequently asked questions
Why can't I connect to a Palworld server?
Check the game version first. Pocketpair often updates the client before a dedicated server catches up. If the versions match, use the right join path, wait until the world has finished loading, confirm UDP 8211, share or clear the password, and remove incompatible mods in that order.
Why does Palworld say Failed to connect to server?
The dedicated server is offline, still generating the world, or the address was typed wrong. Copy host:port from Overview on berrybyte instead of retyping it. Xbox and PS5 never use that address. They search Community Servers by the exact ServerName.
Why can't Xbox or PS5 find a Palworld server?
Console clients cannot join by IP. Search Community Servers for the exact ServerName. The dedicated server must list itself with a public lobby and allow Xbox or PlayStation in CrossplayPlatforms. berrybyte already enables Crossplay and the community listing.
What ports does a Palworld dedicated server use?
UDP 8211 is the default game port. Steam also uses a query port, commonly 27015, so the server can appear in the PC browser. berrybyte opens both. On a self-hosted box, forward the ports the process actually bound, not assumed defaults.
Why does Palworld show a version mismatch or the Xbox platform error?
The dedicated server is on an older Palworld build than the player. Update the client from the store, then restart the server so Auto update on start pulls the matching dedicated build. The Xbox message "prevented from playing with people on platforms other than the Xbox network" is usually this same version gap.