Same problem here since 1h !!! Such catastrophic, and I didn’t made any chance during this time, so it’s a problem from Bubble… Come on, it is the launching day for me today, you can’t do that !
Thank you everyone for your patience… the fix is going up now.
We’re supporting a lot of different configurations, and I added checks around whether you’re using the correct cloudflare account. Basically,
if your domain is pointed to bubble
but your traffic should be over cloudflare but isn't
report that it's broken
but your traffic is coming over cloudflare and shouldn't be
report that it's broken
but your traffic is coming over cloudflare, but it's the wrong cloudflare account
report that it's broken
Getting this right in all cases turns out to be harder than my tests demonstrated. I’ve fixed the root cause and added logging around this case while I was peeking around in there, so as we add more supported configurations () we’ll be able to trace their root causes.
By the way, the breakage is probably going to overshadow a slight tweak, which is that we’ve added the ability to auto-verify your domain, which should eliminate a lot of the 403 and 525 errors users have had.
I don’t have a lot of time to prioritize this, but I’m considering your post a canary for other issues our users might encounter. If you could do me a favor, can you give me a timeline (to the week, or day) of when you moved zeroqode to Cloudflare, and any other related changes that might have happened around the same time?
I’ve been performing a lot of work on the exterior surface of bubble (that is, not just Cloudflare) and some of it has subtle effects elsewhere. So, for instance, if you moved to CF on Nov 18th but your SEO didn’t start taking a hit until the 20th, then that should help me figure out what we can improve on.
Hi @peterj
we moved zeroqode.com to Cloudflare on 14-th of November and immediately we saw drop in the traffic registered on Google Analaytics. I don’t think SEO was affected, it seems that there is something related to Google Analytics tracking.
By the way we moved all the zeroqode subdomains to CF before the main domain and none of them have similar issues with Google Analytics (these subdomains include dev.zeroqode.com, gallery.zeroqode.comapitools.zeroqode.com )
Hope this helps
Thanks!
The solution for now is to use cloudflare in DNS only mode (“grey cloud”). You’ll lose you abilities to set custom firewall rules etc. under your own account settings.
Cloudflare is currently developing a feature that they refer to as “orange to orange” for customers like you. Our account representative is going to let us know when that product enters beta; depending on the contract terms we may open it up to our own users in time.
Anyways… I set up Cloudflare and everything appears to be working fine. However I received this email from Bubble today:
Hello,
We have noticed that you have tried to set up the domain bohsa.co.uk for your app bohsa2, but the DNS records seem not to be right yet. This is something you should change with your domain name manager (i.e. GoDaddy, Dreamhost, etc.), outside of the Bubble Editor.
I genuinely have no clue what the problem is!
The app isn’t live yet, thankfully. I’m just making a few tweaks and syncing up the data but we are due to go live any day and I’m just concerned that on the surface everything looks fine but obviously something is wrong otherwise Bubble wouldn’t be sending me this email.
@peterj did you have any chance to look into it? We still getting twice less traffic on Google Analytics after migrating to Cloudflare. (Google adwords and Google Search Console don’t show any dip in traffic, so it’s just about data being transmitted to Google Analytics) .