I just received an email from Bubble saying “Action required: Enable Cloudflare for custom hostnames by August 29”—otherwise my custom domain will stop working.
The issue is that when I go to the email/settings page, I don’t see the option they mention. I’m not sure if this is a bug or if I’m missing something on my end.
Another concern is that the email was sent on August 26, which feels like very short notice for something this critical.
Has anyone else run into this? And does anyone know why I don’t see the checkbox for “Accelerate this domain using Cloudflare”?
Here is a screenshot of the email. It’s bizarre:
a) sending this with only 3 days’ notice or the app breaks, and
b) when trying to do it, the option isn’t even visible because of a bug.
I’ve reached out to support but still haven’t received a clear answer on whether this email was sent by mistake or what is actually going on.
I also have a custom domain, but I haven’t received this email. Have you tried clicking on the instructions? Did you paste this into the bubble bot to understand what happens in the meantime? I’m sure support will intervene soon to clarify the situation..
Since I’m off work today, and doing 100 other things to put off what I should be doing…
I may need a business coach
Anyway, I noticed this line from the email that I quoted above.
I do know from reading a million past forum posts that in 2019, Bubble switched to managed cloudflare integration for their custom domain names.
They’re saying you need to change your DNS records to reflect this because the older accounts were pointing to Bubble’s IP address. You probably have an old account.
Yours may be ok? But, since you can’t click on what you’re supposed to click on, it seems only bubble support can help you.
I hope you get it worked out.
Enjoy the rest of your day.
Added: There’s also a forum post from 2019 that talks about this…but I didn’t look it up again to get the link
I got the same email.. And when I logged into my app, I saw that “Accelerate this domain using CloudFlare” WAS already enabled for the app Bubble told me it wasn’t checked for.
I then unchecked the box… Which caused everything my app to go down… Then I refreshed the page, re-checked the box, and it gave me new A records. I ran over to my DNS, placed the new A Records, and 20 minutes later, my app is back up.
I think the email was a tad confusing from Bubble – I believe it was triggered from apps that may have an older CNAME implementation (like I did..).
Now, it’s all A Records, no CNAME’s.
@fede.bubble Would keep my eye on this just in case others get that email like I did and were confused by the box already being checked for CloudFlare.
Yes, that’s my suspicion too since the app was started in 2019. Still waiting on Bubble to give a clear answer, and the deadline tomorrow has me stressed out (the email doesn’t even say if it means end of day tomorrow or just sometime tomorrow).
Thanks for the insight. So that means the email is real, and for some reason that feature hasn’t been enabled on my app. I’m still perplexed that Bubble would deprecate something without doing their due diligence to ensure customers can actually transition.
Just be careful… In my case, once I unchecked that “Accelerate this domain using CloudFlare’“, there was no warning.. It went straight to town and took my app down. When I re-checked it, I had brand new A records I had to go run immediately over to my DNS for.
Bit of a harrowing 20 minutes.. but glad it’s over with now. App is back up and running just fine.
Looking forward to more info, as the email was received for an app of mine that is already using that cloudflare feature, but not for a separate app which is not using it
Hi everyone. I followed up with the team today and wanted to share an update.
We’ve identified the error in how we pulled the email recipient list, which led us to accidentally send the email to some users who should not have received it, and miss sending it to some users who should have received it.
My sincerest apologies for this error and the confusion it caused. We will be putting extra checks in place to keep this from happening again. As a next step, we will revise the original email to make the instructions clearer and then re-send it to the correct list of people.
In the meantime, we won’t be making any changes to the Cloudflare setup, so you can disregard the August 29 deadline. We’ll let you know when we have a new date for this work.
Thanks for your patience here and for surfacing this issue.
TJ
