Hello guys!
Im new to Cloudflare.I deployed an app for api requests testing in Cloudflare workers.After an hour of testing workers stopped proceeding my requests.In my workers panel i can see that number of requests is increasing but its not working as expected.I guess it can be bot traffic blocking .What can i do with it?I have a free plan
There’s not enough information here to know what is happening. What does it mean you “deployed an app for api requests”?
You may consider using wrangler tail to see the console log output, and writing some things to console.log to see what’s going on
To answer the question, “What can I do with it?”
Here are a great many ideas of things that you might could do with Workers:
Indeed, there are a lot of bots out there. And what’s worse is that most of them look like normal traffic, so it’s hard to block. I think it would be cool if you took advantage of some tensorflow libraries to try to guess which traffic is bots. I would be interested in what your false positive rate would be … but how would you know they were humans reporting false positives? oof. it’s a dilemma.
Personally, I like to log all my traffic in short lived keys in KV so that I can see what’s going on…though with logpush these days, it’s not necessary and might do better being pushed to a Third Party big data place.
saying “api testing” i mean that my traffic on workers is generated by program not by user.I get 403 error access denied.
The issue is very simple my automated traffic is blocking by Cloudflare bot protection.Is there an option to turn it off?
Thank you. That is more clear. I’ve never heard “api testing” used in this way before, to imply that traffic is automated. Is this a worker calling another worker? If so, they need to be set up to be “aware” of each other.
“Simple” is a dangerous word in software development. It can both sound insulting and paint you into corners.
You say your issue is “very simple” (and I’m sure it is, if we all know what you know already, and we know what we know) which assumes information undisclosed, but that’s okay…
I’m not sure what is giving you this error, you don’t say where the 403 is coming from, but…
To “turn off” any given feature of Cloudflare’s protection based on rules, you can do so with Page Rules
presumably, the Worker is not even getting the request because of some issue?
It’s possible that you are getting the Browser Integrity Check. You can configure that here:
Understanding the Browser Integrity Check
Still…here is some general info about Workers and Page Rules that is good to be aware of:
You say your “automated traffic is blocking” and then follow it with a preposition, “by Cloudflare”.
Does this mean your Worker is blocking the traffic or that your Worker is not seeing the traffic that you are sending it by some other means, or are you sending it from Cloudflare? See, because your Worker is on Cloudflare, it makes me think that your Worker is set to block your traffic, but that doesn’t make sense to me based on your trouble.
In any event, you can access the cf object in the worker to read and set various Cloudflare parameters, such as bot enforcement. Keep in mind that this is not useable in Preview.
However, you may want to just set your security setting to “essentially off”
What may seem simple is more often than not, not. If it’s simple, then you already know how to do it, so why are we here? This is why we ask for more information. It helps to know what you’ve tried, what you were expecting, and what is happening for you.
Sometimes we give you documentation so that you might find your own answer and alleviate your frustration, because we did not find enough clarity in your lengthy explanation to just answer your query simply. Also, we know documentation can be dense, so there may be things you haven’t read yet, or which you might not know to read.
We are a community of volunteers mostly, not employees, so please keep that in mind. Questions that go unanswered are most often too vague to know an answer and/or would insult anyone attempting. We’re here to help, and you’re frustrated, but we’re not here to insult your intelligence nor become insulted.