Site does not work on PHP-FPM on Plesk server: 503 service unavailable

Follow

Comments

11 comments

  • Avatar
    Cornelia Mühlich

    I had this issue and solved it like it is discribed.

    The question is now: How did that happen and how to prevent it? As I logged into the plesk panel it showed me that several packages were updated. Could that have been the reason?

    1
    Comment actions Permalink
  • Avatar
    Alexandr Redikultsev

    Hi @Cornelia Mühlich.

    Maybe there was a hung PHP process that was terminated by the actions mentioned in the article.

    0
    Comment actions Permalink
  • Avatar
    Cornelia Mühlich

    Possible. But in that case I can't prevent it to happen again... Next time it happens I'll check for that. Thank you (:

    0
    Comment actions Permalink
  • Avatar
    Cfaessler

    First Resolution doesn't work for us (Onyx Plesk 17.5 - Debian 8).

    Second Resolution via SSH is a bit an overkill.
    When there are many domains on a server this will take a while.
    Is there any possibility to use this only for one domain?

    0
    Comment actions Permalink
  • Avatar
    Artyom Baranov

    @Cfaessler,

    Hello! I see that you have already submitted a request to support in regards to your questions.

    I believe they will find a solution soon.

    0
    Comment actions Permalink
  • Avatar
    Artyom Baranov

    @Cirrus Tecnologia,

    Hello! No, the issue described in this article is caused by the corrupted or missing configuration file while the issue from the mentioned article is caused by PHP 7.3 bugs.

    0
    Comment actions Permalink
  • Avatar
    spanovic

    Got this same issue the moment after Plesk Migrator finished working. I had one website transfered from one server to another, and that migration caousd this symthoms and it took 30% of my websites down. Any update on making sure that this does not happen?

     

    0
    Comment actions Permalink
  • Avatar
    Alexandr Nikolaenko

    Hello @spanovic,

    Migration is a quite complex process and there are might be various causes of occurred behaviour. Most probably PHP re-configuration process was interrupted due to some reason. However, a thorough investigation anyway is required to define the root cause.
    You can submit a ticket for us or use a server-wide workaround from the article.

    0
    Comment actions Permalink
  • Avatar
    Christopher Scott (Edited )

    I just experienced this problem when adjusting modsecurity rules. This is the steps to reproduce

     

    I use the Atomicorp Advanced Ruleset purchased through plesk

    PHP-FPM 7.2

    I have some rules disabled in a domains Additional Apache Directives (as per this article https://support.plesk.com/hc/en-us/articles/115002531753-How-to-disable-a-single-ModSecurity-rule-for-a-website-in-Plesk

    I then tried to disable an extra rule for the same domain by adding it to Modsecurity settings (as per this article https://support.plesk.com/hc/en-us/articles/115002531753-How-to-disable-a-single-ModSecurity-rule-for-a-website-in-Plesk

     

    This caused this error, tested it several times, and it causes this error everytime. To workaround until it is fixed, I have removed the rule I wished to disable from ModSecurity settings, and added it to the list in the Additional Apache Directives.

    No issues. I haven't tested to determine if it's having different rules disabled by both methods at the same time, or a fault just with the application of the modsecurity settings

     

    I hope this is helpful

    0
    Comment actions Permalink
  • Avatar
    Denis Bykov

    @Christopher Scott

    This behavior seems to be unrelated both to the current and the referred articles.
    I would suggest contacting regular Plesk support to investigate this behavior precisely.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request