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.
Let's Encrypt Certificates
Let's Encrypt Certificates
Hello,
I started using Let's Encrypt certificates for my sites under vesta , instead of self-signed certificates.
But now Im receiving mails that my Let's Encrypt certificates will run out and I need to update them.
I thought process should be automated when used inside Vesta? Is there a way to automate updating of certificates ? Also how to update the certificates on my own ?
Help is appreciated.
I started using Let's Encrypt certificates for my sites under vesta , instead of self-signed certificates.
But now Im receiving mails that my Let's Encrypt certificates will run out and I need to update them.
I thought process should be automated when used inside Vesta? Is there a way to automate updating of certificates ? Also how to update the certificates on my own ?
Help is appreciated.
-
- Support team
- Posts: 1096
- Joined: Sat Sep 06, 2014 9:58 pm
- Contact:
- Os: Debian 8x
- Web: apache + nginx
Re: Let's Encrypt Certificates
Please try to read a few pages on the forum before posting such a generic question.
Yes, when you enable Let's Encrypt on any domain, there is an automatic Daily cron setup that renews all SSLs that are less than 30 days to renew.
Yes, when you enable Let's Encrypt on any domain, there is an automatic Daily cron setup that renews all SSLs that are less than 30 days to renew.
Re: Let's Encrypt Certificates
check at the cron tab. you should have something like the following line
Re: Let's Encrypt Certificates
I had that cron job only on admin user, not on any other... I have added it manually, hopefully that is fixed.
Thanks for your help.
Thanks for your help.
-
- Support team
- Posts: 1096
- Joined: Sat Sep 06, 2014 9:58 pm
- Contact:
- Os: Debian 8x
- Web: apache + nginx
Re: Let's Encrypt Certificates
The cron job renews it for all domains server-wide under all users, it is not needed inside individual users.
If you want to admin a VestaCP Server, I'd suggest you to read through the forums and learn a bit more before using it full time.
If you want to admin a VestaCP Server, I'd suggest you to read through the forums and learn a bit more before using it full time.
Re: Let's Encrypt Certificates
If that is the case, how do you explain the mails I'm receiving from Let's Encrypt that certificates will run out soon and that I need to update them ?mehargags wrote:The cron job renews it for all domains server-wide under all users, it is not needed inside individual users.
If you want to admin a VestaCP Server, I'd suggest you to read through the forums and learn a bit more before using it full time.
Re: Let's Encrypt Certificates
He do not explains that, he explains that you need to have some basic linux knowledge and the ability to understand how for example to run the letsencrypt script manualy to see if you have any error.Perp wrote:If that is the case, how do you explain the mails I'm receiving from Let's Encrypt that certificates will run out soon and that I need to update them ?
You didn't provide any informations about your system, maybe also you didn't check your log files (you can find the paths here: https://vestacp.com/docs/), you just post a generic request "i get this mails". Without any additional information we are unable to provide any support.
Let's Encrypt works on our system without any problems "out of the box". So if you want to have some free support, please share more informations, otherwise you are free to choose the VestaCP payed support: https://vestacp.com/support/
Re: Let's Encrypt Certificates
OK, the problem was that I had this error when using v-update-letsencrypt-ssl:
DNS problem: NXDOMAIN looking up A for <name>.alpha.<domain-name>
I fixed by removing dependecies to that alpha sub-domain.
DNS problem: NXDOMAIN looking up A for <name>.alpha.<domain-name>
I fixed by removing dependecies to that alpha sub-domain.