Access to the user's domain panel

How can a domain user log into his account? In Hestia, he is on a shared VPS, where there are several accounts. As administrator, I logged into https://IP:8083, but I have a syscon32 user. How should he log in?

You should break yourself of the habit of logging in via IP. Hostnames exist for a reason. You user will login the same way that you should at https://example.net:8083

Thank you. When trying to access https://syscon32.cl:8083:
the following appears in the browser: (Image attached)

How can I solve this problem?

Here is a guess where to start

The certificate is only valid for the following names: mail.servpc.cl, servpc.cl, www.servpc.cl

dont see a syscon32.cl in the list.
This may help

v-change-sys-hostname host.domain.tld
v-add-letsencrypt-host

or just use this one https://servpc.cl:8083/login/

1 Like

Before reviewing the recommendations, I want to clarify that I use Hestiacp on a shared VPS, where I have several domains hosted, servpc.cl is the main domain, syscon32.cl is a new hosting.

I should also do this: v-change-sys-hostname host.domain.tld
v-add-letsencrypt-host without problems
I must use host.domain.tld

Error: DNS record for host.domain.tld doesn’t exist
Error: Let’s Encrypt SSL creation failed

Someone else will have to correct me if I am wrong.

You dont access the hestia cp on every domain hosted on the server. You pick one domain to access the hestia cp and it matches your hostname.

and no you should not have put ‘host.domain.tld’ as the domain

for example: www.example.com

the host is ‘www’
the domain is ‘example’
the tld is ‘com’

v-change-sys-hostname servpc.cl
v-add-letsencrypt-host

then all your customers/accounts would access hestia cp at:
https://servpc.cl:8083/login/

1 Like

And I have to do that for each hosted domain?
If I enter https://IP:8083 as administrator, I get the above

Unless you have obtained a certificate that includes your IP, which is not common practice, you cannot access HTTPS via IP without encountering a warning. That is why I suggested that you cease that behavior since it encourages the bad habit of ignoring security warnings.

Just use the official hostname that you have assigned to your HestiaCP like @jperkins described, regardless of which user needs access.

1 Like

I got it now, although I still have problems with SSL

Someone else is gonna have to help you with a screenshot not in English. sorry I cant read it, nor paste it into a translator.

Here is the message in English

Failed to connect

An error occurred while connecting to servpc.cl:8083.

The site is temporarily unavailable or very busy. Please try again later.
If you can’t load any pages, check your computer’s network connection.
If your computer is behind a firewall or proxy, make sure Firefox is allowed to access the web.

it is working properly from here

1 Like

and you are only 10ms away. Looks like Atlanta


dooserver (192.168.x.x) -> servpc.cl (45.79.196.36)                                         2024-08-17T14:46:24-0500
Keys:  Help   Display mode   Restart statistics   Order of fields   quit
                                                                       Packets               Pings
 Host                                                                Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. _gateway                                                          0.0%   113    0.4   0.4   0.3   0.6   0.1
 2. host-138-43-213-x.cpws.net                                        0.0%   113    2.6   3.5   1.7  27.8   3.0
 3. er-b.cpws.net                                                     0.0%   113    2.7   3.0   1.6   8.3   0.9
 4. host-74-51-15-185.united.net                                      0.0%   113    2.9   4.6   1.5  49.9   6.3
 5. host-74-51-15-59.united.net                                       0.0%   113    3.4  11.8   2.8 129.5  26.8
 6. host-74-51-15-47.united.net                                       0.0%   113    3.6  11.1   3.1 154.3  26.6
 7. host-74-51-15-137.united.net                                      0.0%   113    4.3   4.5   3.8  16.4   1.5
 8. 208.86.65.87                                                      0.0%   113   10.6  10.6  10.1  18.0   1.0
 9. (waiting for reply)
10. (waiting for reply)
11. (waiting for reply)
12. (waiting for reply)
13. 45-79-196-36.ip.linodeusercontent.com                             0.0%   112    9.8  10.0   8.9  10.6   0.2

Thanks for the help, it seems that the DNS was missing, perhaps, because now it is fine.

I am going to update a password, because in some of the domains it gives an error:
Welcome to Hestia Control Panel

Invalid username or password. When I enter the servpc site, it enters correctly, but if I try to enter with the syscon32 user it gives that error, even though I have changed the password

It is unstable, in some cases it works well and in others the previous message appears again
I will keep trying.
Thank you very much

1 Like