Actualización automática cada 30 segundos
Status |- Number of jail: 3 `- Jail list: nginx-http-auth, postfix, sshd
['197.225.146.23', '151.19.97.222', '182.42.93.139', '92.118.39.56', '91.224.92.190', '20.255.61.0', '80.94.92.177', '103.101.162.38', '209.38.43.218', '165.245.140.170', '51.77.222.24', '1.214.42.172', '103.164.20.29', '209.141.62.124', '197.248.104.31', '45.78.224.19', '51.68.226.87', '194.107.115.65', '175.173.168.124', '101.36.98.91', '38.22.160.113', '103.250.10.42', '115.190.73.63', '154.92.109.196', '188.166.115.143', '101.47.161.72', '165.245.136.174', '101.36.119.184', '94.204.104.134', '189.47.10.100', '98.70.127.17', '88.142.46.185', '121.228.31.181', '45.78.219.124', '162.241.87.197', '216.227.168.71', '190.129.122.12', '34.58.124.191', '14.103.118.194', '185.193.240.246', '152.32.145.111', '144.48.8.10', '213.142.148.132', '203.55.129.202', '45.78.218.124', '14.103.203.191', '203.15.2.16', '45.78.222.208', '187.188.0.71', '45.78.219.68', '119.53.253.2', '81.192.46.32', '45.78.217.218', '45.78.201.208', '40.127.67.83', '183.82.126.193', '72.17.34.38', '69.6.215.53', '102.211.152.138', '78.89.154.59', '80.94.92.165', '5.23.55.83', '54.38.190.246', '92.118.39.95', '92.118.39.87', '34.175.118.185', '103.183.74.205', '192.3.179.41', '115.190.216.185', '103.183.74.130', '189.243.26.187', '101.126.54.245', '80.94.92.166', '101.89.148.7', '12.182.125.210', '92.118.39.62', '39.109.104.252', '41.203.213.8', '102.88.137.145', '157.245.66.63', '23.95.193.133', '45.78.218.144', '49.49.230.84', '101.47.161.104', '14.103.112.243', '45.148.10.147', '91.224.92.108', '211.219.22.213', '193.23.199.107', '103.187.146.107', '185.194.199.46', '45.148.10.141', '160.251.172.221', '45.227.254.170', '91.224.92.54', '2.57.121.25', '91.224.92.78', '45.148.10.157', '200.32.52.150', '34.85.163.94', '152.32.171.99', '52.159.248.242', '219.92.10.113', '2.57.122.208', '2.57.122.238', '80.94.92.183', '45.148.10.151', '45.148.10.152', '193.32.162.146', '189.89.20.45', '195.178.110.30', '129.212.178.51', '104.152.40.8', '103.226.139.207', '45.78.216.165', '45.40.57.41', '101.47.140.254', '101.47.161.128', '118.99.80.24', '218.0.63.25', '51.79.165.204', '36.50.63.131', '45.78.219.16', '13.93.203.231', '206.217.131.233', '162.240.109.153', '216.10.245.205', '45.78.206.228', '95.130.227.106', '154.221.28.214', '181.237.110.91', '211.213.96.6', '45.78.217.106', '54.38.52.18', '180.184.176.74', '5.42.239.222', '179.43.174.100', '188.166.88.153', '93.123.109.38', '134.199.196.185', '105.27.148.94', '103.234.151.178', '101.47.160.45', '165.232.85.109', '137.184.111.54', '2.57.121.112', '188.166.103.176', '188.166.107.135', '77.169.143.147', '101.47.163.219']
2026-01-24 09:48:42,715 fail2ban.utils [3188200]: ERROR 76ea28037200 -- exec: ( printf %b "Subject: [Fail2Ban] sshd: banned 101.47.163.219 from vps-6a98652a.vps.ovh.ca From: Fail2BanThe IP 101.47.163.219 has just been banned by Fail2Ban after Fail2Ban" ) | /usr/sbin/sendmail -f "no-reply@sostechags.xyz" "salvador.gallegos@sostechags.xyz" 2026-01-24 09:48:42,716 fail2ban.utils [3188200]: INFO HINT on 127: "Command not found". Make sure that all commands in '( printf %b "Subject: [Fail2Ban] sshd: banned 101.47.163.219 from vps-6a98652a.vps.ovh.ca\nDate: `LC_ALL=C date +"%a, %d %h %Y %T %z"`\nFrom: Fail2Ban \nTo: salvador.gallegos@sostechags.xyz\\n\nHi,\\n\nThe IP 101.47.163.219 has just been banned by Fail2Ban after\n3 attempts against sshd.\\n\\n\nHere is more information about 101.47.163.219 :\\n"\nwhois 101.47.163.219 || echo "missing whois program";\nprintf %b "\\nLines containing failures of 101.47.163.219 (max 1000)\\n";\nlogpath="/var/log/auth.log"; grep -m 1000 -wF "101.47.163.219" $logpath | tail -n 1000;\nprintf %b "\\n\nRegards,\\n\nFail2Ban" ) | /usr/sbin/sendmail -f "no-reply@sostechags.xyz" "salvador.gallegos@sostechags.xyz"' are in the PATH of fail2ban-server process (grep -a PATH= /proc/`pidof -x fail2ban-server`/environ). You may want to start "fail2ban-server -f" separately, initiate it with "fail2ban-client reload" in another shell session and observe if additional informative error messages appear in the terminals. 2026-01-24 09:48:42,723 fail2ban.utils [3188200]: ERROR 76ea28037200 -- exec: ( printf %b "Subject: [Fail2Ban] sshd: banned 101.47.163.219 from vps-6a98652a.vps.ovh.ca From: Fail2Ban The IP 101.47.163.219 has just been banned by Fail2Ban after Fail2Ban" ) | /usr/sbin/sendmail -f "no-reply@sostechags.xyz" "salvador.gallegos@sostechags.xyz" 2026-01-24 09:48:42,723 fail2ban.utils [3188200]: INFO HINT on 127: "Command not found". Make sure that all commands in '( printf %b "Subject: [Fail2Ban] sshd: banned 101.47.163.219 from vps-6a98652a.vps.ovh.ca\nDate: `LC_ALL=C date +"%a, %d %h %Y %T %z"`\nFrom: Fail2Ban \nTo: salvador.gallegos@sostechags.xyz\\n\nHi,\\n\nThe IP 101.47.163.219 has just been banned by Fail2Ban after\n3 attempts against sshd.\\n\\n\nHere is more information about 101.47.163.219 :\\n"\nwhois 101.47.163.219 || echo "missing whois program";\nprintf %b "\\nLines containing failures of 101.47.163.219 (max 1000)\\n";\nlogpath="/var/log/auth.log"; grep -m 1000 -wF "101.47.163.219" $logpath | tail -n 1000;\nprintf %b "\\n\nRegards,\\n\nFail2Ban" ) | /usr/sbin/sendmail -f "no-reply@sostechags.xyz" "salvador.gallegos@sostechags.xyz"' are in the PATH of fail2ban-server process (grep -a PATH= /proc/`pidof -x fail2ban-server`/environ). You may want to start "fail2ban-server -f" separately, initiate it with "fail2ban-client reload" in another shell session and observe if additional informative error messages appear in the terminals.