This solution consists of creating a symbolic link from the certificate origin location to the destination location. This is the best solution since VestaCP will automatically renew LetsEncrypt certificates – a symbolic link would ensure any updates are reflected in the VestaCP admin panel.
mv certificate.crt certificate.crt_old
mv certificate.key certificate.key_old
ln -s /home/admin/conf/web/ssl.DOMAIN.TLD.key /usr/local/vesta/ssl/certificate.key
ln -s /home/admin/conf/web/ssl.DOMAIN.TLD.crt /usr/local/vesta/ssl/certificate.crt
sudo service vesta restart
Be sure to change domain.tld with the domain your server is using with VestaCP