Custom domain verification repeatedly failing for 2 days now
Need suggestions. Followed the custom domain instructions repeatedly for 2 days now, and it continues to exhibit the same symptoms: despite the _acme-challenge.. DNS entry being set correctly and verified its propogation every way I could think of, if I either click verify on the dashboard or running 'supabase domain reverify' refuses to work. it just conitnues to say the recommended TXT entry needs to be set. Eventually after multiple attempts and waiting various lenghts of times, inevitably the challenge key value string will suddenly change when i try to verify it, forcing me to change the DNS TXT entry again and attempt to get it to verify again in futility
I resorted to creatign an entirely new empty supabase project to attempt to see if it was due to the specific project, but it exhibits the exact same symptoms
I'm at end of my rope, this should be the simplest thing but is eating up disproportionate time.
Has anybody found an undocumented issue or workaround for this?
Has anybody found an undocumented issue or workaround for this?
2 Replies
well. this magically resolved itself today and started just working fine. i didn't really get any help from anybody unfortunately including support other than pointing me back to the docs I already read multiple times, netting into multiple days of wasted time and nothing learned.
I would advocate that somebody on the ops team take a look at what happened there and what resolved it in the end because it really was a bad experience.
I would advocate that somebody on the ops team take a look at what happened there and what resolved it in the end because it really was a bad experience.
This site is not monitored by Supabase staff normally and is user helping user. Github issues or support is best bet for feedback.