A website is not accessible with "Nginx 504 Gateway Time-out"

Follow

Comments

9 comments

  • Avatar
    iamkingsleyf

    now is 502 error, plesk have started again

  • Avatar
    Pavel Mikhaylov (Edited )

    Hello iamkingsleyf,

    Do you experience the issue with 502 error at the moment?

    If you do, please let us know, what are other symptoms of the issue? What is in the subscription log files?

    I would also like to recommend contacting our support: https://www.plesk.com/contact-support

  • Avatar
    iamkingsleyf

    Yes i do but 504 error all 21 domains

  • Avatar
    Bulat Tsydenov

    @iamkingsleyf, the assistance with this issue was provided to you in scope of support ticket. If you need further assistance, please reply to the ticket.

  • Avatar
    yoyoy

    hello

    if you experience problems after modifying nginx.conf add the line proxy_connect_timeout 1200s;

    it could be useful ;)

  • Avatar
    Ivan Postnikov

    @yoyoy, yes, this is mentioned in step 1 of resolution.

  • Avatar
    Glenn

    I would also suggest limiting search time period so you're not searching logs months or years old:

    grep -R "upstream timed out" /var/www/vhosts/*/logs/ | grep "2018/10/3*" | wc -l &

    For example. 

  • Avatar
    Ivan Postnikov

    Hello @Glenn,

    Thank you for the hint, this command modification may be useful for other Pleskians.

    However, the command in symptom does not require modification in accordance with the present date and is more universal.

  • Avatar
    Glenn

    Hi Ivan,

    When I ran the command without a date limit, the result was 12000+ and according to my tech, was parsing logs more than a year old. It's was an insanely high number.

    When we ran it with date limit I got a more reasonable and realistic number of approx. 1100 and adjusted fcgi to 1200s. 

    Thanks for feedback.

     

Please sign in to leave a comment.

Have more questions? Submit a request