Palworld Dedicated Servers can occasionally experience update, startup, and connection issues, especially after a Palworld Steam update or when third-party mods are installed. This guide will help you identify common problems, which files or settings to check in your ZAP-Hosting game server management, and the steps needed to restore normal operation.
Before starting troubleshooting, make sure you have access to your Palworld game server management and can open the server console as well as the Configuration tab (raw text view).
Required Access You need access to the ZapX customer account for your Palworld server to stop, start, reinstall the server, and edit configuration files.
About Configuration Files Most issues in this guide cannot be resolved by gameplay setting changes alone. If you need to check or manually adjust Palworld server settings, you will usually find the relevant file in the Configuration tab (raw text view) of your game server management.
For Palworld Dedicated Servers, the main server settings are typically stored in the following file:
Pal/Saved/Config/LinuxServer/PalWorldSettings.ini
In the ZAP-Hosting game server panel, you can usually open this file via the Configuration tab (raw text view).
PalWorldSettings.ini contains the central OptionSettings line with server values such as:
- Server name
- Password
- Admin password
- Player limits
- Gameplay multipliers
- PvP and raid settings
A typical structure looks like this:
[/Script/Pal.PalGameWorldSettings]
OptionSettings=(ServerName="[your_server_name]",ServerDescription="[your_server_description]",AdminPassword="[your_admin_password]",ServerPassword="[your_server_password]",PublicPort=8211,PublicIP="[your_server_ip]")
Be Careful When Editing Syntax
Palworld uses a single OptionSettings=(...) structure for many settings. Accidentally removing a comma, quotation mark, or bracket can prevent your server from starting correctly.
You should only edit PalWorldSettings.ini if:
- you need to correct an incorrect server or admin password
- you want to remove invalid values after a failed manual change
- you want to test if a startup issue is caused by a faulty configuration entry
After saving changes, restart the server to apply the new settings.
One of the most common issues with Palworld game servers is a failed Steam update.
This error usually indicates that the game files were not properly updated via Steam.
- Completely stop your Palworld server.
- Open your game server management in the ZapX customer account.
- Open the ZapX AI Agent for your game server and ask it to validate the Steam files or reinstall the server.
- Confirm the suggested action in the chat to execute it.
- Wait until the process is fully completed.
- Restart the server.
Why This Helps
File verification or reinstallation forces the server to redownload missing or corrupted Palworld Steam files. This is the most reliable solution for the 0x6 update status error.
Usually, no configuration changes are needed for this error.
| Problem | Config File Needed | Further Action |
|---|---|---|
app '2394010' state is 0x6 after update job | No | Stop server, verify files or reinstall, then restart server |
If players see Connection timed out, the cause is usually a startup failure, faulty mod configuration, or connection problem.
First, make sure the server has started successfully.
You can check this by:
- Viewing the server status in the ZapX customer account
- Opening the console and checking the normal startup output
- Testing if the server responds to console commands (if available)
If the server shows little activity and does not respond normally, it may have crashed during startup.
If you edited PalWorldSettings.ini shortly before the problem, open the file again in the Configuration tab (raw text view) and check for:
- missing commas
- incorrect quotation marks
- duplicate values
- invalid IP or password values
Example entries to check:
ServerName="[your_server_name]"
ServerPassword="[your_server_password]"
AdminPassword="[your_admin_password]"
PublicPort=8211
PublicIP="[your_server_ip]"
If unsure whether the configuration caused the problem, revert recent changes and restart the server.
If Palworld just received an update and you use mods or UE4SS, the server may be incompatible.
In this case, you should:
- Stop the server.
- Create a backup if available in your product management.
- Remove or update installed mods.
- Restart the server and test the connection.
Mod Compatibility After Updates Palworld Steam updates can break server-side mods. If the problem occurred right after an update, mods are one of the first causes to check.
Palworld clients can have trouble connecting correctly via the in-game "Recent Servers" list.
Instead, connect directly using your server's IP and port.
Use this format:
[your_server_ip]:8211
Replace [your_server_ip] with your actual game server IP address.
A timeout can also occur in certain world states, for example, if a guild member leaves the guild while others are offline.
Possible solutions include:
- The affected player rejoins the guild
- The world is restarted
- A backup is restored if the world remains unusable
Risk with World Data If you suspect world or save corruption, avoid repeated manual changes without a backup. Create or restore a backup before making destructive changes.
Steam-related connection problems can prevent your Palworld server from updating or being reachable.
This message usually relates to a temporary Steam service issue, not a faulty Palworld configuration.
- Wait 5 to 10 minutes and try again
- Check if Steam is undergoing maintenance or outages
- Avoid repeated restarts during a temporary Steam outage
Steam maintenance often occurs on Tuesdays, so short interruptions are possible.
If your server keeps trying to update during a Steam outage, it may stay offline until Steam responds normally again.
If your product has an automatic update feature in the panel, you can temporarily disable it until the outage is over.
Handling Temporary Steam Outages If the server worked before and suddenly shows Steam connection attempts, it’s usually better to wait briefly rather than immediately changing configuration files.
Usually, no configuration changes are needed for this problem.
| Problem | Config File Needed | Further Action |
|---|---|---|
Connecting anonymously to Steam Public...Retrying | No | Wait, check Steam status, temporarily disable automatic updates if needed |
If a message appears that the match uses an incompatible game version, server and client versions do not match.
- Restart the Palworld server.
- Wait until the server has fully started.
- Update your local Palworld client via Steam if needed.
- Try connecting again.
If the server still reports an incompatible version, the update may not have been applied correctly. Then repeat file verification or reinstallation as described above.
A version conflict is usually not caused by PalWorldSettings.ini. However, if the server does not start after an update, it is still worth checking the configuration file for validity and unchanged content.
Some startup messages may seem critical but are expected behavior.
This message often appears at startup and is usually harmless for Palworld Dedicated Servers in this context.
You normally do not need to edit any files or run additional commands just because of this message.
Usually Harmless If the server otherwise starts normally and players can connect, this Steam library message can usually be ignored.
The following table summarizes the most important checks for troubleshooting Palworld.
| Problem | File to Check | Path in Server Files | Manual Changes Needed | Restart Needed |
|---|---|---|---|---|
Update error 0x6 | Usually none | Not required | No | Yes |
| Connection timed out after config edit | PalWorldSettings.ini | Pal/Saved/Config/LinuxServer/PalWorldSettings.ini | Yes, check OptionSettings values | Yes |
| Connection timed out after mod update | Mod files, no standard config | Varies | Remove or update incompatible mods | Yes |
| Steam retry loop | Usually none | Not required | No | Sometimes, but waiting first is recommended |
| Incompatible game version | Usually none | Not required | No | Yes |
steamclient.so warning | None | Not required | No | No, if server runs normally |
If you don’t know where to start, proceed as follows:
- Check if the server is online.
- Try connecting with direct IP instead of "Recent Servers".
- Check if Palworld or Steam recently had an update.
- Remove or update mods if you use any.
- Check
PalWorldSettings.iniin the Configuration tab (raw text view) for invalid syntax. - Restart the server.
- Verify or reinstall game files if update errors persist.
This way, you can rule out the most common causes first without making unnecessary changes.