Error code: 2 Lets Encrypt Support

[plaidshirtakos]

I tried to use Lets Encrypt Support under SSL Support section when I added a new domain name on web panel. I got this error message:

Error code: 2

[ScIT]

viewtopic.php?t=14685
https://www.google.ch/search?q=vestacp+ ... etsEncrypt

[plaidshirtakos]

There isn't any exact solution in these topics. Should I change from Apache to Nginx? But why?

[ScIT]

I think you didnt understand how vestacp works. Vesta runs default with apache2 and nginx as caching server. So what is your setup? If you use the default installation, be sure you have enabled apache2 and nginx (we use for both the default templates on our side). So as soon as all domains are setup properly, lets encrypt will work out of the box.

[jimmyeao]

There isn't any exact solution in these topics. Should I change from Apache to Nginx? But why?

Ditto here - unable to find a satisfactory resolution to this. It appears Vesta can't parse my sapache2.conf - I would restore from a backup, but there isn't a user/conf/sapache2.conf file in the backup, just one listed under each of my domains.
Why the backup structure differs from the server folder structure is beyond me, its less than helpful. Just looking at the apache conf files seems to make Vesta fall over, it really should be more robust in this area.

[jimmyeao]

I've finally found a fix that helped me, it comprises of several stages:
If you have an issue with Vesta parsing the apache2.conf or sapache2.conf, create a new user then move one domain to this new use and then back again. this appears to fix the issue with the conf files. The command to move a domain is done from the command line and is

Code: Select all

v-change-domain-owner domain.name user

Once you have done this, go though all your domains that are giving you an issue and remove SSL support. Note, if you try and re-enable it through the webinterface it will fail.
from the command line, for each domain, use the command

Code: Select all

v-add-letsencrypt-domain user domain.name

For some reason this works when the web interface doesnt, and letsencrypt updates now work,

Hope this helps someone!

[ScIT]

I've finally found a fix that helped me, it comprises of several stages:
If you have an issue with Vesta parsing the apache2.conf or sapache2.conf, create a new user then move one domain to this new use and then back again. this appears to fix the issue with the conf files. The command to move a domain is deon from the command line and is

Code: Select all

v-change-domain-owner domain.name user

Once you have done this, go though all your domains that are giving you an issue and remove SSL support. Note, if you try and re-enable it through the webinterface it will fail.
from the command line, for each domain, use the command

Code: Select all

v-add-letsencrypt-domain user domain.name

For some reason this works when the web interface doesnt, and letsencrypt updates now work,

Hope this helps someone!

this sounds like changed template files, maybe a v-rebuild-user username or in vestacp, mark all user then rebuild will help. just an idea.

[plaidshirtakos]

I think you didnt understand how vestacp works. Vesta runs default with apache2 and nginx as caching server. So what is your setup? If you use the default installation, be sure you have enabled apache2 and nginx (we use for both the default templates on our side). So as soon as all domains are setup properly, lets encrypt will work out of the box.

What kind of setup? I just added domains on web panel, process was successful, I can open uploaded website in browser.