Good idea. Just tried that. No rules are active after I stop Fail2ban: Chain INPUT (policy ACCEPT) target prot opt source...
No, those numbers do not belong to host from where I test. When I stop the bastille/ISPConfig firewall the Fail2Ban rules are still active, yet at...
I do have all the ports opened in the Firewall section of ISPConfig. However, when I check the activate button (or run the bastille start command...
You're right. My apologices. I was searching the forum for posts where my issue was described, so I ended up at this years old thread. This is the...
I'm having the same issue. Were you able to resolve it? How?
Server C: Machine is NOT accessible after bastille is activated Chain INPUT (policy DROP 0 packets, 0 bytes) pkts bytes target prot opt in...
Server B: Machine is NOT accessible after bastille is activated Chain INPUT (policy DROP 0 packets, 0 bytes) pkts bytes target prot opt in...
Server A: Machine IS accessible after bastille is activated Chain INPUT (policy DROP 0 packets, 0 bytes) pkts bytes target prot opt in...
I have 3 servers running CentOS 7.9. I never activated the ISPConfig built-in firewall, but decided to do so after the latest ISPConfig upgrade to...
So I messed up by installing acme.sh when having Certbot already setup on my CentOS 7.9 server running ISPConfig 3.2.6. I have since then read up...
You are right. I used the link ispconfig.org/ispconfig/ispconfig3/repository/archive.tar.gz?ref=stable-3.1 to download ISPConfig 3.1 (which I...
I have found two issues with the latest install of ISPConfig 3.1 and the upgrade to 3.1.15p3 when installing on CentOS 7.8.2003. I used the stable...
Separate names with a comma.
