Setting up Let's Encrypt with a public IP and multiple domains in Hestia CP.

Hello to all community members, I have a question about the Hestiacp panel: I have successfully installed it on Debian 11 with all updates, and it works perfectly. I use it as a self-hosting solution on a real physical machine with a public IP from my internet provider in Paraguay. Currently, it has a working domain, and its hostname is correctly set with Lets Encrypt SSL certificates. I’ve been looking for a way to implement the same certificate for all the domains I create within the server. If I try to enable Lets Encrypt support from the panel for each domain separately, the panel creates SSL support for the last domain where I activated it but removes SSL support for the previously activated one.

I found a tool called certbot, which theoretically activates SSL support for all domains using a single public IP for the server. How do I achieve this using Hestiacp?

Hestia works fine with multiple SSL certificates on server …

With the exception for anything on port :8083…

Could you please tell me how to make HestiaCP generate Let’s Encrypt certificates for all the domains I have created on my server?

The issue I’m facing is that, for example, I have a domain that is working fine with Let’s Encrypt. However, when I try to generate another Let’s Encrypt SSL certificate for another domain that will use the same shared IP, the panel generates it correctly but removes the SSL from the previous domain, and this keeps happening.

As long for the it should work fine …

I have multiple domain running on it with out any problems …

The server where this works for you, does it have a single shared IP configured for all the set up domains? The issue is that if I follow that procedure, the Let’s Encrypt certificate is configured for the last domain in which I perform that setup procedure. However, the SSL is also removed from the last domain where it was activated. In other words, Let’s Encrypt provides an SSL certificate for a domain with an IP address. But, if I have a single IP address with multiple domains created in the same panel, what should I do to ensure that Let’s Encrypt can provide SSL certificates for all the domains configured in Hestia CP?

I have only a single Ip adress on that server… It should work fine …

How do you request a new certificate then?

Apparently, I follow the exact process you showed me in the screenshot. For instance, I currently have Let’s Encrypt SSL on the domain, and I would like to add Let’s Encrypt SSL certificates to the domain (and another 11 or 12 domains) with their respective webmail When I do this, Hestia CP removes the SSL from the existing domains and assigns it only to the most recent one.

Could you please explain in detail what are you doing? Because you only need to edit the web domain and select Enable SSL for this domain and Use Let's Encrypt to obtain SSL certificate (you can also add automatic redirection to HTTPS and HSTS) and once done Save


Do the same for all your domains.

1 Like

I will try to be as descriptive as possible:

I have installed Debian 11 on a server, and successfully installed the Hestia CP panel, which is working fine.
I have created plans and users for the panel successfully.
I have also been able to properly set up all the domains in the DNS so that the same server hosting the panel acts as the primary DNS (in my country, Paraguay, there are limited freedoms regarding external hosting, so I set it up on my own server to configure it as I like).

Now, I have 12 domains created with a single public IP, and what I need is for all the domains to have Let’s Encrypt certificates.

For some reason, when I configured the first domain, it worked well. However, when configuring the second domain, the system assigned the Let’s Encrypt certificate to the second domain but removed it from the first one. This pattern repeats with the rest of the domains.

It has no sense, could you please explain how are you doing that? Using Hestia you add a web domain and configure it to issue and use a Let’s Encrypt certificate, then you add a new web domain and configure it to issue and use a Let’s Encrypt certificate and it will create different and independent certificates for your different domains.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.