nullerror
CDCloudflare Developers
•Created by nullerror on 11/11/2023 in #general-help
"This hostname is not covered by a certificate." on all DNS records
Hi all
Today I woke up to my site displaying a "This site can’t provide a secure connection" on Chrome and a "This hostname is not covered by a certificate." on all my DNS records. Not sure what happened? I was under the impression my site would be covered by universal SSL?
My site is active and has been for several days (in fact, was working for several days until today)
I don't have any "multi-level" or whatever you call it domains like test.blah.hello.com. I have one DNS record that's one domain level and should be covered by Universal SSL.
Any ideas?
2 replies
CDCloudflare Developers
•Created by nullerror on 11/7/2023 in #general-help
Confusion surrounding Cloudflare X Backblaze "Bandwidth Alliance" and free egress with CDN
Hi All
I'm a bit confused surrounding the nature of the Cloudflare and Backblaze B2's relationship and how this whole "free egress" with CDN works.
According to "Deliver Public Backblaze B2 Content Through Cloudflare CDN" it states that "you can store content with Backblaze B2 Cloud Storage and serve it to users using Cloudflare's CDN (Content Delivery Network) with no download fees from Backblaze". Which sounds amazingly sweet however I'm a bit confused in regards to the no download fees "from Backblaze" part. It sounds like I'll still be getting charged fees from Cloudflare? Is this the case? I've tried looking online and maybe I don't have the right search terms but I can't find any sort of pricing regarding this it sounds like it's completely free?
My use case is a large Backblaze B2 bucket serving between 1GB - 100GB to my personal server per day. Currently I'm biting the B2 download egress fees but this sounds like a way out if I'm understanding correctly.
5 replies
CDCloudflare Developers
•Created by nullerror on 11/4/2023 in #general-help
CNAME still not working?
Hi all. Just became aware of the outage. I set up a new CNAME for my site (following the Backblaze B2 with Cloudflare CDN guide online "Deliver Public Backblaze B2 Content Through Cloudflare CDN") last night and it is still not working. According to the status page of the outage "DNS Updates: Restored" however this change still is not accessible. I tried re-adding the CNAME again after seeing the updated status but the change is still not accessible on my end and on DNSChecker. Leads me to believe I'm doing something wrong?
Possible unrelated info but provided as background incase (see CNAME info below)
My DNS Records includes only 8 A records 4 of which are "www" and the other four seem to be the root site. They all point to some IPs I think for webpage hosting? It's been a long time since I set this site up so I'm not sure but regardless they are working and not part of the larger problem. Just including this info in case it is relevant. Also these were set up a while ago.
The issue is with the single CNAME record I have with name "forever" and target "f00X.backblazeb2.com" with proxy status enabled just as is done in the above mentioned guide. Going to forever.mysite.com/file/bucketname/filename should result in a download but instead I get
forever.mysite.com’s server IP address could not be found. ERR_NAME_NOT_RESOLVED
Any ideas?
4 replies