of my VPS servers that run behind cloudflare, 80% of the cpu is just bots going for non existant fil
of my VPS servers that run behind cloudflare, 80% of the cpu is just bots going for non existant files
Cand occassionally i'll drop in, block an ASN and then it will be another ASN 1 month later
ISure but at that point it's very user-specific and Cloudflare wouldn't take action to block things on your own domain when it might be blocking things for legitimate users.
Csending any abuse type email is generally never read
IIf you want to reduce that kind of thing you can deploy your own rules that are tailored to your specific domain
II.e rate limiting rules.
Ci mean i do it for my domains already, i'm suggesting something just for pages.dev, but also my 2ndary conversation is the concept of cloudflare being the hub to lower bot traffic in the world in some way. It would be a form of community service in line with how it pushed back against patent trolls.
Cjust an idea
Canyways...carry on
Cnow getting a ton of 404's for /sito/wp-includes/wlwmanifest.xml I HATE BOTS...just flooding me.
Si get thousand of bot requests a day :Shrug:
Swe are smart and dont put credentials or anything on the client tho so we are fine
Sgod i love how many services cf offers i have to hold back to not implement everything for simple apps 
but maybe rate limiting.. just 1 more
but maybe rate limiting.. just 1 more
1Is there somewhere I can track the changes to CF docs?
C
GitHub
Cloudflare’s documentation. Contribute to cloudflare/cloudflare-docs development by creating an account on GitHub.
1Thank you wasnt sure of the exact repo
1This was the change I was trying to figure out manually 
no wonder I couldnt find it lol
no wonder I couldnt find it lol
Si updated some lib and now i get that build error even tho im using
and yes
"compatibility_flags": ["nodejs_als"]and yes
nodejs_compat
Scould this be a change from
node:async_hooksasync_hooks
KDoes hyperdrive cache queries that return 0 rows?
M#hyperdrive
MAm I right that
...will I see "hi!" in the console 5 seconds after the worker has sent a response? (And presumably I don't need to use
waitUntil()...will I see "hi!" in the console 5 seconds after the worker has sent a response? (And presumably I don't need to use
await
MIf I'm getting build errors for workers where the only error in the build log is "
Failed: error occurred while updating repository submodules
Phmmm i have an issue that cloudflare/pages-action@v1 still uses node 20 - but it seems i need node 23 to deploy the latest nuxt to it. Is the pages-action outdated? or will there be an update for it?
SAnyone know why there is suddenly a 1,000 worker route limit per account?
SI have more than 1,000 but users are now reporting this error.
SThere is nothing documented about it, and I can't even tell if the Business plan ups the limit.
SPlease do not post your question in multiple channels/post it multiple times per the rules at #
welcome-and-rules. It creates confusion for people trying to help you and doesn't get your issue or question solved any faster.
welcome-and-rules. It creates confusion for people trying to help you and doesn't get your issue or question solved any faster.THi, does anyone knows how CPU is shared between isolates (workers) ?
I am running an LZ based compression algo in Rust compiled to WASM.
For the same file compressed I see high discrepancies in CPU time: most of the time it consumes about 1500ms of CPU time but sometime 2500 or 3000ms.
The worker is just calling that wasm instance, no I/O calls.
So it seems vCPU allocated to an isolate is not fixed. This seems unfair as we are billed by CPU time and sometimes we can be billed 2x,3x for the exact same compute (no I/O involved) depending on the vCPU allocated to our isolate.
Plus the fact that it adds latency to get the response, so we pay more for slower execution..
I am running an LZ based compression algo in Rust compiled to WASM.
For the same file compressed I see high discrepancies in CPU time: most of the time it consumes about 1500ms of CPU time but sometime 2500 or 3000ms.
The worker is just calling that wasm instance, no I/O calls.
So it seems vCPU allocated to an isolate is not fixed. This seems unfair as we are billed by CPU time and sometimes we can be billed 2x,3x for the exact same compute (no I/O involved) depending on the vCPU allocated to our isolate.
Plus the fact that it adds latency to get the response, so we pay more for slower execution..
MCF devs may be interested to know that Cursor, the AI assistant, is giving 404 links to the docs. This is because the URLs it outputs are relative, not absolute, yet lack the prefix
/https://developers.cloudflrare.com/workers/ai/
SHey guys, I have a problem that my production worker is much slower then staging one even though the only difference is the traffic (the code and configuration is exactly the same). Do you know how can I fix it?
Kfeels like that is something that would be easier done external? :D
Klike a server that is set up for compression - lz compiled with cpu flags and then its probably 10ms, you could transfer the data from worker to worker and compress in way less time then
IBy definition CPU time is invariant of number of vCPUs. Even if two cores are allocated/working at the same time then there will be the same number of CPU (milli)seconds... but that can't happen in Workers because they're single-threaded anyway. Not sure what the reason for the variance you're seeing there is. How are you getting the specific CPU time metrics? GraphQL API?
TThat what I currently do, those CPU heavy algos are running from GCP cloud run with allocated CPU. Waiting for cloudflare containers to see what they have to offer
Kyeah id def outsource that part, workers always seems more of a platform for <100ms tasks :D
TThat is what i thought also, as CPU time should be invariant of vCPU allocation. But for those algos I see wide CPU time variations, seen from workers logs (beta) in CF dashboard.
AHello. Looking to understand a little more about the lifecycle of a durable object. In the constructor of the durable object class, I want to create a store and then add a listener to it. What I'm trying to figure out is how to properly clean up the listener. It's my understanding that if the do hibernates and wakes back up, it will run the constructor again. Do I need to worry about removing that listener? Is there a method I can override to include code to remove the listener? Thanks in advance.
IWhen a durable object hibernates, all memory is cleared. So in your case the store would vanish completely (and so it's fine to reattach listeners). Anything you want to persist across hibernations should be put in the DO persistent storage, either via the classic KV API or the new SQLite API.
AGreat. Thank you.
AHey peeps I'm encountering some mysterious behaviour. My Pages Function is throwing intermittent 401 errors. I traced the code back to some packages I'm using:
Debugging that shouldn't be a problem. The issue is that the 401 request that I receive in my browser is not reflected in the Real Time Logs stream.
It's mysterious because it's only ever this intermittent error that does not show up. Every other request I make I can see in the logs stream. I even deployed changes with dummy errors and they show up as expected.
It's also odd that a global try catch does not work around the auth code. There shouldn't be a code path for a 401 if I wrap my auth logic in a try/catch and throw a 418 for example.
App is a Nuxt 3.15.4 app on Cloudflare Pages. Appreciate any help.
@propelauth/cloudflare-worker which calls jose.Debugging that shouldn't be a problem. The issue is that the 401 request that I receive in my browser is not reflected in the Real Time Logs stream.
It's mysterious because it's only ever this intermittent error that does not show up. Every other request I make I can see in the logs stream. I even deployed changes with dummy errors and they show up as expected.
It's also odd that a global try catch does not work around the auth code. There shouldn't be a code path for a 401 if I wrap my auth logic in a try/catch and throw a 418 for example.
App is a Nuxt 3.15.4 app on Cloudflare Pages. Appreciate any help.
KI think there was a similar error a week ago
Khmm or maybe not, can’t find it
MLate to the party but where did you see this option mentioned?
JHello, i have some very basic questions about Pages , is this the place to ask ?
F
Hello everyone!I'm excited to share an open source tool I've developed to solve a common challenge with Cloudflare Workers: Cloudflare Microservice Secrets Manager.
What is it?A centralized microservice for managing environment variables and shared secrets across all Workers in a project. Particularly useful for microservice architectures!
Key features:- Centralized configuration for all your variables and secrets
- Environment-specific management (dev/staging/prod)
- Enhanced security with authentication and attack protection
- Automated deployment via a single command
GitHub Repository: cloudflare-workers-env-syncThis project is completely open source under the MIT license. I hope it can be useful to other developers working with microservice architectures on Cloudflare Workers.
Feel free to try it out, open issues, or contribute if you have ideas for improvements! I'd love to hear your feedback.
A big thank you to the Cloudflare team for their amazing solutions that make our crazy projects possible!
#CloudflareWorkers #OpenSource #Microservices
GitHub
Cloudflare Microservice Secrets - A centralized microservice for managing environment variables and shared secrets across all Cloudflare Workers in a project. Simplify configuration with environm...
Ehello , have someone here , I have same question about worker dev , fetch request always pending and I have no idea to fix it
Zhey so I have a CNAME for www, and a page rule, and it still effing times out on www for some stupid reason
HTo confirm, you want it to redirect from
www.zach.handley to zach.handley(assume the domain is your actual domain)?Zyeah so jonathansogunquit.com is my step fathers site for his restaurant I made, and www.jonathansogunquit.com times out with a 522 for some reason (immediately, might I add) despite having a CNAME and a page rule
Z
