URGENT: Critical Outbound SMTP Block & Egress Failure — Project efknuwnomcbywluznhnp
Hello Supabase Team,
My project (Project ID: efknuwnomcbywluznhnp) is experiencing a critical outage: all outbound SMTP connections are failing, preventing authentication emails (signups, password resets) from being delivered. This is a total outage of critical functionality.
Diagnosis: The issue is a critical network connection failure on the Supabase platform side (Egress Block), not a configuration error.
7 Replies
This is a user helping user platform and not regularly monitored by the Supabase staff.
What is a Egress Block? have you tried your SMTP settings elsewhere to be sure it's working?
What email provider are you using?
What is the error message in the Auth log?
Hello, thanks for the help! I have already run a full diagnosis:
1. Egress Block: An Egress Block is a firewall rule preventing outbound connections from my Supabase project to the external SMTP server (Resend, on port 587). This is highly likely because:
2. SMTP Settings Tested: YES, I tested my Resend connection externally with
openssl and it works perfectly. This proves the SMTP server is reachable and my credentials are correct.
3. Provider and Logs: I am using Resend. My Resend dashboard shows ZERO connection attempts from the Supabase project. The connection is failing before it reaches the provider.
4. Auth Log Error: The Auth logs show 200 OK on the signup request, but then show NO ERROR related to the SMTP connection attempt. This silence is typical when a connection is blocked by a network firewall.
Action: I suspect a Supabase-side Egress Block on my project ID: efknuwnomcbywluznhnp. I have also opened a support ticket (SU-287211). Could someone with platform access please check the firewall or connection logs for this project?Maybe support can help, but I've never heard of an Egress Block for SMTP.
If you are getting no error and a 200 then Supabase thinks it has connected to an SMTP and sent the data successfully. If that failed there would be an error.
OR you have confirm email off for signup.
Thank you again for the suggestion about the 'Confirm email' setting!
I have just confirmed my settings: 'Confirm email' is currently ON in my dashboard.
This officially eliminates the last possibility of a configuration error.
Since the setting is ON, Supabase is required to send the email, but the connection is failing silently due to the Outbound Egress Block.
To summarize the final evidence for the official Supabase staff:
1. Configuration is correct: Custom SMTP (Resend) is set up, and Email Confirmation is ON.
2. External Test Works:
openssl proves the SMTP server is reachable from outside the platform.
3. Failure Point is Egress: The Resend dashboard is completely EMPTY, meaning the connection is blocked before it leaves the Supabase network.
Action Required: Please, an official staff member needs to check the Platform Egress Firewall Logs (Port 587) for project ID: efknuwnomcbywluznhnp. This is a platform-level network outage.
Thank you for escalating this to the correct team.We don't escalate individual issues here. Your support request gets handled based on Pro/Free status and when support gets to it.
Also you are the only person reporting this.
How are you doing your signup in your app? auth.signUp()?
Also where are you getting the phrase Outbound Egress Block from?
If the SMTP call from Supabase does not get back a success response then it will timeout and error or reflect the error it gets back in the auth log.
Is the user getting added to the authentication section of the dashboard?
Thank you very much for your time and all the help, especially with checking the "Confirm email" setting and confirming the user status flow!
Your input has been crucial in eliminating all configuration errors. I now have all the definitive evidence needed to properly escalate this network outage through the official support channel.
I will be closing this thread and focusing exclusively on my support ticket (SU-287211).
Thanks again!
@garyaustin and @silentworks
Subject: RESOLUTION: Issue SU-287211 Resolved
The issue has been resolved.
Root Cause Identified
The primary failure was caused by a newly introduced Auth Hook that was improperly configured (returning the error "Hook requires authorization token").
After removing the faulty Auth Hook, the authentication process is now completing successfully, and the confirmation emails are being sent via the custom SMTP (Resend).
Network Status
This confirms that:
1. The Outbound Egress Block (the original suspected issue) is either resolved or was not the root cause.
2. The Custom SMTP configuration is functional.
Please close this ticket as the issue is resolved on my side. Thank you for your assistance.