It’s been over 24 hours and I still can’t get this custom domain name to connect. Usually it takes just a few minutes. I did notice there are 4 records to connect now instead of the 2 we historically needed. Am I doing something stupidly wrong?
Johnny, I always appreciate your help in the forum. Thank you for this!
So, I like that you tried to test my url using Google’s Dig console. I did this too, but I think you entered a different url from the looks of that screenshot. This is what I get back with the correct URL:
So, the suggestion of setting only the CNAME records in Namecheap (in lieu of Bubble’s recommended A records) did not work It’s also been over 48 hours since I tried the recommended A record approach and I still can’t connect this domain
Okay, so I’ve figured out the issue. It appears that in my frustration with this custom domain name integration taking longer than usual, I most likely pressed the Confirm My Settings button too many times. Apparently Cloudlfare places temporary restrictions on domains that have tried to be added to their service too many times within a short period. I imagine this sort of gotcha didn’t exist before Bubble integrated cloudflare by default… but it certainly does now
So moral of the story, have patience and don’t mash the Confirm My Settings button like I did. Honestly, there may have been another issue in place here… but if this issue befalls anyone in the future, please send a polite email to the Bubble team and they’ll fix you up right away. Thanks again @jess for all your help