• The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Question Plesk Onyx - How to disable Fail2ban Service in Rescue Mode on Centos 7

AlexL777

New Pleskian
Hello Community and Developers,

I rarely turn to you, but then there are always powerful problems. From one hour to the other Plesk has closed all ports, probably because of incorrectly registered jails for the ports like 22, 80 and more.

Now I have logged in through my webhosting in the console via SSH in Rescue Mode and try to disable Fail2ban.

Unfortunately, normal Centos 7/Linux Commandos do not work in Rescue Mode. Is there a way to start MariaDB Service and disable Fail2ban in rescue mode?

When I work with "nmap" command, I can see well that port 80 is closed. Apparently almost all server ports are closed. Maybe a hacker attack took place, so the server blocked all Internet traffic.

How do I get out of this mess or can you help me?

I use Plesk Onyx, Centos 7.4 and MariaDB 10.x or also Fail2ban from Plesk.

Thanks in Advance.
 
Chmod iptables to 000 while in rescue, and then reboot back to normal. It will fail to start essentially resolving the issue. Should be self explanatory at this point :)
 
Back
Top