On October 19, 2021, we have enabled 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.
If you had already registered your account at Plesk 360 (formerly known as My Plesk) please use one for login. Otherwise please re-register it using the same email address as your existing 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.

Various actions fail in Plesk with Fail2Ban installed after server reboot: Unable to open file /run/lock/files/, There is no directory /var/run/




  • Avatar
    Wolfgang Ketterer

    If you write fail2ban correctly, then it works as well. :-)

    At least the manual solution! The automatic creation via tmpfiles.d didn't work for me. No idea why. I put the following two lines in the root crontab


    @reboot mkdir -p /run/lock/files ; chown root:psaadm /run/lock/files ; chmod 0770 /run/lock/files
    @reboot mkdir -p /run/fail2ban ; chown root:root /run/fail2ban ; chmod 0755 /run/fail2ban
    Comment actions Permalink
  • Avatar
    Danil Dmitrienko

    Hello Wolfgang,

    Thank you for your notes. The article has been adjusted.

    The solution with /etc/tmpfiles.d/*.conf is for OS with  the Systemd support (CentOS 7, Ubuntu 16 and etc). Otherwise, your solution with the crontab might be a good alternative and useful for other pleskians, but note it was not tested by Plesk.

    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request