Install Certificates by Platform

Install and configure TLS certificates on nginx, Apache, IIS, Tomcat, Kubernetes, HAProxy and more.

• Certbot renewal

  Renewal is already automated by a timer you did not install. What to check when it silently stops working, and why a renewed certificate still serves the old one.

• Install a TLS certificate on nginx

  nginx has no chain directive — the intermediates go in the same file as the certificate. That one detail causes most nginx TLS problems.

• Install a TLS certificate on Apache httpd

  Apache 2.4.8 changed how the chain is supplied. SSLCertificateChainFile is deprecated — the intermediates go in SSLCertificateFile now.

• Install a TLS certificate on IIS

  IIS wants a PKCS#12 archive, not PEM files. Build the PFX with OpenSSL, and use -legacy if the import dialog rejects a correct password.

• Kubernetes TLS secrets

  Create a kubernetes.io/tls secret from a certificate and key, including why the certificate file must contain the full chain for Ingress to serve it correctly.

• Install a TLS certificate on Apache Tomcat

  Tomcat 8.5+ reads PEM files directly, so the old keystore dance is optional. Here is both routes, and the keystore/key password trap.

• Install a TLS certificate on HAProxy

  HAProxy wants one PEM file containing the certificate, the chain and the private key — the only common server that expects the key in the same file.