-
Notifications
You must be signed in to change notification settings - Fork 0
Backup and Restore
Only Administrators can create or restore PalCenter backups.
A current PalCenter backup includes:
- Configured Palworld servers and Administrator passwords
- Notification providers and credentials
- Historical metrics, events, and active-player tracking
- Users, roles, and password hashes
- Internal system configuration and session-signing secret
- Backup metadata, including format, PalCenter version, and creation time
The result is a single file named similar to:
palcenter-backup-2026-07-24.tar.gz
Backups contain sensitive information. Store them in encrypted, access-controlled storage.
- Sign in as an Administrator.
- Open Backup & Restore.
- Review the current data availability.
- Select Create and Download Backup.
- Store the downloaded archive safely.
PalCenter briefly pauses data services while creating a consistent archive.
- Create and download a backup of the current installation first.
- Under Restore a backup, select a
.tar.gzarchive created by PalCenter. - Select Restore Backup.
- Read the replacement warning.
- Select Confirm Restore.
PalCenter validates the archive, required files, databases, users, and system configuration before replacing any data. If replacement or reopening fails, PalCenter attempts to recover the previous data.
A restore replaces current server connections, notifications, history, users, roles, login credentials, and system configuration with the backup contents. Because the session-signing secret may change, users may need to sign in again.
Do not edit or repack a PalCenter archive. Invalid or incomplete uploads are rejected before they can replace application data.
You may also stop the container and back up the complete /app/data volume.
Never copy only a live SQLite file while PalCenter is running.
PalCenter v1.1.1 · Repository · MIT License
PalCenter v1.1.1
Getting Started
Administration
Deployment
Troubleshooting
Project