inviteUserByEmail failing on certain instances on the Supabase platform about auth HOT 4 OPEN

Thanks for this, I will transfer this to the Auth repo for easier tracking.

The error message you are seeing is typically due to issues of duplicate calls. Are you able to see if the same call is being made twice or potentially the first one is failing during execution?

from auth.

Hi Auth,

So I have tracked down the issue to using port 25 for our custom SMTP server. The ones that were working were using port 587.

Very recently this message started appearing in the SMTP setup panel:

This would have been in the last week or so. Changing the port to 2525 (CRAM-MD5) fixed the issue. As port 25 (TLS) was working before, I have to assume that this is a recent change.

If port 25 is actually no longer supported by the custom SMTP service, the note seems a little soft. I am pretty sure that our SMTP provider is not blocking port 25. If Supabase's infrastructure blocks outgoing port 25 requests, it would probably be better to have a more dire message here.

I will not close the ticket in order to give my feedback about the documentation but the issue is resolved on our end.

lwjameson

from auth.

Facing exact issue here, it worked after I disabled smtp on supabase.

I am using spacemail for smtp and their mails has to sent through https but I was expecting it to work through localhost which is http. So it didn’t work.

When I pushed my changes to prod with smtp, it worked fine

from auth.

@saka01

Thanks for circling back. It makes sense that it works after disabling SMTP as it should default to the Supabase

Quick check - does port 465 work for you? one of the underlying libraries we use only enforces ssl on port 465 so if there is a hard requirement you may have to use port 465

from auth.