• 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!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    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. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

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