Certbot is already running

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is: no

I ran this command: I restored my server snapshot, and before the restore my Nginx proxy manager had already requested the certificates via Cloudflaer using *.yydy.link and yydy.link, but after I restored the previous server snapshot, I reused the Nginx proxy manager to send the certificate to the Let's Encrypt The following error occurs when applying for the certificates.

It produced this output:

log:Error: Command failed: certbot certonly --config "/etc/letsencrypt.ini" --work-dir "/tmp/letsencrypt-lib" --logs-dir "/tmp/letsencrypt-log" --cert-name "npm-45" --agree-tos --email "vip@ypcloud.space" --domains "*.yydy.link,yydy.link" --authenticator dns-cloudflare --dns-cloudflare-credentials "/etc/letsencrypt/credentials/credentials-45"
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-0_tp1hz3/log or re-run Certbot with -v for more details.

at ChildProcess.exithandler (node:child_process:402:12)
at ChildProcess.emit (node:events:513:28)
at maybeClose (node:internal/child_process:1100:16)
at Process.ChildProcess._handle.onexit (node:internal/child_process:304:5)

My web server is (include version): yydy.link

The operating system my web server runs on is (include version): Linux Young-Docker 6.2.0-25-generic #25-Ubuntu SMP PREEMPT_DYNAMIC Fri Jun 16 17:05:07 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

My hosting provider, if applicable, is:Local deployment; VMware

I can login to a root shell on my machine (yes or no, or I don't know): yes

I'm using a control panel to manage my site (no, or provide the name and version of the control panel): yes

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): Linux Young-Docker 6.2.0-25-generic #25-Ubuntu SMP PREEMPT_DYNAMIC Fri Jun 16 17:05:07 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

How do you revoke a previously duplicated certificate?

# Workaround

Revoking a perfectly fine certificate is almost never the answer and it certainly isn't for this situation. It isn't a "#workaround", it is not a solution.

That said, I have no idea how to debug nor fix this issue when Nginx Proxy Manager is being used.

Also, why answer "no" for the domain name question? That's kinda silly, no? It's not a yes or no question..

1 Like

his domain is yydy.link, he put that on server question but looks like it's firewalled, so he's using DNS challange over cloudflare.

there is another post next it about lockfile, check it too


This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.