• 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.

502 Bad Gateway nginx error

onlinesolutions

Basic Pleskian
Hi folks,

We are running Plesk 12 (latest version) on openSuse 13.1. The web server is nginx as a proxy in front of Apache. We are running into a 502 Bad Gateway nginx error when trying to send data from a simple form to a php script.

The log shows: upstream prematurely closed connection while reading response header from upstream

It seems that Plesk does not configure nginx properly as some pages, especially pages that are accessed via https have broken headers. The headers of a page that is displaying

HTTP/1.1 400 Bad Request =>
Server => nginx
Date => Sat, 26 Jul 2014 09:53:13 GMT
Content-Type => text/html
Content-Length => 166
Connection => close

Any hint is highly appreciated.

Best Regards

Online Solutions
 
A lot of possible reasons of this error are described in KB articles. Have you tried to find solution there with KB search engine and "502 Bad Gateway nginx" phrase?
 
A lot of possible reasons of this error are described in KB articles. Have you tried to find solution there with KB search engine and "502 Bad Gateway nginx" phrase?
Thanks for your reply. Yes, we spend hours researching the forum and other resources. We assume that the basics are covered by the configuration of Plesk.

Any clues and hints are appreciated.
 
Back
Top