This guide is not specific to Checkmk! It applies to web server configuration in general, and we provide this article for your convenience. We can not support you with general web server issues.


Numerous problems related to TLS encryption come down to a simple reason: The web server is configured improperly.
More specifically, many web servers - especially ones not facing the internet - lack the full certificate chain. They only serve their server certificate.


Technically TLS encryption works with only the server certificate, but to verify the trust, you need the chain.
Modern browsers assemble the certificate chain themselves, which covers up the issue of a missing chain, but many CLI tools and programming languages expect the chain from the web server.



There is some further reading on certificate chains, which we want to share in advance and encourage you to read and understand:

Simply put, you only need a few things to work properly:


Before moving on to the actual configuration, you need to acquire and prepare the necessary files:

For the first two, if you do not have, or know how to get them, ask your PKI administrator or the person responsible for certificates in your organization. They should actually be able to provide you with all the files necessary.
If you have the former two files already and don't want to bother your certificate person, you can extract the CA files from your web browser.

  1.  Navigate to your Checkmk web interface
    1. Firefox

      1. Click on the little lock icon

      2. Then click on Connection secure and More information.

      3. Now you see the Page Info, where you click on View Certificate.
      4. This brings you to a page, where you can inspect and download all certificates involved.

  2. Chrome(ium)

    1. Click on the little lock icon

    2. Then click on Connection is secure and Certificate is valid.

    3. This brings you to a page, where you can inspect and download all certificates involved.

If you are running the Checkmk Appliance (virtual or physical) follow the below steps to configure the certificate chain. We have prepared the steps for our Checkmk Appliance as well as for the Apache web server on Linux.

Now, depending on your Checkmk infrastructure, choose the appropriate manual:

Checkmk Appliance

  1. Log into the webconf
  2. Navigate to Device Settings > Web Access
  3. Choose Upload Certificate
  4. Now choose the appropriate files and click Upload
    1. For the certificate chain, you only need the intermediate certificate(s), without the root certificate

Linux Server

The following steps depend on your specific Linux distribution.

  1. Log into the server as root
  2. Navigate to "/etc/[apache2|httpd]/"
  3. Locate your website configuration file. In a default installation this would be:
    1. Debian derivates: /etc/apache2/sites-available/default-ssl.conf
    2. RedHat derivates: /etc/httpd/conf.d/my-ssl.conf
  4. In the configuration file you will find the following directives:

    SSLCertificateFile      /path/to/certificate.pem
    SSLCertificateKeyFile   /path/to/certificate.key
    SSLCertificateChainFile /path/to/chain.pem

  5. Save the file and reload Apache2: "systemctl reload [apache2|httpd]"

Related articles

Related articles appear here based on the labels you select. Click to edit the macro and add or change labels.

Related issues