Yeah with Cloudflare proxy status (cloud) control is automatically disabled because it’s controlled by the Bubble. I’m still not sure if is’t working correctly like I mentioned before in my previous post.
Same thing here… 
Quick question for everyone benefiting from improved Cloudflare speed -
Do the UI elements load quicker but then the Data takes the same amount of time to load, causing slightly more time before the page looking like it’s done loaded until the actual Text and Data shows up?
Or does the speed increase of the cached visual elements allow the Data retrieval to then fire sooner and appear with the same delay as before?
(I’m not sure if Data usually loads immediately on page load, or if the Data waits for the elements and then loads)
This question is more for data heavy pages with multiple Searches and/or reusable elements where there would usually be a delay in the Data showing up
4 Likes
Great question. I’d love to see some benchmarks of a data-intensive page with Cloudflare, and the same page on a cloned app without Cloudflare.
2 Likes
Can someone screenshot exact how to set everything up with Google domains and cloudflare??? I followed the steps above and created a cloudflare account. The ssl is active. But my url only loads http, no https. Before I switched everything was fine. My understanding is that my domain registrar is Google domains and my name servers are on cloudflare along with the ssl cert.
I had to look at the server logs to figure out what had happened to your records. You’ve helped me find an interesting bug, though!
The frontend suggests that everything is good to go on Bubble, but I checked out Cloudflare dashboard and realized that when you switch from bare to www or vice versa, we’re creating Cloudflare records (on successful registration) and then deleting them (on deregistration of the old domain).
To work around this, delete your domain name on Bubble, wait a little bit, and then create a domain (either bare or www, whichever you prefer).
I am trying to do this for a customer who is on godaddy with a bare domain but no luck.
Bubble keeps giving me different IP addresses for the A record - I hit Check My settings and it comes back with a different IP, I update the A record and it changes again. I feel like the cat chasing its tail here.
Is this a bug or something I am doing wrong?
For some reason, when I try to create a test user and click the email confirmation link I get a ‘site not found’ error. My app exists on a sub-domain, but both the root and sub-domain are managed by Cloudflare. Any advice?
I aswell am I having difficulty setting up Cloudflare with Google Domains.
Earlier I was getting a 403 forbidden error.
This process is frustrating… we are supposed to switch to cloudflare with limited support… now im getting the following error… andyes I cleared the cache… no difference
I was getting that same 1014 Error yesterday. Ended up reverting to the previous settings to get my site working again.
I did see the same 1014 error, but it worked fine on incognito mode. After some time, it was working fine on normal mode too. I didn’t really make any changes to fix it. Not sure if it takes some time or not.
Sorry, I can’t be more helpful, but just highlighting my observations.
EDIT: For Bare domains: Everything looked healthy yesterday, not today. What I share below may not help you. Thanks @jonathan.timianko
The following method works for Godaddy.
1 - From the DNS settings, I set to redirect to 301 as “http://www.yourdomain.com”.
2- In Bubble, I first deleted the domain name and added a new one. “www.yourdomain.com”
3 - I deleted all my A records except Godaddy’s non-editable A record.
4 - Then I deleted the CNAME containing “www”.
5 - I added a new CNAME: “www” “app.bubble.io”
For a while, the site crashed. About 1-2 hours later it was working. It took a little longer to actives on mobile
Please note: I did it without using the A record given on the Bubble settings page. I just used CNAME.
5 Likes
who should we reach out to, in order too fix this. i really need to fix this problem. Nothing is working…
update. i started from scratch… removed the cloudflare dns… and used the default google domains nameservers. also removed all the synthetic records
Hey everyone:
Because I care for you all so much, I signed up for a GoDaddy account and registered a domain so I could make some video tutorials.
Wow. It’s slow. It’s so slow. When you change a record on GoDaddy it takes 10-20 minutes, minimum, for it to propagate, and even then it’s not always consistent. Sometimes I reload the page, and everything works; sometimes I reload the page and it looks like it broke again. So I can really sympathize with your frustration.
It took me a half hour to get enough footage to make one video, and I have to make a half-dozen of these to really document how to configure your settings properly.
Needless to say, I’m confident the instructions we’ve been giving users are correct, but GoDaddy’s 1 hour TTLs are making things look harder than they need to.
My new goal is to get some static screenshots of the process on our manual tomorrow or Friday, and to try to get videos together in the next week.
If I haven’t responded to your question on the forum, it’s because there’s already an answer in the thread. I know it’s hard to dig out the right info from such a long thread, but now that I’ve seen all the most common questions it’s better for everyone if I get good documentation out.
10 Likes
Thanks for joining in the GoDaddy trenches! I tried moving to cloudflare on a client app this evening and Bubble has yet to find DNS records pointing to Bubble. Interestingly, it seems to find different A records almost each time trying to set it up. Going the www route does work, but with some issues…
In short the process:
- The domain was already setup so we removed the existing A record (there is only one with GoDaddy).
- We added the CNAME record named www with the value app.bubble.io
- Made sure no other CNAME or A recoreds are present in the DNS settings
This didnt seem to work (or we were too impatient) so we also tried the same as above but first:
- Delete the domain on Bubble
- Wait a good few minutes before setting up again (using the bare domain) according to the instructions provided by you.
Bubble finds A records but not the CNAME.
What did work:
- Delete the domain name in Bubble
- Wait
- Add the domain name preceded by www.
- CNAME setup accoridng to instructions
I say this works, but its not without some issues that seem to be related to the bare vs www domain differences:
- I cleared cache but the browser history saved domain.com (not www.domain.com). So when i type do… and go to domain.com the request times out and the site cannot be reached.
To fix this, make sure to add a 301 redirect in the ‘Forwarding’ section in the GoDaddy DNS settings.
- There seems to be an issue loading some images. It seems to affect images that have been uploaded through the front end of the app by end users before the change was made. These images are stored on: domain.com/version-test/fileupload/file.jpg. Since these links to not have www, they are not found and thus not loaded. This only affects files uploaded by end users. Not images/files directly uploaded from the editor as they have a different url it seems.
@peterj Is there anything to fix those urls? It seems hard as they are basically static links at this point. Ideally I’d go back to setting up the bare domain in Bubble but so far that has not been successful with GoDaddy…
I also feel that the 301 redirect from the bare to the www domain is noticeable in the browser… But maybe I’m too biased at this point 
3 Likes
The 301 redirect was giving me major headaches today. You’ve got the right configuration in your screenshot, but some browsers (ahem Safari) automatically upgrade to www after a few seconds if they can’t find a record in a few seconds. Give it a day and see what happens.
As for the image issue, I think it’s a cookie thing. I’m going to try to find time to look at it tomorrow, or farm it out.
1 Like
since switching over to cloudflare all my api request have been throwing errors… looking at the log, the api is either passing null values where it shouldnt or it passes the value to the server and the server wf’s have null values… anyone else having this issue? when i make a api request the server shows the request as an anonymous user. I tried to logout and log back in—> error message i receive " Oh no!
We’re having some temporary technical difficulties right now. We’re working on the problem as fast as we can!
In the meantime, try refreshing the page or hitting “back” on your browser just in case things are working again…
We’re really sorry!
If this message does not go away within five minutes, please report the following code to the team: 1572489169117x622942991614372100"
2 Likes