Score:0

Fail2ban failregex didn't detect

cn flag

I'm getting a lot of error messages with the following:

Received From: server->/var/log/syslog
Rule: 1002 fired (level 2) -> "Unknown problem somewhere in the system."
Portion of the log(s):

Mar  6 09:18:20 server runcloud[628]: echo: http: TLS handshake error from 87.236.176.137:49883: EOF

I setup a failregex on my jail.local to ban the IP address if it got detected:

[sshd]
enabled = true
logpath = %(sshd_log)s
port = 22
banaction = iptables-multiport
mode = aggressive
failregex = %(known/failregex)s
            ^Bad protocol version identification '.*' from <HOST>
            ^runcloud\[\d+\]: echo: http: TLS handshake error from <ADDR>:\d+

[runcloud-agent]
enabled = true
logpath = /var/log/runcloud.log
banaction = iptables
maxretry = 2
failregex = ^\s*\S+ runcloud\[\d+\]: echo: http: TLS handshake error from <ADDR>:\d+

I rebooted fail2ban and I didn't get an error message. Today I got a email like above and the failregex failed to add the IP address to the ban list.

What am I doing wrong and how to fix it?

I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.