Updating Your Conan Exiles Server
How to update a Conan Exiles dedicated server through the panel, including pre-update steps to protect your save data.
Update Process Overview
Conan Exiles server updates are delivered through SteamCMD using App ID 443030. On WISP/Pterodactyl panels, updates are triggered through the panel UI — the panel runs SteamCMD in the background to pull the latest build from Steam.
Pre-Update Checklist
Before triggering an update:
- Notify players — announce the update in your community channels. Give at least 10–15 minutes notice.
- Back up the save database — copy
ConanSandbox/Saved/game.dbto a safe location. Updates can occasionally introduce issues that corrupt saves on first load with a new binary. - Note your config files — configs are not overwritten by SteamCMD, but verify this is still the case for your egg after updating.
- Stop the server from the panel before running the update.
Running the Update
In the WISP or Pterodactyl panel:
- Navigate to your server.
- Go to the Reinstall or Update option (varies by egg implementation).
- Confirm the action.
The panel will run SteamCMD with arguments similar to:
steamcmd +login anonymous +app_update 443030 +quit
Wait for SteamCMD to complete. This can take several minutes depending on the update size and node bandwidth.
Post-Update Steps
- Check that config files are intact — verify
ServerSettings.ini,Game.ini, andEngine.inihave not been reset. - Start the server and monitor the log for errors:
ConanSandbox/Saved/Logs/ConanSandbox.log - Connect to the server and confirm the build version matches the expected patch version.
- Check that mods are still compatible. Game updates frequently break mods. See the mods article for how to temporarily disable mods for testing.
Forced Validation
If the server behaves unexpectedly after an update, run a forced file validation through SteamCMD:
steamcmd +login anonymous +app_update 443030 validate +quit
The validate flag checks file integrity and re-downloads any corrupt or missing files. This does not affect your save data or config files.
Keeping Mods Up to Date
After a game update, mod authors typically release compatibility updates within 24–72 hours. If a mod is incompatible with the new game version:
- Stop the server.
- Comment out or remove the incompatible mod from
modlist.txt(prefix the line with//or delete the line entirely). - Start the server to confirm stability.
- Re-add the mod once the author releases a compatible version.
Clients with outdated or incompatible mods will fail to join. Keeping mods current reduces connection issues.
Automated Updates
Some panel configurations support scheduled server stops and SteamCMD update triggers via cron. If your setup supports this, schedule updates during low-traffic hours. Always ensure the backup step is part of any automated update routine.