Cert Renewed but shows Error When tried to access server

[carnby77]

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?

[the1ts]

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.

[carnby77]

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.

[TheRealGramdalf]

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.

[github-actions]

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

[github-actions]

Issue was closed due to inactivity.