Compatible with
account required
HAProxy
HAProxy deployment Transactional certificate update through the Runtime API. Disk persistence is required so restarts keep the cert. ssh/WinRM sessions use pinned host keys. Runtime API set ssl cert + commit ssl cert, then persist to disk
Verification: test_verified. Connection: unknown. Credentials: none. Live E2E: no.
No disposable HAProxy host with pinned known_hosts and a TLS listener is configured.
What sslcertificates.io can do
HAProxy deployment Transactional certificate update through the Runtime API. Disk persistence is required so restarts keep the cert. ssh/WinRM sessions use pinned host keys. Runtime API set ssl cert + commit ssl cert, then persist to disk Capabilities: atomic_write, config_test, reload, tls_verify, rollback. Authentication uses ssh.
Required permissions
Restricted service account. Commands are allowlisted: Runtime API set ssl cert + commit ssl cert, then persist to disk. Known-host verification is mandatory.
Setup
Open Dashboard → Integrations → HAProxy. Enter the credentials described on this page. Values are encrypted at rest and never shown again. Run Test connection. Discovery runs only after authentication succeeds. Select a discovered resource. Do not paste opaque IDs unless the provider cannot enumerate them. Perform the certificate or notification action, then confirm the external system matches. Disconnect removes stored credentials and owned test resources created by sslcertificates.io.
Known limitations
User-supplied shell is rejected. A successful file write is not enough; the TLS endpoint must present the new fingerprint.
Official sources
Fact checked 2026-09-20. https://www.haproxy.com/documentation/ HAProxy is a trademark of its owner. sslcertificates.io is not a partner or certified reseller unless a written agreement exists.
Capabilities
Connect
HAProxy is a trademark of its owner. sslcertificates.io is not a partner or certified reseller unless a written agreement exists.