NginxProxyManager / NginxProxyManager/nginx-proxy-manager
Add Certificate via http fails if "-" is into the FQDN
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?- Yes
- Are you sure you're not using someone else's docker image?
- Yes
- Have you searched for similar issues (both open and closed)?
- No
Describe the bug
I try to get over Let`s Encrypt Certificate for eg. aa-test.example.com. This fails and the Test Results is witten the fqdn aatest.example.com.
It looks that the "-" is missing. I use the same FQDN with Nginx V 2.9.18 and it works.
Nginx Proxy Manager Version
V2.13.3
To Reproduce
Steps to reproduce the behavior:
Try to get a Certificate with a FQDN include "-" eg. aa-test.example.com
Expected behavior
Get a Certificate with V2.9.18
Screenshots
Operating System
Docker
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
Start by reproducing the certificate request with the jc21/nginx-proxy-manager:latest Docker image and the FQDN aa-test.example.com, then compare the reported name with the working V2.9.18 behavior. Done means the certificate request succeeds and the hyphen remains present in the FQDN shown in the test results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, nginx
- Domain
- infrastructure, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100