addon-nginx-proxy-manager

addon-nginx-proxy-manager copied to clipboard

I noticed my certs weren't being updated. I tried manually doing so:

These are the logs:

[4/7/2025] [9:42:10 AM] [SSL      ] › ℹ  info      Let's Encrypt Renewal Timer initialized
[4/7/2025] [9:42:10 AM] [SSL      ] › ℹ  info      Renewing SSL certs close to expiry...
[4/7/2025] [9:42:10 AM] [IP Ranges] › ℹ  info      IP Ranges Renewal Timer initialized
[4/7/2025] [9:42:10 AM] [Global   ] › ℹ  info      Backend PID 228 listening on port 3000 ...
[4/7/2025] [9:42:10 AM] [SSL      ] › ℹ  info      Renewing Let'sEncrypt certificates for Cert #3: ha-ct.domain.tld
[4/7/2025] [9:42:10 AM] [SSL      ] › ℹ  info      Command: certbot renew --force-renewal --config "/etc/letsencrypt.ini" --work-dir "/tmp/letsencrypt-lib" --logs-dir "/tmp/letsencrypt-log" --cert-name "npm-3" --preferred-challenges "dns,http" --no-random-sleep-on-renew --disable-hook-validation 
[4/7/2025] [9:42:10 AM] [SSL      ] › ✖  error     Error: Command failed: certbot renew --non-interactive --quiet --config "/etc/letsencrypt.ini" --work-dir "/tmp/letsencrypt-lib" --logs-dir "/tmp/letsencrypt-log" --preferred-challenges "dns,http" --disable-hook-validation  
Another instance of Certbot is already running.
    at ChildProcess.exithandler (node:child_process:422:12)
    at ChildProcess.emit (node:events:517:28)
    at maybeClose (node:internal/child_process:1098:16)
    at ChildProcess._handle.onexit (node:internal/child_process:303:5)
[4/7/2025] [9:42:11 AM] [Express  ] › ⚠  warning   Command failed: certbot renew --force-renewal --config "/etc/letsencrypt.ini" --work-dir "/tmp/letsencrypt-lib" --logs-dir "/tmp/letsencrypt-log" --cert-name "npm-3" --preferred-challenges "dns,http" --no-random-sleep-on-renew --disable-hook-validation 
Another instance of Certbot is already running.
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /tmp/certbot-log-8_3jd8r2/log or re-run Certbot with -v for more details.

I tried rebooting the HA instance, still seeing the same error about certbot already running. Any tips?