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