We are starting CHRISTMAS Sale. Get 30% OFF on lifetime licenses with code: FYSKK72

Letsencrypt problems

Questions regarding the Web Server
Apache + Nginx, Nginx + PHP5-FPM
Posts: 22
Joined: Thu Jul 30, 2015 1:42 pm

Letsencrypt problems

Postby donat » Wed Dec 07, 2016 5:25 pm

We have several problems with letsencrypt and subdomains.

We hoped, that with the new gui we would have better options. But we messed up right now.

Following error in the gui:
Error: Invalid response from http://files.vfmg.ch/.well-known/acme-c ... amDlZP-c9Q: \

In the CLI:
When executing following command:
letsencrypt-vesta -a 60 -u vfmg pydio.vfmg.ch

Then there is just one error: SSL=no doesn't exist.

The certificate itself is released for a wrong url. (Maybe it was alread released before the command for the wrong user). What can I do?

Kind regards

VestaCP Team
Posts: 7807
Joined: Fri Dec 26, 2014 2:23 pm
Location: Moscow

Re: Letsencrypt problems

Postby skurudo » Thu Mar 02, 2017 8:35 pm

If you have apache only configuration, then it's your case - https://bugs.vestacp.com/issues/483

Commit to fix -> https://github.com/serghey-rodin/vesta/ ... b89f2e87cb
-> DigitalOcean competition - please, support us
-> fix for phpmyadmin - nice and sweet now

Posts: 16
Joined: Sun Nov 22, 2015 12:22 pm

Re: Letsencrypt problems

Postby BaDTaG » Wed May 17, 2017 8:48 pm

So don't know if this is to old but i had the same problem and got error 2 when trying to enable lets encrypt.
found that it had to do with the certificates and keys. in /home/USERNAME/conf/web/sapache2.conf it gave error that it culd not find ssl.default.domain.ca .... So i edited sapache2.conf and found .ca and changed it to .pem on all sites.
fixed it. and i culd enable lets encrypt.

think it has to do with the different types .ca and .pem used. when u try and switch to letsencrypt .ca it messes up the old .pem way

Posts: 8
Joined: Thu Jan 19, 2017 8:54 pm

Re: Letsencrypt problems

Postby revelnode » Wed Jul 26, 2017 1:01 am

Thanks for the fix, any idea when it will actually be applied to the install? Saves me from having to come back to this post every time I do new install on a fresh server... something this old should have already be patched.


Return to “Web Server”

Who is online

Users browsing this forum: No registered users and 8 guests