Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NPM not autorenewing certs #1856

Open
unixbird opened this issue Feb 15, 2022 · 4 comments
Open

NPM not autorenewing certs #1856

unixbird opened this issue Feb 15, 2022 · 4 comments
Labels

Comments

@unixbird
Copy link

Checklist

  • Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker 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

@unixbird unixbird added the bug label Feb 15, 2022
@v1-valux
Copy link

v1-valux commented Mar 20, 2022

I can confirm problems on my side with auto-renewal..
Also a completely new request (without dns-challenge) fails, too.
The log instead lists "dns" under --preferred-challenges "dns,http" - is this correct?

Getting the following error when trying to renew my certs manually:

[3/20/2022] [1:03:11 AM] [Express  ] › ⚠  warning   Command failed: certbot certonly --config "/etc/letsencrypt.ini" --cert-name "npm-13" --agree-tos --authenticator webroot --email "[email protected]" --preferred-challenges "dns,http" --domains "domain.tld"

Another instance of Certbot is already running.

EDIT:

I reverted to 2.9.15 which didn't work at first,
then I cleared my browser cache and suddenly manual renewal worked.

Don't quite know which one was the solution (at least for the manual renewal)..

@boehser-enkel
Copy link

Same problem for me @2.9.18

Copy link

Issue is now considered stale. If you want to keep it open, please comment 👍

@github-actions github-actions bot added the stale label Feb 24, 2024
@battletux
Copy link

battletux commented Dec 18, 2024

I was having this issue and tried the temp work around from #2881 but it was not working for me initially so I restarted the container and disabled the force SSL for it to start working.

@github-actions github-actions bot removed the stale label Feb 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants