[SOLVED]How to increase rate limit for JWT End Point?

I have met the rate limit and I am unable to perform any operation 😦

TL;DR

The user was initially confused about how to increase the rate limit for a JWT endpoint. They found the documentation helpful but had questions about permissions and roles. They realized that using the `account.get()` method for every page render was causing the rate limit to be reached. They considered using `localStorage` as an alternative solution. Another user suggested caching the response or waiting for 60 minutes before retrying. The user acknowledged the rate limit abuse and expressed their frustration at being unable to perform any operation due to reaching the rate limit. The thread does not provide a clear solution to increase the rate limit.

You need to wait 60 minutes so

Why you call it more than 100 times in 60 minutes ?

If you need to test while dev, just cache response

100 times in 60 mins wow! please check this once https://appwrite.io/docs/rate-limits#abuse

I would urge to wait a bit then retry?

also seen this once https://github.com/appwrite/appwrite/issues/2953#issuecomment-1542867932

May be this is the reason

I want to check whether user exists or not. and I want to protect routes.. Could anyone suggest me any other best solution?

localStorage is the best alternative this right ?

Ma'am!

I think , I have solved this issue...

🙂

The way we typically check if a user is authenticated is to call account.get(). If that is successful, the user is logged in.

Yeah, I mean, If I use the above method or any other method, for every page render, that method will be called. Because I am wrapping every page with AuthProtectedRoute Page. that's how my limit is getting over. So I am checking it for one time until the user delete the session and updating the UI through localStorage. sir.