Replies: 4 comments
-
It's a real issue. I have been having the same issue and opened up a support ticket. After two days still no definitive response. This is an issue coming back from a Lets Encrypt DNS validation for the cert to be issued. |
Beta Was this translation helpful? Give feedback.
-
Same issue here |
Beta Was this translation helpful? Give feedback.
-
I had this same issue ongoing (using AWS R53 DNS) The only thing that worked was dropping the TTL from the default 300 to 60 for the TXT _acme_challenge record. |
Beta Was this translation helpful? Give feedback.
-
Anyone have a straight solution for this? Running into verification issue. as well. Given that they charge extra $10 a month for this, it's not great that setting it up is such a PITA. |
Beta Was this translation helpful? Give feedback.
-
I'm having an issue setting up the second of the two TXT validation records to implement a custom domain for my Supabase project.
I'm following the instructions here: https://supabase.com/docs/guides/platform/custom-domains (replacing the project ref id & example.com values w/ my own)
As the documentation says, two TXT records get returned:
After adding the above records (again, replacing example.com with my specific domain), the first TXT record (_cf-custom-homename) is validated, but the second continues to be outstanding:
If I check on https://mxtoolbox.com/SuperTool.aspx I see the DNS record and confirmed it resolves to the string value provided by Supabase
Has anyone run into this before? Any tips on how to resolve?
Beta Was this translation helpful? Give feedback.
All reactions