Today I installed Hestia 1.4.3 on a Debian 10 VPS. I used the two default commands on the Hestia CP home page (as I have done dozens of times before without problem). I preceded these commands with
apt-get update && apt-get install ca-certificates
The first install attempt failed with the error:
Updating currently installed packages, please wait… W: GPG error: https://apt.hestiacp.com buster InRelease: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY A189E93654F0B0E5
E: The repository ‘https://apt.hestiacp.com buster InRelease’ is not signed.
I solved this problem by reinstalling Debian 10 on the VPS and then adding the following commands after updating and before the two Hestia commands:
To update the Hestia SSH Keys:
apt-get install gnupg2
Then:
wget -qO - https://gpg.hestiacp.com/deb_signing.key | sudo apt-key add -
The terminal replied with OK.
The installation was then able to proceed. However, near the end of the installation, Hestia gave this warning:
Configuring system settings…
[ * ] Configuring Hestia Control Panel…
[ * ] Generating default self-signed SSL certificate…
req: No value provided for Subject Attribute emailAddress, skipped
[ * ] Adding SSL certificate to Hestia Control Panel…
I am certain that I had properly added the email address. And I have installed Hestia many times in the past without this error. So I think there is a problem with Hestia 1.4.3.
The failure to find my email address prevented the installer from installing a Lets Encrypt Certificate. However, after the install, I was able to log into Hestia and add an SSL certificate to my primary domain address ns1.mysite.com.
Thus, all ended well. But I am hoping the leaders of Hestia can take a look at these two issues and find a fix for them for future versions of Hestia CP.
Thanks again for making such a terrific control panel!