-
-
Notifications
You must be signed in to change notification settings - Fork 42
Backup and Restore
Ryan edited this page Jan 16, 2026
·
1 revision
FileRise stores all persistent data on disk. Back up these paths:
-
/var/www/uploads(file data) -
/var/www/users(users, ACLs, admin config, Pro license) -
/var/www/metadata(indexes, tags, logs)
Notes:
- Logs live in
/var/www/metadata/logand can be rotated/pruned. - Sessions are ephemeral and do not need backups.
- Stop the container or web server (best for consistency).
- Back up the three directories above.
- Store your
PERSISTENT_TOKENS_KEYsecurely (needed to decrypt admin config and tokens).
- Restore the three directories to the same paths.
- Ensure ownership/permissions are correct:
sudo chown -R www-data:www-data /var/www/uploads /var/www/users /var/www/metadata
sudo chmod -R 775 /var/www/uploads /var/www/users /var/www/metadata- Use the same
PERSISTENT_TOKENS_KEYas the original instance. - Start FileRise.
If encryption at rest is enabled:
-
/var/www/uploadsand/var/www/metadatamust be backed up together. - Keep your master key (
FR_ENCRYPTION_MASTER_KEYormetadata/encryption_master.key). - Losing the key makes encrypted data unrecoverable.
Pro bundle and license files live under /var/www/users by default. Restoring that directory restores Pro settings as well.
Docs · Support · FileRise.net · Changelog
- Admin panel
- Admin gotchas
- Common env vars
- Environment variables full reference
- ACL and permissions
- ACL recipes
- Nginx setup
- Reverse proxy and subpath
- WebDAV
- WebDAV via curl
- WebDAV security and clients
- ONLYOFFICE
- Encryption at rest
- OIDC and SSO
- CIFS share auto metadata
- Sharing and public links
- Upload limits and PHP tuning
- Logs and diagnostics
- Backup and restore
- Upgrade and migration
- Migration checklist
- Maintenance scripts
- Performance quickstart
- Performance tuning
- Security hardening