Facebook
TwitterHi,
I've searched around the board and can't seem to find an answer/issue tracked with this bug - and just wanna post the "work-around" solution to this problem -as I can reproduce it with every install I make with the Ubuntu 14.04.2 LTE x86 install I make.
Server installs fine, I upgrade Ubuntu dist to use PHP-5.6.x, Plesk installs fine and run fine and use PHP.5.6.x but every single time I enable fail2ban via Plesk and restart for the first time. The ngnix/Apache server stop to answer on the normal port 80.
Took some testing and reinstallations - but finally I found that a simple:
Seems to do the trick and make Nginx/Apache run normally again and make the fail2ban filters work as expected.
Think that a configuration rebuild should be done by Plesk when fail2ban is enabled
Kind regards
Geert Lund
www.GLD.dk
I've searched around the board and can't seem to find an answer/issue tracked with this bug - and just wanna post the "work-around" solution to this problem -as I can reproduce it with every install I make with the Ubuntu 14.04.2 LTE x86 install I make.
Server installs fine, I upgrade Ubuntu dist to use PHP-5.6.x, Plesk installs fine and run fine and use PHP.5.6.x but every single time I enable fail2ban via Plesk and restart for the first time. The ngnix/Apache server stop to answer on the normal port 80.
Took some testing and reinstallations - but finally I found that a simple:
Code:
/usr/local/psa/admin/sbin/httpdmng --reconfigure-serverSeems to do the trick and make Nginx/Apache run normally again and make the fail2ban filters work as expected.
Think that a configuration rebuild should be done by Plesk when fail2ban is enabled
Kind regards
Geert Lund
www.GLD.dk
