SSL for the HestiaCP itself on Ubuntu 24

Community Support Install & Set-Up
1

Hello, everybody.

Thank you once more for your efforts.

I installed the HestiaCP several times in the past on Ubuntu 22 and it’s been working very reliably ever since. If I remember correctly, the only difference in the latest version (v1.9.4), which I just installed on a Ubuntu 24, was that the installer asked for the name of the user with administrative privileges. I used a string other than the default admin.

If I remember correctly, the older versions set up SSL-enabled access to the panel itself automatically. For some reason, this was not the case this time anymore.

This latest HestiaCP instance is accessible at https://hcp.host.domain.tld:8083, albeit with a certificate related-error. Explicitely accessing http://hcp.host.domain.tld:8083 triggers an automatic redirection. Not sure why.

When attempting to enable SSL for the hcp.host.domain.tld domain, I keep getting errors like the following:

Let’s Encrypt validation status 400 (``hcp.host.domain.tld``). Details: 403:“144.24.175.187: Invalid response from ``http://hcp.host.domain.tld/.well-known/acme-challenge/7IcdwMMZIXWLRzMwQZNtIdKHB4x1EitNC5bJ51V5wTk:`` 404”

Mind you, the response uses http and not https.

Is this problem known or am I missing something particular for my situation?

Thank you.

2

Hi @ioan

Did you try this command?

v-add-letsencrypt-host
1 Like
3

Also check if the host DNS is set to child-dns template before applying the SSL.

4

Thank you, both.

For now I am only trying to figure out why is this SSL-related issue occuring for the HestiaCP itself, given the fact that older versions didn’t have it (at least as far as I can remember).

I tried a few things, but couldn’t get anywhere. Eventually I recreated the entire VM, just to start with clean slate.

From my research, it seems to me that this SSL problem is expected behavior, if the sysadmin chooses a user name other than admin for the HestiaCP administrative user at installation time.

Do you know, by any chance, if this is indeed the case?

5

It should work fine a non “admin” username. Use it currently with any thing else.

I wonder if the xxx.xxx.xxx.de is the issue instead

6

Thank you.

I managed to reinstall HestiaCP on the fresh VM with an administrative user name other than admin. SSL encryption for the panel itself worked out the box.

Likely, the old VM had issues.

1 Like
7

How to change the old admin username from the previous admin username to the new admin username. and refresh the new admin username in Hestia’s /home directory

Version 1.9.4
debian12
Automatically upgraded from 1.8.4
Is it necessary for me to change the original username admin to the new username?

8

AFAIK Hestia doesn’t provide such feature. Why do you want to change the name of the admin user?

No, there is no need to change it.