We are happy to announce that Vesta is back under active development as of 25 February 2024. We are working on v1 candidate and expect to engage more with the community over the coming months. We are committed to open source, and we encourage contributors to help us build the future of Vesta.
Letsencrypt problems
Letsencrypt problems
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
Don
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
Don
Re: Letsencrypt problems
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
Commit to fix -> https://github.com/serghey-rodin/vesta/ ... b89f2e87cb
Re: Letsencrypt problems
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
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
Re: Letsencrypt problems
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.
Regards,
Matt
Regards,
Matt