It seems that we are getting frequent http-crawl-non_statics bans on our server for “normal” work with Jira (e.g. moving tasks around in a board or simply updating them)
I know I can whitelist IPs but those change. Is there any other approach to address such a problem?
I’m afraid there is no clear repro. One sure thing seems to be to drag tickets back and forth between backlog and a sprint in a Jira scrum board. Sooner or later, I’ll get banned.
Unfortunately, at that point, if I try to export Firefoxe’s network connections as .HAR file, it exports a 0 byte file only, probably b/c at this point the respective server connection is dead. cscli decisions delete --ip lets me back in but the .HAR export stills doesn’t work without reloading the entire page.
Is there some log on crowdsec’s side which would tell me in detail why the http-crawl-non_statics rule gets triggered?
Here is the crawl non static scenario configuration: CrowdSec Hub
To make it short, if an IP address query more than 40 differents URL (css, jpeg, js etc… are excluded) in a short period, the scenario will be trigger.