NginxProxyManager / NginxProxyManager/nginx-proxy-manager
NPM not autorenewing certs
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 34.2k
- Forks
- 3.9k
- Avg merge
- 21h 12m
- Merged PRs (30d)
- 20
Description
Checklist
- Have you pulled and found the error with
jc21/nginx-proxy-manager:latestdocker 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
Auto renew is failing and not running
Nginx Proxy Manager Version
2.9.15
To Reproduce
Steps to reproduce the behavior:
Certs do not auto renew once they get close to expiry
Expected behavior
Certs renew automatically
Screenshots
Operating System
Docker Swarm
Additional context
Renewing SSL certs close to expiry...
nginxproxy_app.1.mgfk9romsudb@Ramiel | [2/15/2022] [4:54:15 AM] [SSL ] › ✖ error Error: Command failed: certbot renew --non-interactive --quiet --config "/etc/letsencrypt.ini" --preferred-challenges "dns,http" --disable-hook-validation
nginxproxy_app.1.mgfk9romsudb@Ramiel | Renewal configuration file /etc/letsencrypt/renewal/npm-1.conf is broken.
nginxproxy_app.1.mgfk9romsudb@Ramiel | The error was: expected /etc/letsencrypt/live/npm-1/cert.pem to be a symlink
nginxproxy_app.1.mgfk9romsudb@Ramiel | Skipping.
nginxproxy_app.1.mgfk9romsudb@Ramiel | Renewal configuration file /etc/letsencrypt/renewal/npm-3.conf is broken.
nginxproxy_app.1.mgfk9romsudb@Ramiel | The error was: expected /etc/letsencrypt/live/npm-3/cert.pem to be a symlink
nginxproxy_app.1.mgfk9romsudb@Ramiel | Skipping.
nginxproxy_app.1.mgfk9romsudb@Ramiel | Renewal configuration file /etc/letsencrypt/renewal/npm-4.conf is broken.
Errors above
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 by reproducing certificate renewal with the jc21/nginx-proxy-manager:latest Docker image on Docker Swarm, then inspect the certbot renewal output and the /etc/letsencrypt/renewal/npm-*.conf files mentioned in the report. Done means certificates renew automatically without the broken renewal configuration or symlink errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, nginx, typescript
- Domain
- devops, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100