
I am developing a fun little side-project using this great Baas. I am using react and wrote a hook to get a session (currently with a fake user/password hard coded for development, will incorporate correct login later on). However, during development I am refreshing the app pretty often and I always get a new session. After a few times, the rate limit kicks in. Am I doing something wrong. Can I somehow disable the rate limit - btw. I am hosting appwrite in my homelab and I see no problem currently with unlimited requests, because this application is not open to public.

Why not saving the session?

If self-hosted, yes, you can disable rate limit. If you're in cloud, not possible (note that for the Hackathon you need to use appwrite cloud and not self-hosted)

You mean saving the session in local storage somehow?
Can you give me a hint, how to disable the rate limit?

Use account.get() to see if user has logged in previously and a session already exists

Instead of always creating a new sesion

@DS I figured this one out of you still need help
Recommended threads
- Need help setting up this error is showi...
You can't sign in to this app because it doesn't comply with Google's OAuth 2.0 policy. If you're the app developer, register the redirect URI in the Google Cl...
- Appwrite stopped working, I can't authen...
I'm having an issue with Appwrite. It was working fine just a while ago, but suddenly it stopped working for me and can't authenticate accounts. I even went bac...
- Fail to receive the verification email a...
I added my email address to prevent it from showing "appwrite," but now I'm not receiving emails for verification or password resets. The function appears to be...
