I've recently been getting this error in Appwrite and I really don't quite understand why, the rate limits are different per endpoint but I think it's from account.get() in different places? How often are you guys calling this vs relying on state vars to update?
can you maybe share the network request logs that shows the error?
Let's verify if it is rate limiting account.get(), this endpoint shouldn't be rate limited, like other get endpoints in Appwrite.
This could be another endpoint being rate limited, or it could be a bug, let us know 😄
Yes 100% let me check, they’re on https://dailymatchup.com/login
Seems like
it could be from me getting their member account?
i don't see any rate limit error here 🧐
There's no error atm no, but it happens from that endpoint I believe, it happened yesterday trying to login lemme try that again
@Drake so when I log in there seems to be some fkery going on, for lack of a better word
{"message":"Server Error","code":500,"type":"general_unknown","version":"1.4.9"} from a query of queries[0]=equal("user_id"%2C+["64fce4ee7249c9e9eed1"])
and that happened with a few things
Check the server logs for the 500 error
which log
Docker logs
I'm aware, there's a lot of services
I checked database worker and nothing
If you get a 500 error from an API request, it's always the appwrite container
Recommended threads
- Project Inactivity Clarification
I'm on appwrite free plan with my account (om.thakkar@ivcventure.com). Even though throughout the week we use the project atleast once to upload dynamic content...
- [ENHANCEMENT] Use the custom Next.js dep...
Deployment adapters on Next.js are now stable! This means that we don't have to stick to the limitations of sniffing out build outputs and manually moving or mo...
- NextJS builds sudden runtime_timeout
My builds suddenly stopped working. Activating old prebuilt snapshots work, but redeploying that same code produces builds that throw runtime_timeout FRA region