Santosh Pandit

For my particular needs, I have disabled the HTTP/1.0 connections on nginx through the following command in the server context. if ($server_protocol ~* "HTTP/1.0") { return 444; } However, when...

Same issue for me. Unbound version is 1.13.1 installed on Debian Sid. unbound-anchor has been run to update roots. Domain not resolving is "bit.ly".

I am not a programmer, but if you could add openvpn and other functionalities (based on sslh) that would be fantastic. I will be happy to test and give feedback.

Oh, the solution from @ansell works like this. Although the access.log file still contains the following entry when the offending IP visits you for the first time... 20.243.nn.nn - -...

The logpath in jail and location of access_log in nginx are different in your configuration and hence fail2ban does not pick up.

On Debian Testing (currently 11 Bullseye), I had massive problems with jvb (no java machine error). Followed this step: apt remove --purge openjdk-17-jre-headless It reverted automatically to the following version:...