Certbot: Another instance of Certbot is already running
A previous certbot process (or cron/systemd timer) holds the lock file, so a new run refuses to start.
Another instance of Certbot is already running.Error: Another instance of Certbot is already runningUnable to acquire lock /var/lib/letsencrypt/.certbot.lockcertbot lock file already running Meaning
Wait for the other run, check the process (ps aux | grep certbot), and if none is running delete the stale lock (/var/lib/letsencrypt/.certbot.lock). Avoid overlapping cron jobs and the snap/systemd timers running together.
Common causes
- Overlapping cron and systemd timer runs
- Hung or crashed previous run
- Stale lock file
- Manual run during renewal
- Multiple tools managing certbot
⚡ Quick fix
ps aux | grep certbot- Remove the stale lock if no process is running
- Keep a single scheduler (systemd timer or cron)
Detailed fix by platform
Shell
- bash
ps aux | grep [c]ertbot sudo rm -f /var/lib/letsencrypt/.certbot.lock systemctl list-timers | grep certbot
How to diagnose
- Process — Running?
- Lock — Stale?
- Schedulers — Duplicated?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- archive /etc/letsencrypt/live/<domain>/privkey.pem symlink to archive unreadable (permissions after certbot upgrade)
- Challenge failed for domain Let’s Encrypt / Certbot: Challenge failed for domain example.com — Invalid response from http://example.com/.well-known/acme-challenge/x: 404
- Could not automatically find a matching server block Certbot: Could not automatically find a matching server block for example.com. Set the `server_name` directive to use the Nginx installer
Most viewed in SSL / TLS
- HTTPSConnectionPool: Max retries exceeded (SSLError) Python requests: HTTPSConnectionPool(host='api.example.com', port=443): Max retries exceeded with url: /v1 (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] ...')))
- DST Root CA X3 expired (old clients fail) Old clients: certificate has expired — Let's Encrypt chain uses expired DST Root CA X3 (OpenSSL 1.0.x, Android < 7.1.1)
- Keystore was tampered with, or password was incorrect Java keytool: java.io.IOException: Keystore was tampered with, or password was incorrect
Other ways to find it
Where this error sits
Origin: Network. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 18 Nov 2026