Skip to content
Back

restore backup on another server with another domain self-hosted

  • 0
  • 1
  • Self Hosted
Gildas Quiniou
15 Jan, 2026, 11:06

I managed to restore DB+Volumes from a server to another one with another domain but when I try to click my project on the console, I get error "404 - Project with the requested ID could not be found. Please check the value of the X-Appwrite-Project header to ensure the correct project ID is being used.". Should I change something in .env or some records in DB ? Thx.

TL;DR
User encountered a 404 error after restoring a backup to another server with a different domain. The issue might be due to the project's internal Console/permissions metadata being out of sync. Manually editing the database is not recommended. The best solution is to DM the helper for private debugging or a safe workaround.
Gildas Quiniou
15 Jan, 2026, 11:06

restore backup on another server with another domain self-hosted

Flashtum
15 Jan, 2026, 11:45

I can help 👍 This usually happens because the project ID stored in the client / console config doesn’t match the project ID in the restored database. After moving to a new server/domain, the Appwrite Console may still be sending an old X-Appwrite-Project value. You typically need to update the project ID in your .env (and any client configs) to match the restored project, not manually edit DB records. Quick check: Does the project exist when you list projects via the Appwrite CLI or API on the new server? What Appwrite version are you running, and did you restore the projects collection as well?

15 Jan, 2026, 12:01

Thanks for helping. It happens in the Web console. I can see my Project but when I click on it I get this 404 error. I did a backup (full DB + functions and uploads volumes which are both empty anyway) then I did the restore following https://appwrite.io/blog/post/how-to-back-up-your-appwrite-data doc. Btw, I'm able to create a new "test" project and I can click on it from the Web console so my AW seems healthy. I tested in incognito mode in Chrome to prevent having cached values. I checked the X-Appwrite header values both on my first server (running fine) and my second backup server and it shown the same values. Thx.

15 Jan, 2026, 17:29

This usually happens after a restore when the project exists but its internal Console/permissions metadata is out of sync, which is why it shows in the list but 404s when opened. It’s not an .env issue, and manually editing the DB isn’t recommended. This is easier to debug privately feel free to DM me and I can help you sort it out or apply a safe workaround.

Reply

Reply to this thread by joining our Discord

Reply on Discord

Need support?

Join our Discord

Get community support by joining our Discord server.

Join Discord

Get premium support

Join Appwrite Pro and get email support from our team.

Learn more