[New feature] Cloudflare for all

[syhsamantha]

Hi, thanks for the tips with GoDaddy. I have 2 domains with them. I thought about deleting the domain on Bubble, as you described here. My question is what happen to the workflows built on Bubble? Are they all deleted as well once the domain has been deleted? Thanks.

[syhsamantha]

Thanks for you sympathy for GoDaddy users on Bubble. Hope to see the video soon!

[caeroa]

Hi @peterj , this is amazing, my main app has been working for already 2 years, mainly with users in Colombia, South America and now with cloudfare will be way faster!
Now, I had my domain in godaddy, I just transferred it to Namecheap, did all the steps, worked perfectly for a coumple of minutes , check the speed in pingdomain.com and went from 4.06 secs. to 690 milisecs… So impresive, but sudenly I am getting an Error 525 SSL handshake failed, and it is saying it is in the hosting, please take a look:

Over https does not work, over http it does, so I had to go back to my domain without www and remove the CNAM adn ALIAS pointing to app.bubble.io and go back to the A records, any help here? I really want to use cloudfare, and that is why I went from godaddy to Namecheap (in godady the forwarding does not work properly)

[kenlaji]

What does ‘IPv4’ is not valid error mean @peterj ? See my post above.

[simon]

Trying to role back because can’t get GoDaddy to work and get two A record IP addresses to use - which one is correct? Is this a Bug?

[eren]

I got it back last night, and I met this bug. I tried starting with 54.203.28.28, it works.

[simon]

Thanks Eren, that was the solution - use the ones in the image not the one in the text

[miguel]

I am having some weird behaviour with workflows recently, but I have still not switched on Cloudflare, so I am not sure the strange behaviour is related to Cloudflare:

• One API workflow cannot access now some parameter’s fields (the parameter is a custom Thing), even if I set the wf to ignore privacy rules. I believe it used to work fine a few weeks ago.

• A different API workflow modifies a parameter’s field, but some weeks ago it seemed that the parameter was passed by reference (because changes to that field would be seen by another instance of that workflow), but now it seems that the parameter is passed by value (a copy of the original parameter) because changes made to the parameter by an instance of the API workflow are not seen by a different instance of the same API workflow.

Again, not sure if this strange behaviour is related to Cloudflare, but certainly seeing some odd behaviour with API workflows parameters.

[3brotherssupply]

i understand that tech isnt easy at all but a lot of us are on pro accounts… meaning we are paying a good amount for our apps. that price change was rolled out without any warning… now the cloudflare rollout came… seemingly with minimum testing and there are a lot of us that have apps that are basically worthless… if login/logout doesnt work properly you cant do much.

[3brotherssupply]

is there any updated solution to this issue??? im having all types of issues which i didnt have prior to attempted this cloudflare switch… now i can do simple task such as sign up a new user, or login a current user… the workflows says im not sending a email with the request… i submitted a big request and sent a email to bubble support… with no response… im a user on a pro account paying well over $100/mo. All we are asking for is some sort of support/response.

[eve]

@miguel @3brotherssupply We have received a number of reports regarding this issue and our team is currently investigating.

[gaffneyantonio]

I just switched as well and I’m having all kind of issues, too. Can’t run as user, elements not showing, pages showing blank.

[3brotherssupply]

Is there any update to this situation???

[deliriousmiles]

Just wanted to give a shoutout to all you early adopters putting your apps on the line testing out Cloudflare while the rest of us watch and learn! Good luck!

[joe5]

I am having a lot of issues with my community app (nucode.co) after switching to Cloudflare.

I switched from bare to www. and am using google domains.

1. Some items load immediately and then repeating groups take forever even though they’re limited to fixed cells or are using extended scrolling. Whereas before they didn’t have this issue.
   2.Some pages are loading significantly slower than others on content pages (like a blog post). I’m even waiting to load all repeating groups on the page until after the page is loaded.

I’ve even boosted my app to meet the professional plan for speed, and that has still not helped at all.

[3brotherssupply]

is it possible for bubble to roll back all the apps in question the settings prior to the cloudflare implementation until this is all sorted out because its clearly a big issue…also this doesnt present as an outage but it shoud… if workflows are passing nothing but null values you basically have a static home page.

[peterj]

Hey all
Videos are up:

[Video Walkthrough] Cloudflare configuration

Hey all, We’ve listened to your questions and requests, and have put together some videos showing you how to configure your app on Bubble with Cloudflare. We’re still working on getting the manual pages up (the videos turned out to be the easier task to complete), so without further ado: Networking 101 Four videos on what happens when a user requests your site. These should help you understand what you’re trying to accomplish. Legacy principles ALIAS records Using a different name server N…

And documentation is live:

[Documentation] Configuring your Custom Domain with Bubble + Cloudflare

I’ve condensed the answers to all the most common questions about configuring domains into a document linked in the manual: https://manual.bubble.io/application-settings/configuring-dns-records.html It’s a little sparse in pictures, but we will keep improving it over time. If you’re having difficulties, look at the Frequently Asked Questions for an answer. We will keep iterating on these as new questions arise, but seeing as, as of three days ago I wasn’t seeing any new difficulties that we h…

I’ve got a busy week ahead, fixing some weird edge cases across the platform, but this info should be enough to get you over most difficulties.

Also, FYI, Cloudflare is live for all Dedicated customers as of 10 pm today. You can access the features by re-deploying your box.

Free tier (bubbleapps.io) customers will be migrated to Cloudflare as early as Monday.

[peterj]

For future users, here is the explanation for what happened here, and why we no longer recommend switching from a bare domain to www for Legacy Customers:

We perform 301 redirections when a customer is on a bare domain, but they receive a request to www.

301 redirection turns all requests, no matter what method they use, into GET.

API workflows all use POST requests (with a small number of exceptions).

A POST, converted to a GET, loses its query body. So what was a functioning workflow turns into an unsupported method (GET) with an empty query, which manifests as “APIs are broken.”

In 2014, the IETF issued a RFC for HTTP 308, which is method-preserving (POST remains a POST). If we can find a way to implement 308 redirects safely for all users, we may do so in the future, but since it’s so new it breaks compatibility in certain browsers (mostly Internet Explorer).

[3brotherssupply]

Ok, so to be clear. Currently running as www.mydomain.com and in the process of reinitializing all my api request… should I switch back to mydomain.com or leave it as is???

[peterj]

If your custom domain as listed in Settings -> Domain is “www.mydomain.com”, then you should either:

1. Change back to mydomain.com, and follow the instructions in the video link/documentation post to change your nameservers to one that supports ALIAS records

Or

2. Update every single API workflow that calls your app, to use www.mydomain.com instead of mydomain.com

Since API urls don’t really affect SEO, we may be able to roll out a quick change that neither redirects nor breaks Internet Explorer support. I’ll run it by the room next week and see if there are obvious unanticipated issues supporting APIs this way.