NginxProxyManager / NginxProxyManager/nginx-proxy-manager
Let's Encrypt via HTTP changing domain name.
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)?
- Yes
Describe the bug
On the Let's Encrypt via HTTP page entering the domain test-domain.com then clicking test returns "testDomain.com: There is a server found at this domain but it returned an unexpected data" which is not the domain entered. Any domain tested with a - removes the - and capitalises the next letter.
Nginx Proxy Manager Version
v2.15.1
To Reproduce
Steps to reproduce the behavior:
- Go to 'Certificates'
- Click on 'Add Certificate'
- Select 'Let's Encrypt via HTTP'
- Enter domain with a hyphen
- Click 'Test'
- Test Results retuned with different domain which excludes the hyphen
Expected behavior
Test to be carried out on the entered domain
Screenshots
Operating System
Linux Debian 13.6
Additional context
Running in Portainer CE 2.45.0, Docker Version 29.8.0, Tested with Firefox, Safari & Chrome.
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 in the Certificates > Add Certificate > Let's Encrypt via HTTP flow and reproduce the test with a hyphenated domain such as test-domain.com. Trace the displayed test result back to the domain handling, then verify that the result preserves the entered spelling and still reports the expected validation outcome.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100