Bidk, I see a note in the cloudflare dashboard that my domain is covered. Google chrome also displays this message when navigating through the domain.
B
Eshould be a button on the dash to contest the decision, you should also have got an email you can reply to
BBut this is a regular file sharing service made as part of a college project. I don't know, apparently someone decided to make a joke by sending a huge number of reports
BI have already pressed it, but I do not know how long my request will be considered or whether it will be considered at all. After all, technically, according to cloudflare, a huge number of users have sent a complaint and their checks, it seems to me, may not give the desired result
Etheres no ETA or guarentee, and nothing anyone here can do to help, if you have questions you can email
abusereply@cloudflare.comBthanks
HWhich part?
GHi, a bit more than 3 months ago, I got a cloudflare email asking me to renew my certificate by adding a TXT record to my domain. It updated it correctly. Now I got a new email ~3 months later to do the same thing with a new TXT record value. Let's encrypt certificate is valid for 3 months, I am wondering If I am expected to do this task every 3 months manually ?
EI read that hono page as saying that the hono feature is deprecated, not necessarily a Cloudflare feature
Ebut also, that relies on Workers Sites https://developers.cloudflare.com/workers/configuration/sites/
which says
which says
Use Cloudflare Pages for hosting full-stack applications instead of Workers Sites. Do not use Workers Sites for new projects.
Esure it could be more clear if its acttually deprecated, but it does say don't use it
Eright but if Hono wants to deprecate their static file feature that's separate to anything Cloudflare might wish, so you still need to approach it from that angle if using Hono
EIf you wanted to use Workers Sites directly I don't think anything would stop you and I doubt Cloudflare will kill it without sufficient notification first
But if you want to use Hono's static files feature, it's marked as deprecated so they could freely remove it in an update if they wanted to
But if you want to use Hono's static files feature, it's marked as deprecated so they could freely remove it in an update if they wanted to
EMakes sense and no problem
Cit shouldn't be blank blank inside of the pdf though
Cshould say some free zones/subs
Eonly if you have a subscription thats $0+usage
Esubscriptions that are $0 flat with no extra costs shouldnt cause it
C^ you've got r2 and ir
Cit's not a blank pdf
Cyou said "blank invoice" so I was just covering that edge case lol
Canyway based off what Erisa said sounds normal, you've got paid usage based subscriptions like r2/ir
Cthink the only option you've really got there is changing the email which gets them
Cpart of the billing system change I believe
MIs it possible to submit feedback about the Cloudflare Zero Trust product?
Con the forums would be best: https://community.cloudflare.com/c/feedback/feature-request/30 there's a few Zero Trust tags on there. There's no zero trust cf employees in this disc (hence no channels/etc)
Ethe billing system was changed to Stripe and I was told thats just how Stripe works, they generate invoices even for no usage on usage-based products. theres an argument to be made that Cloudflare could skip sending these generated $0 invoices, but apparently they chose not to. filtering at your email provider is the best path
RHi there, am using an R2 bucket and have uploaded a pic there, I'd like to use the pic in a website, but just via link, how do I do this please? Sorry Im a newbie to discord chats..
CYou are going to want to add a custom domain to your bucket then you'll be able to use a link
Yquestion: I get error 1000, DNS points to prohibited IP. The A records are pointing to cloudflare after upgrading to pro plan. My hosting, bluehost is saying I need to pick one, either bluehost or cloudflare. Not sure how to fix this.
IYou don't point the A record to Cloudflare. You need to get the IP address at your Bluehost server and then, from the Cloudflare dashboard, point the A record to those.
ICloudflare doesn't host your website and so pointing an A record at them won't work.
YThanks for your response. I see 4 different a records in cloudflare. Not sure how that happened honestly because I did not manually add them in there. Should I only have 1 a record, which is what bluehost told me to use?
IYou should have one A record, yup. Any other records like NS or DOA you can ignore, those are intentional.
Yok, so I deleted the 4 a records, and will only have 1. Should the name be @?
IIf you want
www.yourdomain.com to also work then you'll need one at www as wellYOk, what about the AAAA, and MX?
IYou should be OK to remove/don't put the AAAA, Cloudflare will handle IPv6 for you automatically. And for the MX, it only matters if you want to receive email on your website.
INote that if you add the MX record your server IP will be exposed so people can potentially see that and bypass Cloudflare.
YI see, so then I'll just remove AAAA and the MX from cloudflare. This should fix the error 1000?
