NginxProxyManager / NginxProxyManager/nginx-proxy-manager
Failed to renew certificate npm-## with error: Some challenges have failed. / Let's Encrypt rennewval in v2.13.7
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 34.2k
- Forks
- 3.9k
- Avg merge
- 21h 12m
- Merged PRs (30d)
- 20
Description
Failed to renew certificate npm-## with error: Some challenges have failed.
All renewals failed. The following certificates could not be renewed:
/etc/letsencrypt/live/npm-##/fullchain.pem (failure)
1 renew failure(s), 0 parse failure(s)
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /data/logs/letsencrypt.log or re-run Certbot with -v for more details.
[7/2/2026] [3:02:03 PM] [SSL ] › ℹ info Renewing LetsEncrypt certificates for Cert #90
[7/2/2026] [3:02:03 PM] [SSL ] › ℹ info Command: certbot renew --force-renewal --config /etc/letsencrypt.ini --work-dir /tmp/letsencrypt-lib --logs-dir /data/logs --cert-name npm-90 --preferred-challenges http --no-random-sleep-on-renew --disable-hook-validation
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 with the renewal output and the Certbot command shown in the issue, then inspect /data/logs/letsencrypt.log and rerun Certbot with -v as suggested. Determine why the HTTP challenge fails for certificate npm-90; done means the certificate renews successfully without the reported challenge error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nginx
- Domain
- infrastructure, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100