Back
Rate limit
Facing rate limit in self hosted instance while testing login.
TL;DR
Developers are experiencing rate limiting while testing login in a self-hosted instance. To avoid this during development, toggle `_APP_OPTIONS_ABUSE` in the `.env` file and restart the appwrite docker stack. Remember to re-enable it when moving to production.
as said in the other channel,
toggle _APP_OPTIONS_ABUSE while in development in your .env file and restart the appwrite docker stack.
If you make many tries, you get blocked to prevent abuse. As Darshan mentioned, you can disable it during development, but make sure to re-enable it when entering in production
I just created a session 2-3 times back to back
