502 Bad Gateway returned while using ngnix proxy to get to a website on CloudPanel - v2.2.0 #450

New Issue

MrUnknownDE · 2026-04-05T20:27:53+02:00

MrUnknownDE commented

2026-04-05 20:27:53 +02:00

Originally created by @warebytes on 12/30/2022

CloudPanel version(s) affected

2.2.0

Description

I have upgraded one of my CloudPanel instances from v2.0.4 version to v2.2.0 and started getting 502 Bad Gateway errors when I try to access a hosted website on the upgraded instance.
All domain requests go through an NGINX proxy first, then they are redirected to my CloudPanel instances.
All domain requests work properly when redirected to CloudPanel v2.0.4 instance.
All domain requests are rejected with code 502 Bad Gateway when redirected to CloudPanel v2.2.0.
Direct requests (without NGINIX Proxy redirection) on the CloudPanel v2.2.0 instance work correctly.
Could please provide a fix to this issue?
Thank you.

How to reproduce

Install NGINX Proxy or NGINX Proxy Manager on a server in the same network as your CloudPanel v2.2.0 instance.
Configure a [Proxy Host] with the DNS of the website hosted on CloudPanel Panel v2.2.0 and add an SSL Certificate - Redirection on port 443.
Configure your firewall to redirect all requests on port 443 and 80 to the NGINX Proxy Server.
Using a browser, go to the domain name of your website.
Browser will return code 502 Bad Gateway.

Possible Solution

No response

Additional Context

v2.0.4 does not have this issue. I still have an instance with the same configuration that is working properly.

*Originally created by @warebytes on 12/30/2022* ### CloudPanel version(s) affected 2.2.0 ### Description I have upgraded one of my CloudPanel instances from v2.0.4 version to v2.2.0 and started getting 502 Bad Gateway errors when I try to access a hosted website on the upgraded instance. All domain requests go through an NGINX proxy first, then they are redirected to my CloudPanel instances. All domain requests work properly when redirected to CloudPanel v2.0.4 instance. All domain requests are rejected with code 502 Bad Gateway when redirected to CloudPanel v2.2.0. Direct requests (without NGINIX Proxy redirection) on the CloudPanel v2.2.0 instance work correctly. Could please provide a fix to this issue? Thank you. ### How to reproduce - Install NGINX Proxy or NGINX Proxy Manager on a server in the same network as your CloudPanel v2.2.0 instance. - Configure a [Proxy Host] with the DNS of the website hosted on CloudPanel Panel v2.2.0 and add an SSL Certificate - Redirection on port 443. - Configure your firewall to redirect all requests on port 443 and 80 to the NGINX Proxy Server. - Using a browser, go to the domain name of your website. - Browser will return code 502 Bad Gateway. ### Possible Solution _No response_ ### Additional Context v2.0.4 does not have this issue. I still have an instance with the same configuration that is working properly.

MrUnknownDE closed this issue

2026-04-05 20:27:53 +02:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/cloudpanel-ce#450