Starting on October 19, 2021, we will enable single-sign-on for our Plesk Support Center to provide a seamless login/account experience. This implies that you’ll be able to use a single account across any of our web-facing properties.
To be prepared for this change and to avoid the need to register during your next ticket submission after the change, we encourage you to create an account here before October 19 using the same email address as your current Zendesk login (support account). It’s essential that you use the same email address on our support center to ensure that your tickets stay attached to the same account. You will continue to use ZenDesk authentication until we switch over to single-sign-on on October 19th.

Fail2Ban iptables rules can be erased sometimes by disabling Plesk Firewall




  • Avatar
    Julian Aubertin

    In my Opinion, the psa-firewall script needs to restart fail2ban when called, but only when fail2ban is active. This can be done by editing the /etcinit.d/psa-firewall skript like:

    after emergency=....


    fail2ban_restart () {
    if [ "active" == `/bin/systemctl is-active fail2ban.service` ] ; then
    echo "$SERVICE_NAME: fail2ban will restart now."
    systemctl restart fail2ban.service &
    echo "$SERVICE_NAME: fail2ban is not active and will not be restarted."

    fail2ban_restart checks if fail2ban is active and restarts ist when detected. You then need to call the function in the start, stop and restart section after the echo statements.

    In Ubuntu 16 fail2ban stores the bans in a DB so no ban will be lost. I assume it does also in other systems.

    Comment actions Permalink
  • Avatar
    Pavel Rozental

    Hello Julian,

    Thank you for provided information.

    I have passed it to our developers. They will consider this solution.

    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request