Perhaps cerbot is continually being started by a background process on a loop due to some error that occurs, and thus there is always a lock when a certbot instance is called from the UI manually. I will even see multiple certbot processes in the ps menu and see different PIDs if I run multiple 'ps' commands in a row. What occurs is a new certbot process will immediately start. I have restarted my container numerous times and have attempted to kill existing certbot processes. If I attempt to renew a certificate or create a new certificate in the proxy host menu then I just get "Internal Error". It occurs when I attempt to create a new SSL cert in the SSL tab. NPM latest image (2.8.0) on Docker (QNAP container station).The certificate is renewed without error. › ✖ error Error: Command failed: /usr/bin/certbot renew -non-interactive -quiet -config "/etc/letsencrypt.ini" -preferred-challenges "dns,http" -disable-hook-validation
› ⚠ warning Command failed: /usr/bin/certbot renew -non-interactive -config "/etc/letsencrypt.ini" -cert-name "npm-3" -preferred-challenges "dns,http" -disable-hook-validationĪnother instance of Certbot is already running. › ℹ info Renewing Let'sEncrypt certificates for Cert #3: Click on 'Renew Now' for a specific certificate.I have some SSL certificates generated in NPM via Let's Encrypt that need to be renewed and I receive a message that 'Another instance of Certbot is already running.'.
0 kommentar(er)
