Securing the Checkmk web interface with HTTPS #CMKTutorial

In this tutorial, Bastian demonstrates how to secure the Checkmk web interface with HTTPS. This ensures that the data transfer with the web UI is secured by encryption and the site is protected from various cyberattacks that may happen due to unsecured connection.

Blog article for best practices for security:

-----------------------------------------------

Follow us on Social Media
-----------------------------------------------

----------------------------------------------
00:00 Introduction
00:31 Generating a private key and a certificate file
03:13 Installing the certificate file
06:53 Troubleshooting
07:29 Conclusion

[emike]

Thanks for making this. There are some big discrepancies, however. You list generating private.pem and request.csr, then mention the full chain (chain.crt) and certificate.pem. Where did those come from?

[stefanreinhardt]

Danke für die Anleitung, aber ein Skript, dass das automatisch erledigt, wäre mir lieber... 🙂

[Wahinies]

Quite a bit different from the documentation thank you. The configtest shows syntax okay after removing the passphrase from the keyfile however after the a2ensite default-ssl the HTTPS connection just times out (double checked allowed through UFW). When disabling the site it just refuses HTTPS.

Update- turned out to be the certificate.. I went with Certbot using DNS validation because I cannot open port 80 to the internet. For anyone having issues with certificates, follow the guide but the part with Certbot use the digitalocean guide

[bryancp]

I am running this in a test environment. If I don't have a domain can I use the IP for the domain fqdn field?

[microcisco]

You added the chain.pem file into /etc/ssl/certs/ folder yet when you changed the default-ssl.conf file, you made the SSLCertficateChainFile point to /etc/apache2/chain.pem thats not going to work????