[GH-ISSUE #1160] 502 Gateway error HTTPS SSL: error:1408F10B:SSL wrong version #953

Closed
opened 2026-02-26 06:35:11 +03:00 by kerem · 6 comments
Owner

Originally created by @frisodubach on GitHub (Jun 7, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1160

I get a 502 Gateway error no matter what, when using https proxy host for Nextcloud and Ghost, using DNS provider Cloudflare.

Nginx Proxy Manager Version
2.8.1

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'Proxy Hosts'
  2. Click on 'Edit'
  3. Change scheme to 'https'
  4. See error 502 bad gateway

Operating System

Docker (Raspberry PiOS)

Additional context

Everything works fine when using HTTP, but when I switch to HTTPS it stop working and throwing a 502 Gateway. I've tried it with pretty much every setting, and no success. I've also tried turning off TLS 1.3 on Cloudflare, and disabling 'Force HTTPS' but both were not succesful. The problem seems to be on the Proxy host side. I found the SSL error in /data/logs/error.log

Originally created by @frisodubach on GitHub (Jun 7, 2021). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1160 <!-- **Describe the bug** <!-- A clear and concise description of what the bug is. --> I get a 502 Gateway error no matter what, when using https proxy host for Nextcloud and Ghost, using DNS provider Cloudflare. **Nginx Proxy Manager Version** 2.8.1 **To Reproduce** Steps to reproduce the behavior: 1. Go to 'Proxy Hosts' 2. Click on 'Edit' 3. Change scheme to 'https' 4. See error 502 bad gateway **Operating System** <!-- Please specify if using a Rpi, Mac, orchestration tool or any other setups that might affect the reproduction of this error. --> Docker (Raspberry PiOS) **Additional context** <!-- Add any other context about the problem here, docker version, browser version, logs if applicable to the problem. Too much info is better than too little. --> Everything works fine when using HTTP, but when I switch to HTTPS it stop working and throwing a 502 Gateway. I've tried it with pretty much every setting, and no success. I've also tried turning off TLS 1.3 on Cloudflare, and disabling 'Force HTTPS' but both were not succesful. The problem seems to be on the Proxy host side. I found the SSL error in /data/logs/error.log
kerem 2026-02-26 06:35:11 +03:00
  • closed this issue
  • added the
    stale
    bug
    labels
Author
Owner

@TheCatster commented on GitHub (Jul 5, 2021):

I have the same exact issue, with the same error (only difference being I run NPM in docker on Debian x86_64.) Did you ever find a solution to this?

<!-- gh-comment-id:874115449 --> @TheCatster commented on GitHub (Jul 5, 2021): I have the same exact issue, with the same error (only difference being I run NPM in docker on Debian x86_64.) Did you ever find a solution to this?
Author
Owner

@frisodubach commented on GitHub (Jul 6, 2021):

No sadly not. I haven't had time to work on figuring out the issue. Good to hear that it's not an issue with just my architecture.
I run NPM in docker too btw.

<!-- gh-comment-id:874822138 --> @frisodubach commented on GitHub (Jul 6, 2021): No sadly not. I haven't had time to work on figuring out the issue. Good to hear that it's not an issue with just my architecture. I run NPM in docker too btw.
Author
Owner

@TheCatster commented on GitHub (Jul 6, 2021):

Yeah, some of the services I'm running are mission critical, so I just resorted to switching to Caddy. This was a fun project to play with.

<!-- gh-comment-id:874889669 --> @TheCatster commented on GitHub (Jul 6, 2021): Yeah, some of the services I'm running are mission critical, so I just resorted to switching to Caddy. This was a fun project to play with.
Author
Owner

@inthebrilliantblue commented on GitHub (Aug 31, 2022):

So Im thinking this issue is being caused by SNI. If you are going -> nginxproxymanager HTTPS -> internal server HTTPS with SNI not required, it works. But if you are requiring SNI (such as on IIS), you will get the 502 error.

<!-- gh-comment-id:1233210233 --> @inthebrilliantblue commented on GitHub (Aug 31, 2022): So Im thinking this issue is being caused by SNI. If you are going -> nginxproxymanager HTTPS -> internal server HTTPS with SNI not required, it works. But if you are requiring SNI (such as on IIS), you will get the 502 error.
Author
Owner

@github-actions[bot] commented on GitHub (Mar 10, 2024):

Issue is now considered stale. If you want to keep it open, please comment 👍

<!-- gh-comment-id:1987039067 --> @github-actions[bot] commented on GitHub (Mar 10, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:
Author
Owner

@github-actions[bot] commented on GitHub (Apr 22, 2025):

Issue was closed due to inactivity.

<!-- gh-comment-id:2819877937 --> @github-actions[bot] commented on GitHub (Apr 22, 2025): Issue was closed due to inactivity.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nginx-proxy-manager-NginxProxyManager#953
No description provided.