Supabase Auth hitting rate limit 429 too often in development

I have a small NextJS app. It's my understanding we should be calling the helper

createServerClient

createServerClient

in server components to authenticate requests (to do some db stuff). I am doing so in a few pages and server actions, but I often find myself hitting 429. Is this really how it's supposed to work? How will my app survive in production if a few clicks here and there causes this? Let me know, in general terms, what I should look out for. I'm pretty experienced with NextJS and web dev as a whole, but perhaps am missing something specifically about Supabase Auth. Thanks in advance.

Supabase•3y ago•

25 replies

bnugggets

Supabase Auth hitting rate limit 429 too often in development

I have a small NextJS app. It's my understanding we should be calling the helper

createServerClient

createServerClient

Supabase Auth hitting rate limit 429 too often in development

Similar Threads

Supabase Auth hitting rate limit 429 too often in development

Similar Threads

Similar Threads

Similar Threads