
Hi team,
I’m currently self-hosting Appwrite v1.7.4 using Dokploy (Compose Type: docker-compose) and everything in the deployment appears to be functioning — Console, workers, database, Redis, etc.
However, when I try to use the new Sites feature from the Console, I see this message:
Appwrite Sites is in high demand To ensure a smooth experience for everyone, we’re rolling out access gradually. Join the waitlist and be one of the first to deploy with Sites. [Join waitlist]
This seems to indicate that Appwrite Sites is not yet available, even though I’m hosting Appwrite on my own infrastructure.
Deployment Info: Appwrite version: appwrite/appwrite:1.7.4 Console version: appwrite/console:6.1.12 Platform: Dokploy (self-hosted via Docker Compose) Compose Type: docker-compose (not Swarm) Sites domain env set: _APP_DOMAIN_SITES=*.mydomain.tld Traefik reverse proxy: properly configured Volumes mounted: includes appwrite-sites
My Question: How can I enable or unlock Appwrite Sites for use on a self-hosted environment? Is the Sites waitlist enforced for all environments, including self-hosted? Is there a specific env var, volume, or console config I need to adjust? Is the gating purely frontend via console:6.1.12, or handled by Appwrite core/backend? Would love any help from the Appwrite team or community on this.
Thanks! 🙏
Recommended threads
- Cannot create function from CLI with KEY
I tried to setup a gitlab CI that push functions from an appwrite.json, tho when doing a first push it fails saying it needs a session. Tho it does create the f...
- appwrite/appwrite:1.7.4 image missing En...
Hi Team, I'm experiencing a critical issue when deploying the official appwrite/appwrite:1.7.4 Docker image. After pulling the image (both by tag and by digest...
- cannot update env _APP_SYSTEM_SECURITY_E...
I tried updating .env file using vim and change the env _APP_SYSTEM_SECURITY_EMAIL_ADDRESS=arcivalpalma07@gmail.com and save. docker compose up -d docker com...
