Stefatorus
CDCloudflare Developers
•Created by Stefatorus on 8/13/2024 in #general-help
Cloudflare Fails to mitigate DDoS Attack, Enabling "Verified Bots" doesn't block deindexing it
For the past years, I believed Cloudflare was a trustworthy company, and have seen it as an example in the field. Highly ethical, always on the edge of innovation, full of competent people, great market coverage.
I even started slowly racking up stocks on Cloudflare beginning in 2019 due to this. But since then, I've seen more and more articles about how Cloudflare failed for them.
I've shrugged off the employment drama because a company needs to stay profitable and sales in Enterprise B2B is hard and requiring.
I've shrugged off the casino complaining of being dropped off Business plan when they were bypassing ISP limits and affecting the Cloudflare IP Trust and generating issues for other customers.
Now what should I believe when I myself have my whole site deindexed in a critical period for us (we're now leading in sanctioning the Govt. for a corruption case for mismanagement of EU funds, and Google is how people found about us)?
I've got DDoSed (Layer 7) quite heavily, I thought Cloudflare mitigates out of the box, but I was wrong. It doesn't, most of the requests (or at least plenty to overwhelm our backend server) were going through. Not DOS, DDOS. Hundreds, if not thousands of different IPs.
We managed to resolve and mitigate the attack with Super Bot Fight Mode which "detects bad bots". We allowed "Trusted Bots", which seems not to cover Google, Bing, Yandex bots via IPv6.
I haven't complained of extra usage that was billed on Workers / Pages, it was negligible. I didn't complain of extra usaged on D3, it was negligible, ~1$ per hour and we mitigated it fast with Super Bot Fight Mode.
But I am highly skeptical that Google will maintain us on #1 page after we answered 403 on our most important pages for days on end. We know we got deindexed, how google will treat the resolution of the 403s, not sure.
Screw cloudflare. We got Cloudflare for stability and for it's reputation. It seems things have changed since we started using them heavily.
76 replies
CDCloudflare Developers
•Created by Stefatorus on 12/11/2023 in #general-help
AMP not working when proxying via I18N proxy made using Cloudflare Workers
https://support.google.com/webmasters/thread/247720215/google-not-indexing-amp-links-correctly
We have issues indexing our AMP pages on Google, due to an unspecified reason.
Website: https://www.incorpo.ro/
Backend (behind proxy, no cloudflare optimizations): https://base-docs.incorpo.ro/
The content on the base-docs content seems to AMP index correctly, but behind our proxy, it breaks.
We haven't been able to use the AMP debugger (it says an error occured and doesn't mention what, outside retrying in a few hours).
Example amp URLs:
https://www.incorpo.ro/en-us/articles/the-right-way-to-spend-on-marketing-in-tough-economic-times/amp/
https://base-docs.incorpo.ro/articles/the-right-way-to-spend-on-marketing-in-tough-economic-times/amp/
They seem to be AMP valid, but for some reason Google fails indexing or (crawling?) them
Suggestions?
1 replies
CDCloudflare Developers
•Created by Stefatorus on 11/24/2023 in #general-help
Cloudflare Polish & Mirage not working on CF Pages
Cloudflare Polish & Mirage doesn't seem to work for converting .PNGs here to .webp images.
Content type is still image/png:
https://www.incorpo.ro
6 replies
CDCloudflare Developers
•Created by Stefatorus on 1/22/2023 in #pages-help
Error: Failed to publish your Function. Got error: Error: Script startup exceeded CPU time limit.
Pages.Dev: incorporo-frontend.pages.dev
deploymentID: 7dde2186-27db-4130-a00b-8178da82751f
accountID: 29688401a993aa199d55e08d1e90c210
Error Log:
Error: Failed to publish your Function. Got error: Error: Script startup exceeded CPU time limit.
1 replies