@JaredBusch said in Fail2Ban: Failed to access sock path:
@gjacobse said in Fail2Ban: Failed to access sock path:
Since that is a screen shot, it appears that some parts of the code is cut off.
You are not listening. I said previously posted.
Thus, you need to look before that.
There in the actual .local file I did post, you will see an action listed. In the settings of said action is one of those options.
I posted that screenshot of with the intentional size because it contains the comment regarding what each does as well as the format.
Actually, I was and am listening. When I you are working from a 6.5” diagonal screen as I have been, you likely miss a bit of information.
That said - not that it likely makes any difference.
# fail2ban-client status sshd Status for the jail: sshd |- Filter | |- Currently failed: 24 | |- Total failed: 92 | `- Journal matches: _SYSTEMD_UNIT=sshd.service + _COMM=sshd `- Actions |- Currently banned: 2 |- Total banned: 2 `- Banned IP list: (IPs)