• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

Issue Random 502 Bad Gateway

Stuzzi

New Pleskian
Hello!

As of yesterday, all of my websites in Plesk version 18.0.31 are showing random 502 Bad Gateway. Sometimes I can load 3 pages before the message appears. Sometimes it shows up right when the page loads and disappears when I refresh the page. I had to take the site offline, but the problem can be seen here Domain Default page

Many thanks for your help!
Greetings Felix
 
Last edited by a moderator:
The reason is located with Apache, it is not responding to Nginx requests properly. There can my several causes. For example:
- Verify that your server's public IP address is whitelisted in Fail2Ban.
- Look into /var/www/vhosts/<domain name>/logs error log files to find out more why Apache is not responding
- Check your system resources and the status of the service, e.g.
Enough RAM?
# free
Enough disk space?
# df
Is the service up reliably or are there errors shown in the journal excerpt?
# service apache2 status
or
# service httpd status
 
Thank you very much for your response! Some of the things I actually had already done because of your advice in other threads. It turned out to be a hardware issue.

Again THANK YOU VERY MUCH! You really saved me already a couple of times ;-)
 
Back
Top