Our ISPConfig server handles our websites nicely, however, if we refer to the server's IP address or full hostname in the browser, we do not get the expected result, because in this case the Apache2 Debian Default Page is loaded, which is essentially Apache's "welcome" page. Of course, this is not a tragic mistake, but a beauty mistake. In this description, we will see how we can configure our Apache web server so that the website we want is loaded.

By using the HSTS header, we can make our websites more secure against man-in-the-middle attacks. In this short description, we will see how we can set this HTTP header in our Apache-based LAMP or ISPConfig server environment.

The HTTP/2 or HTTP2.0 protocol enables faster web services with less data traffic. Although the protocol created in 2015 has been widespread for quite a few years, it is not turned on by default in the majority of web servers due to compatibility reasons. Among other things, it does not support the outdated mod_php Apache module, which in turn still operates many old websites, so enabling and enabling it is left to system administrators. In this short description, we will see how we can enable the use of the HTTP/2 protocol on Apache web servers that still use the old HTTP/1.1 protocol.

In this tutorial, we will install Let's Encrypt Certbot on an ISPConfig3 server environment. Once the installation is complete, our system is ready to obtain and automatically configure and renew free SSL certificates for server-managed domain names so that any web site we manage can be operated over the secure HTTPS protocol with a few clicks.