question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

SSL issue / port appended after upgrade to 2.9.14

See original GitHub issue

Hello incredible NPM Team !

Checklist

  • Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
    • Yes
  • Are you sure you’re not using someone else’s docker image?
    • Yes
  • Have you searched for similar issues (both open and closed)?
    • Yes

Describe the bug After the update to 2.9.14 some proxy hosts are not working any more. It seems that NPM doesn’t do correctly the reverse proxy as i see in the browser address that he tries to access the internal port. Reverting to the previous release fix the issue.

Nginx Proxy Manager Version 2.9.14

To Reproduce Steps to reproduce the behavior:

  1. Create a Proxy-Host with Linuxserver.io/Heimdall behind.
  2. Apply HTTPS and Force HTTPS
  3. Try to access the site: Browser reports bad SSL (SSL_ERROR_RX_RECORD_TOO_LONG) or in the best case the page appears but without any CSS Style

FYI: My NPM is behind Cloudflare DNS

Expected behavior Site should appear correctly like before

Operating System Docker Image on Debian 11.2

Reverting to 2.9.13 solves the issue. I’m not an expert with nginx. Tried to recreate a simple Proxy-Host from scratch but same issue. Hope this will help someone.

Thanks in advance for your help

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Reactions:23
  • Comments:24 (1 by maintainers)

github_iconTop GitHub Comments

3reactions
vilviccommented, Jan 4, 2022

We’re seeing the same issue and have had to rollback to a previous version. Redirects seem to pick up the internal port

2reactions
pseudomixcommented, Jan 6, 2022

Hi Chaptergy,

This did the trick!

Removing:

proxy_set_header X-Forwarded-Host   $host;
proxy_set_header X-Forwarded-Port   $port;

from /etc/nginx/conf.d/include/proxy.conf worked for me.

In the meantime i have mount this file outside of the image to don’t loose the change in case of recreating the container. Feel free to ask me other test.

Thanks

Read more comments on GitHub >

github_iconTop Results From Across the Web

SSL issue / port appended after upgrade to 2.9.14 #1717
It seems that NPM doesn't do correctly the reverse proxy as i see in the browser address that he tries to access the...
Read more >
SSL/TLS communication problems after you install KB 931125
This article provides a solution to SSL/TLS communication problems that occur after you install KB 931125. Applies to: Windows Server 2008 ...
Read more >
VMware ESXi 7.0 Update 3f Release Notes
This issue is resolved in this release. PR 2945707: vSphere vMotion operations fail after upgrade to ESXi 7.x for environments configured with ...
Read more >
VMware Tanzu Application Service for VMs v2.9 Release Notes
To resolve this issue, follow the steps in the related known issue of the TAS for VMs release notes before or after upgrading...
Read more >
FTP and SSL/TLS - ProFTPD
The most common causes of these problems are: a) overly restrictive TLSCipherSuite configuration, or b) missing server certificate (i.e. TLSRSACertificateFile , ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found