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 started failing update
letsencrypt started failing update
I had a situation I thought I'd relay for others who may hit it.
letsencrypt started failing for my main control panel domain while it continued to work for other domains I created in the panel. An important factor is I use an external dns.
If I would run "v-check-letsencrypt-domain admin panel.domain.tld", I would see the response, "Error: Could not connect to panel.domain.tld". I would get the same error if checked on ssl in the vestacp control panel and saved. (and tried that too many times in my testing to hit the rate limit :) )
I discovered that at some point letsencrypt started switching to use IPv6 if available. I had disabled this on my server, but neglected to remove the AAAA record for panel.domain.tld on my external dns. Because letsencrypt would see that IPv6 record, it would try it and not be able to connect and does not appear to failover, or perhaps the script times out before that. Removing the AAAA IPv6 record from my external DNS stopped the CLI error and checking on the SSL and letsencrypt boxes in the vestacp control now also worked.
I hope that helps someone. Cheers.
letsencrypt started failing for my main control panel domain while it continued to work for other domains I created in the panel. An important factor is I use an external dns.
If I would run "v-check-letsencrypt-domain admin panel.domain.tld", I would see the response, "Error: Could not connect to panel.domain.tld". I would get the same error if checked on ssl in the vestacp control panel and saved. (and tried that too many times in my testing to hit the rate limit :) )
I discovered that at some point letsencrypt started switching to use IPv6 if available. I had disabled this on my server, but neglected to remove the AAAA record for panel.domain.tld on my external dns. Because letsencrypt would see that IPv6 record, it would try it and not be able to connect and does not appear to failover, or perhaps the script times out before that. Removing the AAAA IPv6 record from my external DNS stopped the CLI error and checking on the SSL and letsencrypt boxes in the vestacp control now also worked.
I hope that helps someone. Cheers.
Re: letsencrypt started failing update
I should make it clear that although the domain was panel.domain.tld, this is the standard port 80. Not the actual control panel on 8083.
Re: letsencrypt started failing update
Thanks for the tip.
Well it's already time for vestaCP to support ipv6
Well it's already time for vestaCP to support ipv6