• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

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