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
- Realtime for files() works almost well, ...
I have been trying to make use of realtime, today (14.03.26) I have pulled all the latest versions of docker images, and sdk available. Whats working: - Conn...
- Local appwrite run functions --user-id n...
Hi, I'm running into an issue when testing Appwrite functions locally with user impersonation. I'm using a self-hosted Appwrite instance and running functions ...
- Selfhosted Github App installation
I've followed this guide: https://appwrite.io/docs/advanced/self-hosting/configuration/version-control to connect GitHub to my self-hosted Appwrite instance (1....