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
- Impossible to create project via CLI?
Is it possible to create a new project via the appwrite CLI ? I need to create a few projects for something I'm working on and because i don't want to do it man...
- Understanding S3 setup with appwrite
Hey, i'm planning to change the storage from local to S3, tho i have some questions to see before starting the migration. 1. Does all the `/storage/<storage_ty...
- S3 files like health6a079a79afaa25.44072...
I migrated to another external S3 host for my appwrite and in many (but not all) folders a file (something like health6a079a79afaa25.44072323 - file itself is e...