Ok, @eve helped me out yesterday and suggested option 2 which is what I’ve started to do… about 30% done now… I switched from godaddy to Google domains last week because I read that godaddy was a nogo… come to find out Google domains doesn’t support Anames but does support synthetic records… is this a viable option??? I also want to thank you and @eve for helping out so far
@peterjso for my legacy app will it be better long term to switch back to my bare domain now OR go ahead and keep the www.?
I have it on google domains as well.
I’ve been back and forth with @eli and he reports that google’s synthetic records are probably the best option. Keep doing what you’re doing and switching your API calls; as long as your synthetic records are configured correctly you won’t have to do this again. Even if you switch registrars down the road, you’ll be able to use their version of synthetic records.
1 Like
Hi, It is a huge performance increase, and (thank you all at bubble!) a great new feature.
I am sure my app is very data intense for a commerce app, and the Lighthouse test is now without additional cachings (PWA) about 75% for mobile and desktop. I did then some weeks ago leverage the whole cloudflare thing with more caching through PWA service worker. Google Lighthouse propelled a nearly 100%. So its great progress with cloudflare, do not worry. I also added some extra service from cloudflare, for mobile.
2 Likes
Just got it working with Google domains using @eli’s method with the synthetic record forwarding the bare domain to www. Thanks!
I ran into a couple of common issues, first the “Site not secure” issue, and then the Failed handshake error 525 or whatever. The thing that fixed these errors for me was to delete the domain in my Bubble settings and type it in again. So if you’re stuck, that might fix something.
1 Like
I have tried the name cheap approach from @peterj video but I still get a cloudflare 404 after the browser moans about this site is not secure.
I can see the CNAME is pointing to app.bubble.io so all looks correct. When I use mxtoolbox to do a DNS check it reports the following?
Parent server gave glue for www.mydomain.co.uk to be app.bubble.io but we resolve that hostname to 104.19.240.93 104.19.240.93
Those IP addresses are what app.bubble.io resolves to which I guess is a Cloudflare IP, so on the surface that all looks correct but funny that DNS check thinks that is an issue and Cloudflare also appears to not know about the domain. It all looks good in Bubble and I have tried the domain in Bubble with and without www.
Site has been down for 2 days now so this is a bit frustrating. I also can’t roll back as Bubble will not allow me to remove the custom domain!
Anyone got any ideas as I would love to fix this 
Hi @peterj,
I have about 4 /5 sites now up and running on cloudflare and noticing a significant speed boost! Most my of sites were on legacy sub-domains, so it was very easy to setup cloudflare. All I had to do was create a CNAME record in Digital Ocean (replacing the legacy A record) pointing to app.bubble.io. It took about an hour for the cloudflare certificate to validate (I was receiving the warning that the certificate wasn’t valid, but could access the site). Note - one trick with Digital Ocean, you can change the TTLS to 3600 (for CNAME) instead of leaving it as the default 43XXX.
I had one site using google domains. From your documentation, I opted for the 301 permanent re-direct so that my bare site www.coolstuff.com was always redirecting to app.coolstuff.com, then part two was to create a CNAME record (in google domains) to point app.coostuff.com to app.bubble.io. Google took hours to process this change, and the site was down (digital ocean, the site was still accessible). You just have to be patient and expect your site might be down for a few hours or even a day.
Overall, this is awesome! All my apps are faster, most noticeable, my mobile apps. @peterj , thanks for setting up cloudflare, the videos, and documentation. I watched all the videos and wen through the documentation, which helped make this process an easy transfer.
G
2 Likes
@3brotherssupply and @eli
I got time to investigate this one today, and the solution is now in the manual.
1014 errors are caused by trying to Proxy traffic through your own Cloudflare account (“orange cloud”). For now, to avoid 1014 errors, you need to change any CNAMES to DNS only (“grey cloud”) and then clear your DNS cache, which is usually different than your browser cache.
I tried to CNAME another domain account for the sake of White label (SAAS), I was getting this error 1014, after changing the cloud to DNS only (grey cloud) I started getting “You’ve pointed xxx.com to Bubble, but we don’t have an application…etc”
we are in need for this, there is a service called https://www.clearalias.com I tried it before bubble do the switch to cloudflare but bubble blocks it on their side. Now I’m give it another try after the switch and I’m getting “403 Forbidden” I think from bubble setup on cloudflare.
if we cannot CNAME another domain on cloudflare nor use a service like clearalias, I think bubble need to help us here.
Has anyone done this with one.com?
I really can’t get this to work. I’m desperately asking for help.
Your domain records are configured properly. Cloudflare is doing something unexpected.
Please try deleting your app’s domain name on Bubble and then re-creating it.
You’re promoting an adult link 
2 Likes
Hopefully I am making a simple mistake, but I cannot get my site to use SSL/HTTPS, so cloudflare doesn’t work properly.
Concerns:
- No SSL checkbox option (now and during setup)
- No cloudflare checkbox option (now and during setup)
- www.mysite**.app** domain name
Any help would be greatly appreciated!
Okay thanks. “www.rempah.se” works now but I can’t get the page loaded with the bare domain.
EDIT: Weird is, that safari loads the page without “www” but Chrome doesn’t. I’ve cleared the cache.
EDIT2: Solved. Added a simple forwarder from my bare domain to the domain with “www” included.
1 Like
Thanks @meinharttv, I have followed all of your steps for my Google Domain. I get this message in Cloudflare DNS Management. Do I need to do anything with the A or AAAA?
Hey all,
since enabling this option on zeroqode.com we started registering much less traffic on Google Analytics. Traffic from all sources become less, although we know that the traffic is the same.
Did anyone experience something similar?
As Cloudflare is essentially a shared service, there are reports of odd happenings although they are extremely rare. eg:
1 Like
I have my domain registered with Namecheap and already had my domain managed by Cloudflare. My app exists on a subdomain and I previously received instruction on how to enable the Cloudflare for my Bubble app through my existing Cloudflare account. However today-- with no settings being changed on my end, I’ve receiving notifications that my domain isn’t pointing to the appropriate A records. Can someone please advise?
Hi @peterj ,
last week I switched to cloudfare setting adding a CNAME on my provider www.register.it and everything looked fine. This morning, opening the bubble editor, I got this error message.
I know nothing about the A record 104.19.241.93 (as I said I have just added the CNAME app.bubble.io to the subdomain app.studiosemplice.com) but going to this URL this is what I see
My app is live with a pre-launch page but the public domain can be reached with apparently no problem
What should I do ? Can you help me ? Thanks
Same here. Switched it over a few days ago. All working fine. Today, I hit the “Preview” and get an Issues with Domain Popup. Also have the same message with same IP in admin so you are not alone. Most likely a CloudFlare issue of some sort.
1 Like