starred/nginx-proxy-manager-NginxProxyManager

Fork 0

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

[GH-ISSUE #2263] Cert Renewed but shows Error When tried to access server #1614

New issue

Closed

opened 2026-02-26 07:31:46 +03:00 by kerem · 5 comments

kerem commented

2026-02-26 07:31:46 +03:00

Owner

Originally created by @carnby77 on GitHub (Sep 13, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2263

Whenever there is a cert expiring , i renew it. But after renewing successfully, the reverse proxy gives connection not private error. When i click on proceed anyway, it leads to my router login page.
This only happens for duckdns subdomains.
I dont see any issues using dynu or no-ip dns.
Happens all whenever cert near expiration,

Is there a bug?

Originally created by @carnby77 on GitHub (Sep 13, 2022). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2263 Whenever there is a cert expiring , i renew it. But after renewing successfully, the reverse proxy gives connection not private error. When i click on proceed anyway, it leads to my router login page. This only happens for duckdns subdomains. I dont see any issues using dynu or no-ip dns. Happens all whenever cert near expiration, Is there a bug?

kerem

2026-02-26 07:31:46 +03:00

closed this issue
added the
stale

bug
labels

kerem commented

2026-02-26 07:31:47 +03:00

Author

Owner

@the1ts commented on GitHub (Sep 13, 2022):

I'm just not seeing how this behaviour could be linked to cert renewal or otherwise. The only way you would get your router login page is because of DNS/IP and/or port issues. I'm guessing that the router on port 80/443 can only be hit from the inside private IP range, not the external IP range, since nearly all routers only have the GUI running on the inside private IP. Check your DNS is my suggestion.

@the1ts commented on GitHub (Sep 13, 2022): I'm just not seeing how this behaviour could be linked to cert renewal or otherwise. The only way you would get your router login page is because of DNS/IP and/or port issues. I'm guessing that the router on port 80/443 can only be hit from the inside private IP range, not the external IP range, since nearly all routers only have the GUI running on the inside private IP. Check your DNS is my suggestion.

kerem commented

2026-02-26 07:31:47 +03:00

Author

Owner

@carnby77 commented on GitHub (Sep 14, 2022):

I'm just not seeing how this behaviour could be linked to cert renewal or otherwise. The only way you would get your router login page is because of DNS/IP and/or port issues. I'm guessing that the router on port 80/443 can only be hit from the inside private IP range, not the external IP range, since nearly all routers only have the GUI running on the inside private IP. Check your DNS is my suggestion.

duckdns started working after 6-7 hours of cert renewal. Oh well, i guess it is a duckdns issue.

@carnby77 commented on GitHub (Sep 14, 2022): > I'm just not seeing how this behaviour could be linked to cert renewal or otherwise. The only way you would get your router login page is because of DNS/IP and/or port issues. I'm guessing that the router on port 80/443 can only be hit from the inside private IP range, not the external IP range, since nearly all routers only have the GUI running on the inside private IP. Check your DNS is my suggestion. duckdns started working after 6-7 hours of cert renewal. Oh well, i guess it is a duckdns issue.

kerem commented

2026-02-26 07:31:47 +03:00

Author

Owner

@TheRealGramdalf commented on GitHub (Oct 6, 2022):

I had this issue as well. My router is running openwrt, and it was set to listen to 0.0.0.0 - all addresses. That included the public IP. So I changed that to it's local IP (192.168.1.1), and that fixed the issue.

Depending on your router, you may have an option similar to this. You need to disable access to the webui from the public IP, wherever that is (I know shaw routers have it somewhere at least)

In openwrt the config is in /etc/config/uhttpd.

@TheRealGramdalf commented on GitHub (Oct 6, 2022): I had this issue as well. My router is running openwrt, and it was set to listen to `0.0.0.0` - all addresses. That included the public IP. So I changed that to it's local IP (`192.168.1.1`), and that fixed the issue. Depending on your router, you may have an option similar to this. You need to disable access to the webui from the public IP, wherever that is (I know shaw routers have it somewhere at least) In openwrt the config is in `/etc/config/uhttpd`.

kerem commented

2026-02-26 07:31:47 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Feb 9, 2024):

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

@github-actions[bot] commented on GitHub (Feb 9, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:

kerem commented

2026-02-26 07:31:47 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Mar 26, 2025):

Issue was closed due to inactivity.

@github-actions[bot] commented on GitHub (Mar 26, 2025): Issue was closed due to inactivity.

kerem referenced this issue

2026-02-26 08:30:45 +03:00

[PR #1614] [MERGED] Feature: Add two new headers to proxy.conf #3466

kerem referenced this issue

2026-02-26 08:30:49 +03:00

[PR #1766] [MERGED] v2.9.15 #3484

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

No description provided.

Rows
Columns