[New feature] Cloudflare for all

Announcements New features
126

I’m not sure what to tell you. If I had to take a shot in the dark, you had zoomed in previously, and Chrome remembered the setting every time you loaded your page.

Meanwhile, when your DNS data changed, Chrome decided that your page was a new site and reset your zoom settings to 100%. …

Actually, this is a hypothesis I might be able to test for myself. Adding it to the list.

127

Thanks @peterj. I tested this on multiple computers. It affected all devices.

128

OK. I did that. Thank you! I am being prompted by Bubble with the following. Should I ignore the message because I cannot setup an A record using an IP if I already have the CNAME record to the root.

image
image983×147 5.18 KB

129

Opposite order - I have GoDaddy too.

  1. Tick the box to set up Cloudfare
  2. Remove A record
  3. Create with the CName that Bubble provides you.

It took a few minutes to propagate for me, then it was live with no issue. If you get any “There was an error” messages on GoDaddy, it is 99% because you have a conflicting record - In my case, I had a TXT record that had the same name.

130

Is it the same process for apps using sub domain and Cloudflare as a DNS? I have 3 apps using this set up. For some reason I’m seeing Accelerate checkboxes in double and quite not say if it’s actually working because of this.

Also it would be nice to see how does file load waterfall looks on https://tools.pingdom.com/ when Cloudflare is configured correctly.

31%20AM
31%20AM2012×276 26.4 KB

02%20AM
02%20AM2154×382 44.4 KB

131

Question to anyone that switched to a www. Are you receiving the “Your connection is not private” warning message when you click your link in Google results?

image
image1126×756 37.9 KB

133

Had the same message. Clear cookies for bubble and cache and log back in. Should resolve.

135

I can’t seem to get Cloudflare setup correctly with Google Domains for my bare domain. @peterj?

image
image2524×748 104 KB

136

Thank you

137

Hey @peterj Your Amazing! ( Man Hug! )

Speed is super fast already getting comments from users and puts apps like mines up there with the big names across the globe in regards to speed and reliability.

Speechless!

Bubble is not in a bubble this platform is going to be on the world stage!

#Gobubble!

138

Hey, I’ve never seen this before but after creating those 2 CNAME records, I now get this…
Edited: FIXED by clearing cache/history in Chrome :slight_smile:

image
image1231×912 42.2 KB

139

Problem solved with the creation of a free DNS provider at NAMECHEAP.

Just had to setup the DNS of Namecheap in my old DNS provider (OVH - take 30 minutes)

freedns2.registrar-servers.com
freedns1.registrar-servers.com

And create the new entry in the Namecheap setup (CNAME and ALIAS)

Go back to Bubble. Delete, refresh, add. That’s it !

The advanced formula for DNS Pro in mailchimp is like 15$ per year to protect your domain better, but seems great with the free plan.

140

:tada: :tada: :tada:
WOW…
:tada: :tada: :tada:

Thank you @peterj and Bubble… I transferred over last night and it was completely seamless… ticked the box in Bubble, removed my A names, added my CNAME, and BINGO… it all just worked… I never saw a moment when my app wasn’t accessible during the process.

Page loads 2-3x faster now…

Yours gratefully,
Antony.

141

Exceptional Update, works like a charme! :100::+1::+1::+1:

142

For the ones who have their Domain registered at Google
A brief summary for Google Domain Registrar users and legacy plan holders moving over to cloudflare option with almost no downtime exptectations. Google made problems with moving to CNAME records with new “point to bubble´s -.io” address on the CNAME-@-record, so I switched the DNS right over to Cloudflare, but leaving Google as registrar of my domain:

  1. Switch on in bubble the option in Domain / email: “Accelerate this domain with Cloudflare” to “on”
  2. register at cloudflare with your domain (ie “myapp.com”), enter your domain, check for new DNS proposals (2)
  3. Go to Google Domains and your domain-name records/DNS, deactivate first of all the DNSSEC Service to avoid unwanted / uncontrolled downtimes on change process. This is important.
  4. take the DNS servers cloudflare proposed for you (2, with names as ie “adel.ns.cloudflare.com” and “clark.ns.cloudflare.com”) and copy it to your Google domain DNS list - activate them instead of the 4 google DNS.
  5. Go back to Cloudflare and take over the parameters for reactivating DNSSEC for your domain at Google Domains. Parameters for settings are ie: xxxx for key; 13: ECDSA/P256/SHA256 for Algo; 2: SHA256 for Digest Type; 1e29fe40a79bde9c7daace711XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX for Digest. Reactivate your DNSSEC with this new parameters for your safety, directly at Google Domains.
  6. Scroll down in Google Domains / DNS to “Your Ressources” and now delete the 2 “old” A records pointing to bubble (having an IP-4 address rightside ie 54.68.12.205 or other, which was needed before). Cloudflare DNS services should be activated with a green mark by now, recheck this there.
  7. Now, go to Bubble / Domain / email and click “check settings” under your Domain Name field. Message should be “You´re all set. myapp.com is working and ready to go!”
    Done, at my side with no real downtime at all.
    image
    image1900×881 348 KB
143

Hi , maybe my posting could help, …I have also Google Domains,

144

Unfortunately I have ask again why my domain doesn’t work together with Cloudflare.

I’ve setup the domain correctly, but still get the following message in Settings:

04
042034×312 46.6 KB

However, my domain is setup correctly as a CNAME only:

20
20982×624 291 KB

I still cannot access my app with this domain:

25
251848×1552 173 KB

I’ve tried and re-tried for days now without success. I hope someone from Bubble support can have a look at this?

145

@louis.brauer You’ve discovered an uncommon edge case.

Your domain has a “CAA” record. Only the Certificate Authority on record on that DNS entry is permitted to issue certificates for any subdomain on openbooking.ch. In this case, the CAA is letsencrypt.org, which differs from the Certificate Authority Cloudflare uses.

In order to get Cloudflare working, you’ll need to remove this entry:

id 39319
opcode QUERY
rcode NOERROR
flags QR RD RA
;QUESTION
openbooking.ch. IN CAA
;ANSWER
openbooking.ch. 59 IN CAA 0 issue "letsencrypt.org"
;AUTHORITY
;ADDITIONAL
146

What is the process for someone who registered their domain with namecheap already using cloudflare nameservers? The subdomain my app uses is set to bypass Cloudflare proxies. What steps should I take to configure that subdomain with Bubble’s Cloudflare implementation?

147

Subdomains are the easiest case, since subdomains support CNAMEs with no issues.

If I’m reading your comment correctly, your subdomain has a “grey cloud” on Cloudflare… when you tick the checkbox to “Accelerate this domain using Cloudflare” on Bubble, you’ll receive a new DNS record.

We proxy on Cloudflare, so when you change your CNAME to match the provided record, your site will be proxied under our account’s rules regardless of what settings you use on your account.