---
title: "Discussion on \"Let's Encrypt on HAProxy\" | Hashnode"
description: "Discussion on \"Let's Encrypt on HAProxy\". This article shows how to install certbot on haproxy and renew automatically let's encrypt certificates."
url: "https://hashnode.com/posts/lets-encrypt-on-haproxy/6103a80e9036db5b3513bd0a"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Let's Encrypt on HAProxy](https://devops.dina.ch/lets-encrypt-on-haproxy?utm_source=hashnode&utm_medium=feed)

This article shows how to install certbot on haproxy and renew automatically let's encrypt certificates.

Jul 30, 2021 · 4 min read · devops.dina.ch  
Updated Jun 20, 2022  
Read the article

-   [#linux](https://hashnode.com/tag/linux)
-   [#ssl](https://hashnode.com/tag/ssl)
-   [#automation](https://hashnode.com/tag/automation)
-   [#security](https://hashnode.com/tag/security)
-   [#ubuntu](https://hashnode.com/tag/ubuntu)

## Written by

[DINA](https://hashnode.com/@cisel)

@cisel · Switzerland

  
[View profile](https://hashnode.com/@cisel)

DevOps team

## Responses 1

Markdown supported · ⌘↵ to post

[Edge Ops](https://hashnode.com/@edgecacheops)

[Nov 9](https://hashnode.com/posts/lets-encrypt-on-haproxy/6103a80e9036db5b3513bd0a/comment/6af21361031f8bf7cab7beed)

Terminating TLS on HAProxy stays calm when the certificate story and the frontend bind stay in one place. Keep the ACME challenge path reachable on the same frontend that serves the public Host, reload with a soft signal so existing connections drain instead of dropping, and point backends at private listeners so only the proxy owns the public certificate. Prefer one certificate map keyed by SNI rather than a pile of nearly-duplicate frontends, and monitor not-after dates so renewals never surprise a weekend on-call.

Ops prove-out after a renew or map change: open the public Host and confirm the served certificate SAN matches the name clients dial, then reload and watch active sessions while a light probe keeps returning success. If only one SNI name fails, check the crt-list map and that the challenge path still reaches the ACME helper. Most post-renewal outages are a hard restart mid-peak or a challenge path that only worked on the old frontend — treat reload and SNI coverage as first-class checks.
