Replies: 1 comment 7 replies
-
|
Did you check your limiter is setup correctly / read this two comments about "how":
Further I can recommend to apply the patch from this PR: I use it since 5 month and it blocks 99% of the requests on my instance (yes I have 99% bot requests). Further I recommend to use ipv4 only (the address space on ipv6 is to large for efficient blocking of IP addresses). |
Beta Was this translation helpful? Give feedback.
-
|
I think my settings are ok, since I have jailed almost 2,500 bots. As for the PR, since I use the docker image, should I really set the docs/src/searx.botdetection.rst, searx/botdetection/_helpers.py and searx/botdetection/http_sec_fetch.py in volumes to manage them ? I fear it might break a future evolution ?... |
Beta Was this translation helpful? Give feedback.
-
|
To apply a PR on your instance you need to branch, a branch can regularly rebased .. don't hack with docker. |
Beta Was this translation helpful? Give feedback.
-
|
@Eirikr70 make sure to read the comments in order to understand the potential consequences in blocking legitimate trafic. |
Beta Was this translation helpful? Give feedback.
-
|
@unixfox as for the legitimate trafic, there is no risk at that stage since my instance is permanently out of order because of the illegitimate trafic. |
Beta Was this translation helpful? Give feedback.
-
|
@return42 I applied the branch. Hope it will work ! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
Would it be possible to set personalised parameters for blocking the bots ? I ask this since I am being blocked by most of the search engines for "too many requests" and would like to set stricter rules. I have already set a fail2ban filter that excludes all suspicious behaviours for 24 h but it doesn't seem to suffice.
Beta Was this translation helpful? Give feedback.
All reactions