NginxProxyManager / NginxProxyManager/nginx-proxy-manager
SSL Unrecognized Name Alert
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 34.2k
- Forks
- 3.9k
- Avg merge
- 21h 12m
- Merged PRs (30d)
- 20
Description
Checklist
-
Have you pulled and found the error with
jc21/nginx-proxy-manager:latestdocker image? -
Are you sure you're not using someone else's docker image?
- No
-
Have you searched for similar issues (both open and closed)?
- Yes
Describe the bug
accessing the website through cloudflare on HTTPS returns an ERR_SSL_UNRECOGNIZED_NAME_ALERT error. I am using the dns challenge
Nginx Proxy Manager Version
2.12.1
To Reproduce
Steps to reproduce the behavior:
- Go to '...'
- Click on '....'
- Scroll down to '....'
- See error
Expected behavior
to see the default welcome wbepage
Screenshots
Operating System
TrueNAS
Additional context
latest truenas version, reinstalled, tried using the custom certificate, using port 8443 because 443 was acting wierd
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 reproducing the HTTPS access failure with Nginx Proxy Manager 2.12.1 using the latest Docker image on TrueNAS, Cloudflare, the DNS challenge, and port 8443. Check the reported ERR_SSL_UNRECOGNIZED_NAME_ALERT and compare it with the expected default welcome webpage; the issue needs a reliable reproduction and identified cause before a fix can be verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, nginx
- Domain
- devops, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100