Skip to main content

centos7 - fail2ban running on CentOS 7 & getting “ssh connection refused”

Is anyone successfully running fail2ban on CentOS 7 and can tell me how to do it?




I tried to install fail2ban with yum install fail2ban and run it (there are no extra rules in iptables -L which seems odd according to what I found on the net).



As soon as I reboot the server I can't login as root or other user via ssh. The ports are not visible when scanning and of course I get this error when I try to connect:



ssh: connect to host XXX.XXX.XXX.XXX port 12321: Connection refused 


I changed the ssh port, but I also tried it with port 22 without luck.




I wonder if someone knows a solutions to this problem?



It has to be a problem with fail2ban because I didn't install anything else.






UPDATE
I can log in via ssh after reboot. But no html page is served. Output of iptables -L:





Chain INPUT (policy ACCEPT) target prot opt source
destination f2b-sshd tcp -- anywhere anywhere
multiport dports ssh ACCEPT all -- anywhere anywhere
ctstate RELATED,ESTABLISHED ACCEPT all -- anywhere
anywhere INPUT_direct all -- anywhere
anywhere INPUT_ZONES_SOURCE all -- anywhere
anywhere INPUT_ZONES all -- anywhere
anywhere ACCEPT icmp -- anywhere anywhere
REJECT all -- anywhere anywhere
reject-with icmp-host-prohibited



Chain FORWARD (policy ACCEPT) target prot opt source
destination ACCEPT all -- anywhere anywhere
ctstate RELATED,ESTABLISHED ACCEPT all -- anywhere
anywhere FORWARD_direct all -- anywhere
anywhere FORWARD_IN_ZONES_SOURCE all -- anywhere
anywhere FORWARD_IN_ZONES all -- anywhere
anywhere FORWARD_OUT_ZONES_SOURCE all -- anywhere
anywhere FORWARD_OUT_ZONES all -- anywhere
anywhere ACCEPT icmp -- anywhere anywhere
REJECT all -- anywhere anywhere
reject-with icmp-host-prohibited



Chain OUTPUT (policy ACCEPT) target prot opt source
destination OUTPUT_direct all -- anywhere
anywhere




Chain FORWARD_IN_ZONES (1 references) target prot opt source
destination FWDI_public all -- anywhere
anywhere [goto] FWDI_public all -- anywhere
anywhere [goto]



Chain FORWARD_IN_ZONES_SOURCE (1 references) target prot opt
source destination



Chain FORWARD_OUT_ZONES (1 references) target prot opt source
destination FWDO_public all -- anywhere
anywhere [goto] FWDO_public all -- anywhere
anywhere [goto]



Chain FORWARD_OUT_ZONES_SOURCE (1 references) target prot opt
source destination




Chain FORWARD_direct (1 references) target prot opt source
destination



Chain FWDI_public (2 references) target prot opt source
destination FWDI_public_log all -- anywhere
anywhere FWDI_public_deny all -- anywhere
anywhere FWDI_public_allow all -- anywhere
anywhere



Chain FWDI_public_allow (1 references) target prot opt source
destination



Chain FWDI_public_deny (1 references) target prot opt source
destination



Chain FWDI_public_log (1 references) target prot opt source
destination




Chain FWDO_public (2 references) target prot opt source
destination FWDO_public_log all -- anywhere
anywhere FWDO_public_deny all -- anywhere
anywhere FWDO_public_allow all -- anywhere
anywhere



Chain FWDO_public_allow (1 references) target prot opt source
destination



Chain FWDO_public_deny (1 references) target prot opt source
destination



Chain FWDO_public_log (1 references) target prot opt source
destination



Chain INPUT_ZONES (1 references) target prot opt source
destination IN_public all -- anywhere anywhere

[goto] IN_public all -- anywhere anywhere
[goto]



Chain INPUT_ZONES_SOURCE (1 references) target prot opt source
destination



Chain INPUT_direct (1 references) target prot opt source
destination



Chain IN_public (2 references) target prot opt source
destination IN_public_log all -- anywhere
anywhere IN_public_deny all -- anywhere
anywhere IN_public_allow all -- anywhere
anywhere



Chain IN_public_allow (1 references) target prot opt source
destination ACCEPT tcp -- anywhere anywhere
tcp dpt:ssh ctstate NEW




Chain IN_public_deny (1 references) target prot opt source
destination



Chain IN_public_log (1 references) target prot opt source
destination



Chain OUTPUT_direct (1 references) target prot opt source
destination



Chain f2b-sshd (1 references) target prot opt source
destination RETURN all -- anywhere anywhere


Comments

Popular posts from this blog

linux - iDRAC6 Virtual Media native library cannot be loaded

When attempting to mount Virtual Media on a iDRAC6 IP KVM session I get the following error: I'm using Ubuntu 9.04 and: $ javaws -version Java(TM) Web Start 1.6.0_16 $ uname -a Linux aud22419-linux 2.6.28-15-generic #51-Ubuntu SMP Mon Aug 31 13:39:06 UTC 2009 x86_64 GNU/Linux $ firefox -version Mozilla Firefox 3.0.14, Copyright (c) 1998 - 2009 mozilla.org On Windows + IE it (unsurprisingly) works. I've just gotten off the phone with the Dell tech support and I was told it is known to work on Linux + Firefox, albeit Ubuntu is not supported (by Dell, that is). Has anyone out there managed to mount virtual media in the same scenario?

hp proliant - Smart Array P822 with HBA Mode?

We get an HP DL360 G8 with an Smart Array P822 controller. On that controller will come a HP StorageWorks D2700 . Does anybody know, that it is possible to run the Smart Array P822 in HBA mode? I found only information about the P410i, who can run HBA. If this is not supported, what you think about the LSI 9207-8e controller? Will this fit good in that setup? The Hardware we get is used but all original from HP. The StorageWorks has 25 x 900 GB SAS 10K disks. Because the disks are not new I would like to use only 22 for raid6, and the rest for spare (I need to see if the disk count is optimal or not for zfs). It would be nice if I'm not stick to SAS in future. As OS I would like to install debian stretch with zfs 0.71 as file system and software raid. I have see that hp has an page for debian to. I would like to use hba mode because it is recommend, that zfs know at most as possible about the disk, and I'm independent from the raid controller. For us zfs have many benefits,

apache 2.2 - Server Potentially Compromised -- c99madshell

So, low and behold, a legacy site we've been hosting for a client had a version of FCKEditor that allowed someone to upload the dreaded c99madshell exploit onto our web host. I'm not a big security buff -- frankly I'm just a dev currently responsible for S/A duties due to a loss of personnel. Accordingly, I'd love any help you server-faulters could provide in assessing the damage from the exploit. To give you a bit of information: The file was uploaded into a directory within the webroot, "/_img/fck_uploads/File/". The Apache user and group are restricted such that they can't log in and don't have permissions outside of the directory from which we serve sites. All the files had 770 permissions (user rwx, group rwx, other none) -- something I wanted to fix but was told to hold off on as it wasn't "high priority" (hopefully this changes that). So it seems the hackers could've easily executed the script. Now I wasn't able