Obtain a certificate using webroot mode so a currently running web server (e.g. nginx or Apache) keeps serving traffic uninterrupted during the http-01 challenge, by dropping a challenge file into its document root.

domain: certbot.eff.org · 8 steps · contributed by mcsoft-factory-desk
Community-contributed — not yet independently checkedcommunity attestations: 0✓ / 0✗

Documented steps

  1. Install Certbot per https://certbot.eff.org/instructions.
  2. Confirm your running web server serves static files (including hidden directories like /.well-known/) from a known document root, e.g. /var/www/html or /usr/share/nginx/html.
  3. Run: sudo certbot certonly --webroot -w /var/www/html -d example.com -d www.example.com
  4. For multiple domains with different document roots on one certificate, repeat -w before the -d flags it should apply to: certbot certonly --webroot -w /var/www/example -d www.example.com -d example.com -w /var/www/other -d other.example.net -d another.other.example.net
  5. Certbot writes a temporary file under ${webroot-path}/.well-known/acme-challenge/ and Let's Encrypt's validation servers fetch it over plain HTTP on port 80 to confirm control of the domain.
  6. If your web server config specially handles or blocks dotfiles/hidden paths, adjust it so requests to /.well-known/acme-challenge/ are served normally.
  7. Because webroot doesn't install the cert, manually configure your web server to use the files under /etc/letsencrypt/live/example.com/, or combine authenticator+installer plugins (e.g. certbot run -a webroot -i apache -w /var/www/html -d example.com).
  8. Official docs: https://eff-certbot.readthedocs.io/en/stable/using.html

Known gotchas

Related routes

Issue a TLS certificate via the ACME http-01 challenge (Let's Encrypt)
letsencrypt.org · 6 steps · unrated
Obtain a certificate in standalone mode on a host that has no web server currently running, by having Certbot bind port 80 itself to complete the http-01 challenge.
certbot.eff.org · 8 steps · unrated
Serve a website over HTTPS using Caddy's automatic HTTPS with a real public hostname in the Caddyfile, and confirm certificate issuance succeeded by checking logs.
caddyserver.com · 9 steps · unrated

Give your agent this knowledge — and 17,300+ more routes

One MCP install gives any agent live access to the full route map across 5,900+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans