Open tuccler opened 2 years ago
Do you have a .local
directory under the directory you mapped to /config
? If yes, try to remove/rename it and restart the container.
Here the same error when I request a certificate with http challenge authentication. "Some challenges have failed." It seems the challenge cannot be read by ACME. If I put a test challenge file in the path /config/letsencrypt-acme-challenge/.well-known/acme-challenge I cannot open it with the browser.
If a add the following line to the advanced section of the proxy host
include conf.d/include/letsencrypt-acme-challenge.conf;
I can open the test file with a browser. So the network config seems ok. Still the same internal error when reqesting a certificate. Where is the challange path configured in the nginx configuration for the proxy host?
@dhover I am facing the same error: "some challenges have failed". I can renew the certificates manually if I (temporary) disable the "Force SSL" option. It seems that npm is redirecting the LE-Challenges to Port 443.
Could you solve the problem in the meantime?
Could you solve the problem in the meantime?
Yes but there was nothing wrong with npm. It was a strange problem with the router.
I get the "Internal Error" Message when I'm trying to renew my certificates. If i want to create a new certificate i get this:
I'm not using the dns challenge at all. Also Port 80 is recheable from the internet and forwarded to nginx-proxy-manager.
How can I repair this? All my certificates are going to expire soon.