Hello, I am a student engineer who built an internal website for my university club using AppWrite.
My club currently has around 500 members, and when I recently introduced the site and asked members to access it, I encountered rate limit errors.
My site is configured as follows:
- Authentication: Appwrite Auth + Google SSO
- Data management: Appwrite Database
- Site hosting: Vercel
- Most requests are sent directly to Appwrite via the client SDK. Initial setup and batch processing are handled through the Admin SDK on Vercel.
Here is what I would like to know:
- Are there specific criteria that trigger the rate limit? For example, is it applied per project, or per client IP address?
- Is there a way to relax or disable the rate limit? Given the nature of our club's usage, we expect peak traffic from approximately 1,000 devices (500 members, each with a PC and a smartphone).
TL;DR
Developers at the university club are encountering rate limit errors on their website using AppWrite. They're seeking information on criteria triggering rate limits and ways to relax or disable them due to expecting high traffic.
Solution:
AppWrite imposes rate limits on a per-project basis rather than per-client IP address. To potentially relax or disable the rate limit, developers can get in touch with the AppWrite team to discuss their specific requirements and usage patterns.Recommended threads
- [Self-hosted] Realtime crashes with "Mis...
- Error trying to deploy functions from CL...
✗ Error • on-auth-create (6a00b2ab000c9ce2949b) • Server Error ✗ Error: No functions were pushed. Prject ID: 69ffe0270033a4ac420a
- Intermittent Deploy and Execution Errors...
Project: project-fra-658e2f5f4ba30df91177 Function ID: 69bde006001c56757f49 **Several execution errors with:** Timed out waiting for runtime.\nError Code: 400...