• Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is 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.

Issue 502 Bad Gateway nginx only with HTTPS

Richard18

Basic Pleskian
I'm in the middle of a manual migration from one server to another and I'm having problems getting sites running on HTTPS again.

The sites (mostly WordPress) run fine over HTTP with nginx, but not on HTTPS with nginx.

For example, I can access https://domain/index.php and the page will load but without CSS and images.

If I try and go to https://domain/somefolder/some.file I get a 502 Bad Gateway from nginx.

In the proxy_error.log I see:

2016/08/04 14:53:55 [error] 7183#0: *536 connect() failed (111: Connection refused) while connecting to upstream, client: xxx.xxx.xxx.xxx, server: xxx.xxx, request: "GET /somefolder/some.file HTTP/1.1", upstream: "https://xxx.xxx.xxx.xxx:7081/somefolder/some.file", host: "xxx.xxx", referrer: "xxx"

I'm fairly certain permissions are OK because the site is served correctly over HTTP, I just get these errors on HTTPS.

I've searched the forum and the plesk support sites and I can't quite find anything exactly like this.

Plesk 12.5.30 #42 Ubunutu 14.04 LTS - PHP is run as FPM application served by nginx
 
I've managed to fix the sites by changing an option in Websites & Domains > Apache & nginx Settings called "Serve static files directly by nginx", I've ticked it and it seems to have made it all work.

To be honest, I don't completely understand what I've done though or why I was getting the error, can anyone still explain it?
 
Back
Top