ModSecurity failed to update rule set: modsecurity_ctl failed: HTTP Error 403: Forbidden

Follow

Comments

7 comments

  • Avatar
    Daniel Hesse

    Fixed ?

  • Avatar
    Bulat Tsydenov

    Hi Daniel, no it is not fixed yet. Did the workaround help?

  • Avatar
    Pera Burek

    This workaround doesn't work with 

    Plesk Onyx 
    Version 17.8.11 Update #13, last updated on July 7, 2018 04:07 AM

     

  • Avatar
    Alexandr Redikultsev

    Hi @Pera Burek!

    The issue was caused by the outdated links for downloading and should be resolved already in Plesk Onyx 17.8.

    I suggest trying to troubleshoot the issue by checking whether or not it is possible to reach updates.atomicorp.com from the server with curl command:

    # curl https://updates.atomicorp.com/installers/

    It should return the actual page.

  • Avatar
    Cfaessler

    Having this issue on "Version 17.5.3 Update #53"
    Should I open a request?

  • Avatar
    Lukas Erhart (Edited )

    It is not resolved with 17.8.

    Got this error today on 2 of 3 vhosts which all have Plesk 17.8.11 Update #13 installed.

    The one which didn't had the error uses Ubuntu 14.04.5 LTS, the other two use Ubuntu 16.04.4 LTS.

    All are hosted by the same provider.


    The curl command returns on all vhosts a HTML-Page so it's not blocked by anything.

    The plesk_atomic.py already had the above mentioned lines in it.

    I've deleted the file plesk_atomic.pyc and reenabled the ruleset (since the radio-button was already selected, I've only clicked save).
    This was only done on one vhost.
    The issue persisted till I've changed the ruleset to anything else and changed it back to the first list-entry.

    On the other vhost I only changed the ruleset to anything else and changed it back to the first list-entry without deleting the plesk_atomic.pyc and the issue is gone there too.

  • Avatar
    Alexandr Redikultsev

    Hi @Cfaessler!

    Yes, please submit a ticket to us regarding this issue.

     

    @Lukas Erhart, thank you very much for the feedback, the investigation is ongoing right now.

Please sign in to leave a comment.

Have more questions? Submit a request