Apache fails to start on a Plesk server: ModSecurity: failed to load IPs from: /etc/asl/whitelist Could not open ipmatch file "/etc/asl/whitelist": No such file or directory

Follow

Comments

13 comments

  • Avatar
    Unknown User

    Very bad bug! Many thanks for the workaround but this is causing a lot of unexpected downtime.

    0
    Comment actions Permalink
  • Avatar
    Michael Sasinacki

    Ahh Atomic... I'm using Atomic Advanced (bought from Plesk). I hope you resolve this issue quickly. Workaround works. Thanks.

    1
    Comment actions Permalink
  • Avatar
    Steve West

    In the future, I hope Plesk team can develop a method to do a configtest of mod_sec rules before they are applied on a Plesk server.

    0
    Comment actions Permalink
  • Avatar
    Anton Kuznetsov

    Hello Steve,

    The thing is, the error happens due to a missing file from Atomic installation and config file syntax is perfectly okay. So there is no way to pre-test it from the Plesk side.

    0
    Comment actions Permalink
  • Avatar
    Nicolas Labbe (Edited )

    Because of this bug, I've switched off Mod Security and now I can't turn it back on.. Even if I try to use Comodo.
    modsecurity_ctl failed: START httpd_modules_ctl --enable security2,unique_id apache_control_adapter[38496]: apache_action(restart): invoke_httpd_action failed, trying second time

    EDIT: I was able to enable it by running the CLI command provided in the article, and then putting modsec back on in plesk.

    0
    Comment actions Permalink
  • Avatar
    Donnie Weaver

    Will this page be updated once the bug is fixed?

    0
    Comment actions Permalink
  • Avatar
    Michael Sasinacki

    I was wondering the same thing. I broke one of my servers trying to find out if the problem is fixed. I applied Atomic Advanced Rule set, no errors. But then i discovered that the web server is not servig content correctly. In some instances i was getting a Apache default page.

    I ended up deinstalling modesecurity and disabling Reverse Proxy Server (nginx).

    1
    Comment actions Permalink
  • Avatar
    Donnie Weaver

    Some level of communication from Plesk and/or Atomic here would be great. I was told by Plesk support to follow this page for updates. It's concerning many days have passed with no information.

    0
    Comment actions Permalink
  • Avatar
    Julian Bonpland Mignaquy

    Donnie Weaver hi!, we have direct communication with Atomic internally. Once they fix the issue we will publish it in this article.

    1
    Comment actions Permalink
  • Avatar
    Filippo Casti

    I see this post is updated but I don't see any fix. News?

    0
    Comment actions Permalink
  • Avatar
    Unknown User

    Filippo Casti the supposed solution is "aum -u"

    0
    Comment actions Permalink
  • Avatar
    Filippo Casti

    I don't think so. I can lunch "aum -u" and the update goes fine but when I try to switch from "Comodo" to "Atomic Standard free" I have this error:
    "modsecurity_ctl failed: [Errno 2] No such file or directory: '/var/asl/bin/aum': '/var/asl/bin/aum"

    0
    Comment actions Permalink
  • Avatar
    Nicolas Labbe

    I was able to enable Atomic rule after running "aum -u" but the rules list is empty. Seems like it's still broken.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request