lock SSL / TLS Origin: Network OSI layer 7 · Application Last updated 18 Nov 2026

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.

Exact message you may see 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
Seen on: Certbot Linux SSL

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

  1. ps aux | grep certbot
  2. Remove the stale lock if no process is running
  3. Keep a single scheduler (systemd timer or cron)

Detailed fix by platform

Shell

  1. bash
    ps aux | grep [c]ertbot
    sudo rm -f /var/lib/letsencrypt/.certbot.lock
    systemctl list-timers | grep certbot

How to diagnose

  1. Process — Running?
  2. Lock — Stale?
  3. 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:

Where this error sits

Origin: Network. Errors that are often confused with or caused by this one (click to open):

archive — /etc/letsencrypt/live/<domain>/privkey.pem symlink to archive unreadable (permissions after certbot upgrade) (SSL / TLS)archiveChallenge 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 (SSL / TLS)Challenge failed for …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 (SSL / TLS)Could not automatical…deploy hook — Certbot renewed the certificate but the server still serves the old one (deploy hook / reload failed) (SSL / TLS)deploy hookDjango — Django send_mail: ssl.SSLError: [SSL: WRONG_VERSION_NUMBER] (EMAIL_USE_SSL vs EMAIL_USE_TLS on the wrong port) (Email / SMTP)DjangoDNS plugin — Certbot DNS plugin: Error determining zone / invalid credentials (Cloudflare/Route53 API token) (SSL / TLS)DNS pluginIncorrect TXT record found at _acme-challenge — Certbot: DNS problem: NXDOMAIN looking up TXT for _acme-challenge.example.com / Incorrect TXT record (SSL / TLS)Incorrect TXT record …Invalid response from .well-known/acme-challenge: 404 — Certbot: Detail: Invalid response from http://example.com/.well-known/acme-challenge/abc: 404 (SSL / TLS)Invalid response from…lock

Explore the map of this error Full error map →

🧠 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.