Vesta Control Panel - Forum

Normally this happens because the vesta path is not part of your servers exported PATH.

Try this:

export PATH=$PATH:/usr/local/vesta/bin/

:-)

I suppose you are very very new to server management ?

Vesta uses apache or nginx to serve web pages.

I would suggest googling 'how does a webserver handle multiple connections' or something like that.

Yup, after like four tries it (enab/disable ssl) it created and issued the cert.

I did a ton of reading on ACMEv2 - we have until November 2019 for new registrations.

I hope that VestaCP gets an update out soon.

This has been discussed already, but answers were not given about when or even how to fix this problem.

Let's encrypt will not renew due to new auth. You replied 24 version alreadu fixed this, yet no release has happened.

I now have multiple domains with expired certs.

How can I fix this NOW?

All the links are down, info@vesta says its the purchase provider.

Idk.

Yes, it is a lot of manual configuration. If you have a lot of domains on their own IPs it will take some time. I was looking at how to automate it, and I should be able to, but I'm strapped for time. Also, you need to change v-update-host-certificate which will need to be chattr +i to stop an over ...

Depends on your actual configuration, but setting all alias subdomains will add them to the LE ssl cert, yes :-)

You can add them as their own domains (xxx.xxx.tld) if you want them to have their own folder. Which will give them their own cert.

:-)

Confirmed working on Ubuntu 18.04