In light of vulnerabilities like RegreSSion, we need to have fail2ban installed and configured for our containers (with mode = aggressive). Moreover, our docker logs for the web front end are basically unusable because of all the hacking attempts... Fail2ban would be a cheap way to keep it under control: ``` 2026/01/16 07:31:00 [error] 31#31: *6062 open() "/app/aa.php" failed (2: No such file or directory), client: 172.18.0.1, server: , request: "GET //aa.php HTTP/1.1", host: "service-meteoio.slf.ch" 2026/01/16 07:31:00 [error] 31#31: *6062 open() "/app/ext.php" failed (2: No such file or directory), client: 172.18.0.1, server: , request: "GET /ext.php HTTP/1.1", host: "service-meteoio.slf.ch" 2026/01/16 07:31:00 [error] 31#31: *6062 "/app/wp-includes/js/dist/index.html" is not found (2: No such file or directory), client: 172.18.0.1, server: , request: "GET //wp-includes/js/dist/ HTTP/1.1", host: "service-meteoio.slf.ch" 2026/01/16 07:31:01 [error] 31#31: *6062 "/app/wp-includes/SimplePie/index.html" is not found (2: No such file or directory), client: 172.18.0.1, server: , request: "GET /wp-includes/SimplePie/ HTTP/1.1", host: "service-meteoio.slf.ch" 2026/01/16 07:31:01 [error] 31#31: *6062 open() "/app/av.php" failed (2: No such file or directory), client: 172.18.0.1, server: , request: "GET //av.php HTTP/1.1", host: "service-meteoio.slf.ch" ```