starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-25 17:35:52 +03:00

[GH-ISSUE #4500] Can't disabled well-known (letsencrypt) path protection #2884

New issue

Open

opened 2026-02-26 07:37:05 +03:00 by kerem · 4 comments

kerem commented

2026-02-26 07:37:05 +03:00

Owner

Originally created by @mrforsythexeter on GitHub (Apr 25, 2025).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4500

Checklist

Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker 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
I have a service which lives behind NPM, it needs to be able to request its own SSL certificate as its used for other purposes than simply web access. It's a commercial product I can't change. By default NPM seems to include './etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf' which returns a 404 for a request to the /well-known/ URL space, as a protection system. However, this prevents the underlying system from using letsencrypt to make the request.

I tried to use the advanced section to change this location, however nginx emits a warning about duplicate locations and doesn't work.

I don't see any way to stop this default behaviour or get around it using NPM.

Nginx Proxy Manager Version
v2.12.3

To Reproduce
Steps to reproduce the behavior:

setup a small nginx server with the URL path on port 80
add the proxy host to NPM
try and request the file (URL)

Expected behavior
A checkbox to turn off letsencrypt protection for that proxy host (stops the inclusion of this file)

Operating System

Additional context

Originally created by @mrforsythexeter on GitHub (Apr 25, 2025). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4500 **Checklist** - Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker 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** I have a service which lives behind NPM, it needs to be able to request its own SSL certificate as its used for other purposes than simply web access. It's a commercial product I can't change. By default NPM seems to include './etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf' which returns a 404 for a request to the /well-known/ URL space, as a protection system. However, this prevents the underlying system from using letsencrypt to make the request. I tried to use the advanced section to change this location, however nginx emits a warning about duplicate locations and doesn't work. I don't see any way to stop this default behaviour or get around it using NPM. **Nginx Proxy Manager Version** v2.12.3 **To Reproduce** Steps to reproduce the behavior: 1. setup a small nginx server with the URL path on port 80 2. add the proxy host to NPM 3. try and request the file (URL) **Expected behavior** A checkbox to turn off letsencrypt protection for that proxy host (stops the inclusion of this file) **Operating System**  **Additional context**

kerem added the

stale

bug

labels

2026-02-26 07:37:05 +03:00

kerem commented

2026-02-26 07:37:06 +03:00

Author

Owner

@woliver99 commented on GitHub (Jul 28, 2025):

yeah i just encountered this problem, i just did a shitty fix by going to the actual proxy config stored on my server and commenting it out and adding the /.well-known/acme-challenge/ location to proxy port 80 of the server

@woliver99 commented on GitHub (Jul 28, 2025): yeah i just encountered this problem, i just did a shitty fix by going to the actual proxy config stored on my server and commenting it out and adding the /.well-known/acme-challenge/ location to proxy port 80 of the server

kerem commented

2026-02-26 07:37:06 +03:00

Author

Owner

@mrforsythexeter commented on GitHub (Jul 29, 2025):

I think one thing that NPM could do here (in my case is).. If you are using DNS-01 challenge for the SSL, then don't add this to proxy host configuration. As this is only required for HTTP-01 challenge.

The other idea I would support here, would be to only apply this location when its just about to make a request to lets encrypt, I know the host would be "affected" by this, however nginx -S reload "should" be fast enough and handle this without issue.

@mrforsythexeter commented on GitHub (Jul 29, 2025): I think one thing that NPM could do here (in my case is).. If you are using DNS-01 challenge for the SSL, then don't add this to proxy host configuration. As this is only required for HTTP-01 challenge. The other idea I would support here, would be to only apply this location when its just about to make a request to lets encrypt, I know the host would be "affected" by this, however nginx -S reload "should" be fast enough and handle this without issue.

kerem commented

2026-02-26 07:37:06 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Feb 3, 2026):

Issue is now considered stale. If you want to keep it open, please comment 👍

@github-actions[bot] commented on GitHub (Feb 3, 2026): Issue is now considered stale. If you want to keep it open, please comment :+1:

kerem commented

2026-02-26 07:37:06 +03:00

Author

Owner

@mrforsythexeter commented on GitHub (Feb 3, 2026):

This is still an issue, and a "close" is not a solve.

@mrforsythexeter commented on GitHub (Feb 3, 2026): This is still an issue, and a "close" is not a solve.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/nginx-proxy-manager-NginxProxyManager#2884

No description provided.

Rows
Columns