-
Notifications
You must be signed in to change notification settings - Fork 0
Unraid Deployment
PalCenter is available through the Unraid Community Applications catalog. This is the recommended installation method for Unraid users.
- Open the Unraid Web UI.
- Navigate to Apps → Community Applications.
- Search for PalCenter.
- Select and install PalCenter.
- Review and configure the application settings.
- Start the container.
- Open
http://<unraid-ip>:3000.
The official Unraid template configures PalCenter to run as the non-root
nobody:users account:
- UID
99 - GID
100
The template also maps /mnt/user/appdata/palcenter on the Unraid host to
/app/data in the container. This location stores PalCenter configuration,
users, sessions, notifications, history, and other persistent application
data.
The official template handles the UID/GID configuration. Users installing from
Community Applications should not need to run chmod or chown commands.
| Setting | Container value | Suggested host value |
|---|---|---|
| Repository | ghcr.io/shanebionic/palcenter:v1.1.1 |
— |
| Web interface | 3000/tcp |
3000 or another available port |
| API | 3001/tcp |
Advanced/optional use only |
| Persistent data | /app/data |
/mnt/user/appdata/palcenter |
| Container user | 99:100 |
Unraid nobody:users
|
Access the web interface at:
http://<unraid-ip>:3000
Port 3001 provides direct API access for advanced use. It is not required for
normal use of the PalCenter web interface. If published, restrict it to a
trusted management network.
Community Applications is recommended for Unraid. If you intentionally deploy PalCenter with Docker Compose instead, configure:
PALCENTER_UID=99
PALCENTER_GID=100and map:
/mnt/user/appdata/palcenter:/app/data
Do not map Palworld save directories or the Docker socket.
PalCenter verifies that the directory is writable at startup. If the host does
not permit permission tightening but the directory remains usable, PalCenter
logs a warning and continues. If UID 99 and GID 100 cannot write, startup
fails safely.
- Start the container.
- Open
http://UNRAID-IP:WEB-PORT. - Create the first Administrator.
- Add a Palworld server using a LAN IP or DNS name reachable from the container.
Do not use localhost for a remote Palworld server.
Keep the appdata mapping when recreating the container. The official template continues to apply the Unraid UID/GID mapping. Create a PalCenter backup before upgrades. For a cold backup, stop the container and copy the complete appdata directory; never copy only a live SQLite file.
PalCenter also remains available as a standard Docker deployment for non-Unraid systems. See Docker Installation.
For project updates and support, visit the PalCenter repository or issue tracker.
PalCenter v1.1.1 · Repository · MIT License
PalCenter v1.1.1
Getting Started
Administration
Deployment
Troubleshooting
Project