NginxProxyManager / NginxProxyManager/nginx-proxy-manager
SSL works locally but shows “Not Secure” and redirects to router login when accessed from another network
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 34.2k
- Forks
- 3.9k
- Avg merge
- 21h 12m
- Merged PRs (30d)
- 20
Description
I run this in my local environment and made the port public using router port forwarding. I bound a domain to my router’s public IP and mapped it to my local port with npm, then applied Let’s Encrypt SSL. It works fine locally, but from other networks it’s not secure and redirects to my router login page.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by checking the router port-forwarding entry, the public DNS mapping, and the Nginx Proxy Manager host and SSL settings described in the report. Done means external requests reach the intended proxy host and present its valid certificate instead of showing the router login page.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nginx
- Domain
- infrastructure, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100