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 now failing for those with ipv6 AAAA records
LetsEncrypt now failing for those with ipv6 AAAA records
Hi,
My sites are setup to use IPv4, but also have an IPv6 record setup in nginx, as well as the DNS. This all works fine:
https://community.letsencrypt.org/t/ves ... nt/36527/9
Is there anything we can/need to tweak to make it work? This basically means every domain's SSL certificate will expire, and the only way around it currently is to remove the AAAA record (not what I want to do)
Thanks
Andy
My sites are setup to use IPv4, but also have an IPv6 record setup in nginx, as well as the DNS. This all works fine:
I have a thread open here:root@admin:~# curl -g -6 "http://cdn.steampunkjunkies.com/.well-k ... llenge/foo"
sdfsad
root@admin:~# curl -g "http://cdn.steampunkjunkies.com/.well-k ... llenge/foo"
sdfsad
https://community.letsencrypt.org/t/ves ... nt/36527/9
Is there anything we can/need to tweak to make it work? This basically means every domain's SSL certificate will expire, and the only way around it currently is to remove the AAAA record (not what I want to do)
Thanks
Andy
Re: LetsEncrypt now failing for those with ipv6 AAAA records
So no one else is having this issue??? I find it hard to believe, considering this is a whole LE change, and other people using Vesta must also have IPv6 records that are screwing this up :/
Cheers
Andy
Cheers
Andy
Re: LetsEncrypt now failing for those with ipv6 AAAA records
I could have sworn I posted this! (but I couldn't find it to follow up). Ooops!
Re: LetsEncrypt now failing for those with ipv6 AAAA records
Ok, let's close then.