Vesta Control Panel - Forum

When the certificate was initially installed, subdomain.domain.com was created to launch the panel at https://subdomain.domain.com:8083, on which the certificate and the key were generated.
This certificate and the key were copied from the files on the path /home/user/web/subdomain.domain.com/private/tmp.folder/ to the files by the path /usr/local/vesta/ssl/.
Before the end of the first validity period of the certificate, the panel was launched at https://subdomain.domain.com:8083 without any problems. After the certificate has expired, the certificate and key information have been copied to the panel certificate files again, but the problem is that the validity dates of the certificate have remained the original and the panel at https://subdomain.domain.com:8083 starts as a "Non Secure" connection.
Thus we have the following:

1. SUBJECT and ALIASES on the domain itself and in the panel settings in the SSL section are defined correctly
2. NOT_BEFORE and NOT_AFTER in the domain settings - new (ie extended), the same settings for Vesta SSL remain old
3. The address https://subdomain.domain.com opens without problems, https://subdomain.domain.com:8083 same opens as Not Secure.

According to the above, there are two questions: how to extend the validity of the certificate in Vesta SSL and how to automate the process with Cron, so that each time you do not transfer certificates from the domain to the panel folder.

Thank you.

ScIT wrote:viewtopic.php?f=19&t=13057

Thank you. Helped me a lot.