Unclaimed tool
Appwrite
appwrite.io
Open source backend platform for web, mobile, and server applications.
Tools
From public taxonomy evidence
Related skills
- 🐛 Bug Report: Multiple internal curl errors has occurred within the executor! Error Number: 111.
Appwrite functions failing with 'Multiple internal curl errors... Error Number: 111' (connection refused) on the first run after deploy or restart is a resource problem: the executor containers are not fully up when the first call lands.
supporting match - Appwrite manual installation throwing "Failed to connect to database" error
If a self-hosted Appwrite install fails with database or redis connection errors (Failed to create connection, AUTH password errors, or the appwrite-schedule, appwrite-maintenance and appwrite-usage containers restarting), check your .env for _APP_REDIS_USER and _APP_REDIS_PASS. The redis library in use didn't support
supporting match - 🐛 Bug Report: JWT still valid after Session Timeout
A practical guide for Appwrite. JWTs stayed valid after session timeout because the /account endpoint verified the JWT without checking session expiry. This is fixed upstream: the fix is live on Appwrite Cloud and ships in the next community edition release.
supporting match - 🐛 Bug Report: All Users.CreateUser... endpoints return a vague server error is null name is provided
[ChiragAgg5k (maintainer)]: This was a server bug, fixed in Appwrite 1.9.0 (PR #11413): create-user endpoints typed name as non-nullable string, so passing name: null threw a vague server error. Handlers now accept ?string $name and treat null as empty string.
supporting match - Astro SSR: cross-site POST fails checkOrigin when served through Appwrite custom domain
How to fix: Astro SSR: cross-site POST fails checkOrigin when served through Appwrite custom domain. Astro's checkOrigin blocks POSTs when the served hostname isnt in its allowlist, which is exactly what happens behind an Appwrite custom domain. The fix: put the exact HTTPS hostname into Astro's security.allowedDomains
supporting match - Astro SSR: cross-site POST fails checkOrigin when served through Appwrite custom domain
How to fix: Astro SSR: cross-site POST fails checkOrigin when served through Appwrite custom domain. Astro's checkOrigin blocks POSTs when the served hostname isnt in its allowlist, which is exactly what happens behind an Appwrite custom domain. The fix: put the exact HTTPS hostname into Astro's security.allowedDomains
supporting match - Astro SSR: cross-site POST fails checkOrigin when served through Appwrite custom domain
How to fix: Astro SSR: cross-site POST fails checkOrigin when served through Appwrite custom domain. Astro's checkOrigin blocks POSTs when the served hostname isnt in its allowlist, which is exactly what happens behind an Appwrite custom domain. The fix: put the exact HTTPS hostname into Astro's security.allowedDomains
supporting match
Public conversations
Recent discussions
- Astro SSR: cross-site POST fails checkOrigin when served through Appwrite custom domain
My Astro SSR site hosted through an Appwrite custom domain worked fine on the local machine, but Astro's CSRF and origin validation rejected every POST form submission once served through the custom domain. The browser showed Cross-site POST form submissions are forbidden. The thread is from September 2026 and a mainta
- TypeError: e._formData.get is not a function when calling a Server Action in Next.js
The culprit is the isomorphic-form-data package, pulled in by older Appwrite and Twilio SDKs: it overwrites Node's native global.FormData with the form-data package, which does not implement the Web FormData#get() API that React Server Actions require. A maintainer reproduced the exact error only when that package was