NginxProxyManager / NginxProxyManager/nginx-proxy-manager
404 not working for SSL Default
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?- No
- 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 have installed the docker image of the latest NPM. I have manually added a wildcard SSL certificate. I have configured NPM to use a custom 404 error page. I have not yet created any hosts.
When I browse using HTTP to NPM i.e. http://site.domain.com, I correctly see my 404 page.
When I browse using HTTPS to NPM i.e. https://site.domain.com, I do not see my 404 page but instead see 'This site can't be reached' and 'ERR_SSL_UNRECOGNIZED_NAME_ALERT'.
Is there something else I need to configure in order for the 404 to work for SSL also?
Nginx Proxy Manager Version
To Reproduce
Steps to reproduce the behavior:
- Go to settings, default site, edit, select custom and paste html
- Go to SSL certificate and add custom certificate.
- That is all, do nothing else
- Open browser and enter http address and will see 404 page
- Open browser and https address and will not see 404 but error ststed above.
Expected behavior
When browsing to a non existent HTTPS web address I see my 404 page.
Screenshots
Operating System
Docker Desktop on Windows Host
Additional context
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
Reproduce from Settings > Default Site with a custom 404 page and custom wildcard SSL certificate, then compare HTTP and HTTPS requests with no hosts configured. Check the Docker image's HTTPS handling for unmatched hostnames and determine whether the expected result is the custom 404 page rather than ERR_SSL_UNRECOGNIZED_NAME_ALERT.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, nginx
- Domain
- infrastructure, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100