This happens when Webfaze's data folder was inside a folder that the redeploy replaced. The data folder holds your uploads, your licence and your encryption keys, so it must live somewhere a redeploy doesn't touch.

Hostinger

Hostinger replaces the app's folder on every deploy. Since Webfaze 1.0, the data folder is kept next to the app, in domains/<your site>/webfaze-data, where a redeploy can't delete it. If your site ran an older version, update to the latest from Account → Downloads. Don't set WEBFAZE_DATA_DIR unless you want the folder somewhere else.

Railway, Render, Coolify, Fly and other container platforms

Containers start empty. Attach a persistent volume at /data and set WEBFAZE_DATA_DIR=/data.

Docker

Keep the ./data volume from the included docker-compose.yml.

Getting your site back

  • Content: with MySQL, your pages and posts are still in the database. With SQLite, the database was in the data folder: restore your latest backup in Tools → Backups.
  • Uploads: copy your saved uploads folder back into the data folder. A backup file lists uploads but doesn't contain them.
  • If config/secrets.env was lost too: passwords can no longer be checked and saved credentials (email password, payment and API keys) can't be read. Use Forgot your password? to set a new password (the link appears in the app's log if email isn't working), then re-enter those credentials in Settings and in each extension's settings.
  • Licence: enter your key again under Settings → Advanced → Licence. If it says it's in use, remove the old entry in webfaze.com Account → Licences first.

From now on, keep a copy of the data folder's uploads and config/secrets.env with your backups.