NginxProxyManager / NginxProxyManager/nginx-proxy-manager
acme-challenge
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 34.2k
- Forks
- 3.9k
- Avg merge
- 21h 12m
- Merged PRs (30d)
- 20
Description
On the server, use your own path to obtain the SSL LE.
The problem is that
many people need to obtain certificates themselves
but NPM intercepts the path /.well-known/acme-challenge/
I suggest using a custom path for NPM, for example /.well-known/npm-acme-challenge/
To obtain certificates on end servers, I use this approach and enable SSL none
location /.well-known/acme-challenge/ {
proxy_set_header Host $host;
proxy_set_header X-Forwarded-Scheme $scheme;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header X-Forwarded-For $remote_addr;
proxy_set_header X-Real-IP $remote_addr;
proxy_pass http://192.168.10.64:80;
}
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 tracing how Nginx Proxy Manager handles the /.well-known/acme-challenge/ path and how proxy-host SSL settings affect it. Define where a custom ACME challenge path would be configured and verify that requests can still reach an end server for Let's Encrypt issuance without disrupting existing proxy behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nginx
- Domain
- networking, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100