Having e-mail auth provider enabled rate limiting other auth providers usage
Problem
Bug report Having e-mail auth provider enabled gives a 429 rate limit exceeded, despite using only Phone auth provider. Describe the bug We had e-mail auth provider and phone auth provider enabled. (With e-mail auth not being used.) Once we started getting a spike in traffic for our SMS OTPs, we started getting a 429 rate limit exceeded, despite Twilio looking fine on our end. Once we disabled e-mail auth as a provider, everything was working normally again. To Reproduce 1. Enable e-mail and phone auth providers, 2. Try hitting rate limits that you would normally hit, but with phone SMSs, 3. Get a 429 - Rate Limit Exceeded. 4. Disable E-mail auth, and check that everything is working again. Expected behavior Did not expect any rate limit issues. System information - Browser: Chrome, - Version of "@supabase/supabase-js": "^2.1.1", - Version of Node.js: [e.g. 16.13.1]
Unverified for your environment
Select your OS to check compatibility.
1 Fix
Solution: Having e-mail auth provider enabled rate limiting other auth providers usage
Same here while trying to add new user. It was working fine, but suddenly started giving 'Email rate limit exceeded' errors. ReactJS
Trust Score
5 verifications
- 1
Same here while trying to add new user. It was working fine, but suddenly starte
Same here while trying to add new user. It was working fine, but suddenly started giving 'Email rate limit exceeded' errors. ReactJS
Validation
Resolved in supabase/supabase GitHub issue #10850. Community reactions: 10 upvotes.
Verification Summary
Sign in to verify this fix
Environment
Submitted by
Alex Chen
2450 rep