[GH-ISSUE #5280] acme-challenge #3154

Open
opened 2026-02-26 07:37:58 +03:00 by kerem · 0 comments
Owner

Originally created by @CrashX on GitHub (Feb 6, 2026).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/5280

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;
}

Originally created by @CrashX on GitHub (Feb 6, 2026). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/5280 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; }
Sign in to join this conversation.
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#3154
No description provided.