I’m a legacy customer and this weekend I tried to activate domain acceleration with clouflare.
I’ve been following your tutorials, videos and posts. Everything is very self-explanatory and I think I set up my installation correctly.
I have a bar domain (fraichy.com), I transferred my DNS settings with name servers to namecheap (as mentioned). And waiting 24 hours. (My domain manager is OVH but it doesnt relly matter after the transfer).
After this, i removed my “A record” (@ - 54.69.164.32) on namecheap. Next, i enter the DNS record (ALIAS & CNAME) points to app.bubble.io (as bubble manual says)
Attached photo of the DNS records (all dns records on namecheap :
– what’s happening is we’re silently adding .io records to your dedicated instance. So, for example, if you’re on d99.bubble.is, when you turn on cloudflare, we add d99.bubble.io, and then aim requests for your sites only from app.bubble.io to this endpoint.
Behind the scenes, it looks like yourdomain.com → app.bubble.io → d99.bubble.io → (some ip address)
That changes as of today, though—as of today’s bubble version, we’ll be instructing you to use A records.
(Sorry for the delay; we’ve been working on this feature for a couple months and it’s finally ready.)
Your box is new enough to take advantage of these features (and in fact I can see your dX.bubble.io DNS entry in our records, which means someone on your instance has checked the box at least once).
The version you’re on will tell you to CNAME to app.bubble.io, but you can instead create A records pointed at: 104.19.240.93 104.19.241.93
and you’ll be good to go.
(If you don’t feel comfortable doing this with a production app, create a new test app on a subdomain, like app-test.yourdomainhere.com just to run through the steps.)
All this said, I’ve been making very significant improvements to how we handle routing and certificate issuance in the past few months, so I encourage you to upgrade your instance as soon as you feel comfortable doing so.
I am hitting the exact same issue as outlined in this post. It’s been well over 24 hours. Any thoughts on what might be causing this?
CNAME and ALIAS records are set up correctly and pointing to app.bubble.io and the DNS provider (Namecheap) is adamant that it is not an issue on their end, indeed the A RECORD IPs are your addresses.
We use cloudflare already, we use to protect certain pages and use VPN to access parts of the website along with certain security requirements we have as a security expert I feel are necessary to protect us and our clients.
However for those that cannot use your cloudflare options, can you please share the settings you have applied so i can take a look at apply them also such as workers etc etc?
It’s pretty vanilla right now, but we’re constantly moving toward increased utilization of the speed and security features CF provides.
We reserve the right to change these at any time.
At the moment:
We do not use RocketLoader, as the dynamic page rewrites it causes are poison
We use Full SSL, and we’re in the middle of moving to Full (strict)
We use Brotli, query param ordering, HTTP/2, dynamic css minification, and a couple other speed features
We use edge caching extensively, and are in the middle of some improvements here
We are not extensively using page rules or workers or most of the other features people think of when they think of CloudFlare, because it’s often difficult to implement them in a way that’s beneficial to most users without breaking legacy behavior. But also, see above: we reserve the right to turn these features on as we find ways to do so that preserve or improve performance for everyone
Based on how other CloudFlare features work, if we implemented workers, one of two things would happen:
We’d implement them to make the core bubble experience better for everyone
We’d implement them as optional add-ons for certain types of functionality
With our surface area (tens of thousands of unique domains) and account restrictions (i.e. caps on the numbers of workers we can deploy) it’s never going to be practical to enable arbitrary users to deploy arbitrary CloudFlare workers on our pages.
Trying to push an app live and getting a Forbidden 403 error.
Have tried deleting the initial setup in bubble and redoing the process - but alas same result.
Has the team given this any more thought? One area where I think this could deliver a lot of value to the majority of users would be enabling the Cloudflare worker for Prerender. Do you think this is likely?
