I’ve got an idea for a feature-add we could do to turn pages into proxies, but it would have to be assessed for security &c. Because there are potential security concerns with the approach I have in mind, it might have to be based on a narrow whitelist of proxy providers (e.g. ghost) instead of being a free-for-all.
As to the broader question of how to get orange-to-orange/Cloudflare workers/more Cloudflare features available in general: we’ll discuss with our account manager what the ramifications of that would be, if at all possible. I thought it was as simple as checking a box, but in the past couple days I went looking for resources on orange-to-orange and noticed that Shopify (who are much bigger than Bubble) have been dealing with the same frustrations we are, and they don’t have a solution for it either.
this is great news, Peter, would this depend on the second part of your message or this would work regardless?
Whitelisting sounds like a good approach - apart from ghost maybe you could allow airtable, webflow (and i guess more can be added based on user requests in cases where it makes sense)
Any ETA for this?
Thanks!
It’s highly hypothetical for now. I can see what steps it would take, and we have an excellent pre-existing use-case we could test on it, but it depends on the overall product roadmap and the aforementioned security concerns.
Were we to do it, it would not rely on orange-to-orange, which would be a different project altogether. Aspirationally, I’d like to kill all the reasons for people wanting to use their own Cloudflare accounts by expanding our own feature set.
I’m especially attuned (you might even say myopic) to domain-related feature requests (whitelabeling, path proxies, etc), because I have a good idea what it would take to make them work, but we have a much more pressing performance roadmap that tends to suck all the air out of the room when it comes to these kinds of requests.
Thanks, Peter,
but I’m still not sure I understood whether you are going to be working on this in the near future or in a more distant one. Or you need to discuss this with the team to decide that?
I do a lot of work in my free time to validate/invalidate potential features. (You’re welcome. ) I know what my proof-of-concept code would look like, and in the next 2-6 weeks I plan to attempt to make it happen to see why (if) it would be a bad idea.
This feature is desirable, but when I asked about feasibility recently I was told that it’s probably harder than I’m assuming. So I’m going to try it for myself.
Hi @peterj I hope you are doing well. Just wanted to check in and see if you found time to look into a way for bubble users to make use of cloudflare workers directly or create proxies more easily?
I’m currently using a custom edge proxy that a friend wrote for me in order to achieve pretty URL’s (Mysite.com/username) but I know it’s a short term solution and we have run in to a problem or two with it recently.
Bubble says its unable to look up A record 104.19.240.93. Sometimes it has an issue with the other A record, and sometimes it has an issue with both. Often, when I simply hit the “Check my Settings” button it will say the issue is resolved. However, if I refresh the page the error almost always pops back up. My site is loading without an error, but it is PAINFULLY slow. I know there are some areas of pages that I need to clean-up, but the landing page which has nothing more than texts and links to other pages is also loading very very slow.
Thanks, Johnny. I waited a little longer for the site to transition from GoDaddy community servers to the Cloudflare servers. Additionally, I disabled an old backend workflow that I was no longer working. It may have been being unintentionally triggered and if so would have been an endless loop. The site is running fast again and the error has stopped popping up in the Bubble settings. Not sure exactly what the fix was but it seems to be working well.
I´ve just came into an issue since my app is a subdomain like app.domain.com and it´s using the cloudflare feature and works perfect.
The problem now is that I want to add my domain.com website into cloudflare but if I do that it affects to the app breaking everything.
Is there anything I can do to have the built in cloudflare of Bubble for my subdomain and other cloudflare for my domain.com website which is in Wordpress?
That should be possible. When we establish records on your behalf, we only register the record(s) you provide (so, for app.domain.com we only redirect that one to bubble). You’re free to point any other subdomains to any other valid endpoint on the web.
If you want to give me more specific details via DM, feel free. For instance, what’s your real domain, who’s your registrar, what your proxy configuration is, etc.
Hi, I am experiencing an issue that seems related to Cloudfare. The custom domain name of my site is gosaily.com, in Bubble it is set-up correctly and works fine. Now I am trying to add a sub domain as tutorial.gosaily.com that point to a gitbook space, so I added in my registrar panel a CNAME that points tutorial.gosaily.com to hosting.gitbook.io. But it does not work …
I think that Cloudfare should be out of the way with sub domain, but I may be wrong. Anybody con help ? maybe @peterj can advice me on how to solve this. Thank you
gitbook is running on their own cloudflare distribution:
;; ANSWER SECTION:
tutorial.gosaily.com. 900 IN CNAME hosting.gitbook.io.
hosting.gitbook.io. 300 IN A 104.18.0.145
hosting.gitbook.io. 300 IN A 104.18.1.145
;; AUTHORITY SECTION:
gitbook.io. 3594 IN SOA dahlia.ns.cloudflare.com. dns.cloudflare.com.
(the telltales are the 104. IP address and the cloudflare nameserver)
It’s possible there’s a conflict there, it’s possible you need to change your configuration on gitbook; it may be something else entirely.
Perhaps I’m misunderstanding, but when I consult the docs, I see no mention of bare domains, and the documentation screenshot shows app.bubble.io as the value for both ALIAS and CNAME.
As a result, I’m still unclear as to what exactly will happen when I enter my desired domain - a bare domain - into the field under app settings.
All I want is to have mydomain.com as the canonical domain and for www.mydomain.com to redirect to it.
Am I good to go if I simply enter the bare domain into the settings page and then change the DNS records as the settings page will [presumably] suggest?
) I know what my proof-of-concept code would look like, and in the next 2-6 weeks I plan to attempt to make it happen to see why (if) it would be a bad idea.
…
