starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-25 01:15:51 +03:00

[GH-ISSUE #4724] Nginx as local network proxy with Lets encrypt and Duckdns doesn't work after upgrade #3000

New issue

Closed

opened 2026-02-26 07:37:32 +03:00 by kerem · 1 comment

kerem commented

2026-02-26 07:37:32 +03:00

Owner

Originally created by @komzi2920 on GitHub (Aug 21, 2025).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4724

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

I'm not sure if this a bug.
I have updated my container which was configured with SSL and Duckdns to manage local hosts in my home network, but now I cannot access them via https protocol because I get now always 504 timeout error.
I have increased the timeout for the parameters listed below in nginx.conf file and now I'm getting a different error 502 Bad Gateway.
proxy_connect_timeout 300s;
proxy_send_timeout 300s;
proxy_read_timeout 300s;

Below is show the curl command output when trying to test https connection with my host xx @domain yy.duckdns.org

#####################################
curl -v https://xx.yy.duckdns.org

Trying 192.168.zz.tt:443...
Connected to xx.yy.duckdns.org (192.168.zz.tt) port 443 (#0)
ALPN: offers h2,http/1.1
TLSv1.3 (OUT), TLS handshake, Client hello (1):
CAfile: /etc/ssl/certs/ca-certificates.crt
CApath: /etc/ssl/certs
TLSv1.3 (IN), TLS handshake, Server hello (2):
TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
TLSv1.3 (IN), TLS handshake, Certificate (11):
TLSv1.3 (IN), TLS handshake, CERT verify (15):
TLSv1.3 (IN), TLS handshake, Finished (20):
TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
TLSv1.3 (OUT), TLS handshake, Finished (20):
SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
ALPN: server accepted http/1.1
Server certificate:
subject: CN=*.yy.duckdns.org
start date: Aug 21 19:58:32 2025 GMT
expire date: Nov 19 19:58:31 2025 GMT
subjectAltName: host "xx.yy.duckdns.org" matched cert's "*.yy.duckdns.org"
issuer: C=US; O=Let's Encrypt; CN=E8
SSL certificate verify ok.
using HTTP/1.1

GET / HTTP/1.1
Host: xx.yy.duckdns.org
User-Agent: curl/7.88.1
Accept: /

TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
old SSL session ID is stale, removing
< HTTP/1.1 502 Bad Gateway
< Server: openresty
< Date: Thu, 21 Aug 2025 21:33:27 GMT
< Content-Type: text/html
< Content-Length: 154
< Connection: keep-alive
<

502 Bad Gateway

openresty </html> * Connection #0 to host xx.yy.duckdns.org left intact 502 Bad Gateway502 Bad Gateway

Can you please help me how to resolve this ?

Thanks !

Nginx Proxy Manager Version

v2.12.6

To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior

Screenshots

Operating System

Additional context

Originally created by @komzi2920 on GitHub (Aug 21, 2025). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4724  **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**  I'm not sure if this a bug. I have updated my container which was configured with SSL and Duckdns to manage local hosts in my home network, but now I cannot access them via https protocol because I get now always 504 timeout error. I have increased the timeout for the parameters listed below in nginx.conf file and now I'm getting a different error 502 Bad Gateway. proxy_connect_timeout 300s; proxy_send_timeout 300s; proxy_read_timeout 300s; Below is show the curl command output when trying to test https connection with my host xx @domain yy.duckdns.org ##################################### curl -v https://xx.yy.duckdns.org * Trying 192.168.zz.tt:443... * Connected to xx.yy.duckdns.org (192.168.zz.tt) port 443 (#0) * ALPN: offers h2,http/1.1 * TLSv1.3 (OUT), TLS handshake, Client hello (1): * CAfile: /etc/ssl/certs/ca-certificates.crt * CApath: /etc/ssl/certs * TLSv1.3 (IN), TLS handshake, Server hello (2): * TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8): * TLSv1.3 (IN), TLS handshake, Certificate (11): * TLSv1.3 (IN), TLS handshake, CERT verify (15): * TLSv1.3 (IN), TLS handshake, Finished (20): * TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1): * TLSv1.3 (OUT), TLS handshake, Finished (20): * SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 * ALPN: server accepted http/1.1 * Server certificate: * subject: CN=*.yy.duckdns.org * start date: Aug 21 19:58:32 2025 GMT * expire date: Nov 19 19:58:31 2025 GMT * subjectAltName: host "xx.yy.duckdns.org" matched cert's "*.yy.duckdns.org" * issuer: C=US; O=Let's Encrypt; CN=E8 * SSL certificate verify ok. * using HTTP/1.1 > GET / HTTP/1.1 > Host: xx.yy.duckdns.org > User-Agent: curl/7.88.1 > Accept: */* > * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4): * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4): * old SSL session ID is stale, removing < HTTP/1.1 502 Bad Gateway < Server: openresty < Date: Thu, 21 Aug 2025 21:33:27 GMT < Content-Type: text/html < Content-Length: 154 < Connection: keep-alive < <html> <head><title>502 Bad Gateway</title></head> <body> <center><h1>502 Bad Gateway</h1></center> <hr><center>openresty</center> </body> </html> * Connection #0 to host xx.yy.duckdns.org left intact 502 Bad Gateway502 Bad Gateway Can you please help me how to resolve this ? Thanks ! **Nginx Proxy Manager Version**  v2.12.6 **To Reproduce** Steps to reproduce the behavior: 1. Go to '...' 2. Click on '....' 3. Scroll down to '....' 4. See error **Expected behavior**  **Screenshots**  **Operating System**  **Additional context**

kerem

2026-02-26 07:37:32 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-26 07:37:33 +03:00

Author

Owner

@komzi2920 commented on GitHub (Aug 26, 2025):

Hi guys,
I'm struggling to resolve his issue and now it looks that it is relevant to rootless docker network (driver slirp4netns) which for some reason has problems after upgrade. I still don't understand what was changed vs previous status, but I'm sure that this is the root cause of the issue I'm having. I'll try later with localhost or 10.0.2.2 ip (tap0 device created in user space) for all other containers running in the same host machine, but I don't know how to address the cases for other hosts in my LAN network. I'd appreciate if someone can guide me to resolve this unexpected situation. If no, I'm thinking to run docker as not rootless and that will open vulnerabilities or maybe I'll try podman. Thanks !

@komzi2920 commented on GitHub (Aug 26, 2025): Hi guys, I'm struggling to resolve his issue and now it looks that it is relevant to rootless docker network (driver slirp4netns) which for some reason has problems after upgrade. I still don't understand what was changed vs previous status, but I'm sure that this is the root cause of the issue I'm having. I'll try later with localhost or 10.0.2.2 ip (tap0 device created in user space) for all other containers running in the same host machine, but I don't know how to address the cases for other hosts in my LAN network. I'd appreciate if someone can guide me to resolve this unexpected situation. If no, I'm thinking to run docker as not rootless and that will open vulnerabilities or maybe I'll try podman. Thanks !

kerem referenced this issue

2026-02-26 08:31:24 +03:00

[PR #3000] [MERGED] Fix device or resource busy when patching IPv6 settings #3642

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#3000

No description provided.

Rows
Columns