The address https://mydomain.com is using a right certificate (it has been already updated successful several times), but https://mydomain.com:8083 is using an expired certificate. It should be updated yesterday, but id didn’t.
I don’t know if it’s due to the update of Hestia to v.1.4.11 just yesterday too or due to the expiring of the SSL certificate JUST ALSO yesterday.
So i’ve 2 doubts:
- a) is it required to use 2 different certificates for 2 different ports?
- b) in affirmative case, why Hestia has not updated the :8083 certificate?
I don’t like ask on forums before to deeply search on forums. But certainly i’m already without options/answers.
a) As i read “there”, the same certificate for a domain.com is USABLE for any port. So, HestiaCP (nginx?) should serve the answer to mydomain.com:8083 taking the SAME certificate than for the default web requests for that domain? I don’t know enough about the marriage of HestiaCP-Nginx, and maybe it not depends on hestiaCP management, but on Nginx configuration.
b) (doubt) How does it know NGINX which domain name will be used on browser to users access to HestiaCP if there are more than one domain names hosted in the same HestiaCP? In my case, following recommended good practices, i created my domain name under a NOT-ROOT user. But other users could create other domain names. Then, HestiaCP (:8083) is accessible through all of these domain names? What happens then with the SSL certificates.
@eris Suggested to me run this command (when i explained all this as comment of another topic):
But this didn’t solved the question. In fact, i found a new problem (not directly related with this topic… or maybe it is!?): when running this command Hestia try to renew a Letsencrypt certificate for a NON-EXISTING domain name: mydomain_old.com which i created far far away and i removed from Hestia almost a year ago.
For mysterious reason it survive in a black whole, hehehe, and appears again! I have removed 3 times some minutes ago -before write here- and after executing the above command the domain name APPEARS AGAIN under de default “admin” user of HestiaCP and… causing a fail in the certificates renew process.
Then i tried this other similar command:
v-add-letsencrypt-domain 'my-not-root-user' 'mydomain.com'
And it successfully renewed the Lets Encrypt certificate for that domain (the unique hosted on my server), but didn’t altered the domain used for mydomain.com:8083
My apologies for be so exhaustive with my explanations, but i understand that in this way is easier for you to helo me. Thanks again!