Hi, i’ve been using dehydrated to keep my certs updated since pretty much day 1, and it’s been worked flawless, but since a couple of days ago i’m having an issue with updating a cert that’s about to expire soon: Processing pokemap.berlin with alternative names: www.pokemap.berlin dev.pokemap.berli…

From where i am, i can access http://dev.pokemap.berlin/ over IPv4, but not IPv6. For dual-stack sites, Let’s Encrypt used to prefer to validate over IPv4, but it was recently changed to prefer IPv6. You need to see what’s going on with that site’s IPv6 connectivity, or remove the AAAA record. (O…

Ah, that would explain it! My outgoing IPv6 still works fine, i’ll check why the incoming stopped working. Thanks!

Hi @jangrewe , Apologies for the issuance problems! As @mnordhoff mentioned we recently changed to preferring IPv6 for dual-homed hosts, but the implementation is meant to fall back to IPv4 if the IPv6 connection doesn’t work. You’re not the first person to notice this doesn’t seem to happen but I …

Thanks @cpu , i’ve added my details to that issue. The actual reason was that my ISP decided to, for whatever reason, not properly route that specific IPv6 to my server anymore. I moved to a different IPv6, updated the AAAA record, now it’s working fine again.

Certbot - IPV6 Not Configured and Challenges Fail (IPV6 Preferred) - #6 by cpu - Help

Topic		Replies	Views	Activity
Certbot - Not able to verify Domain due to IPV6 Records Help	2	1288	May 25, 2017
Certbot - Challenge Not Passing Due to IPV6 Configuration Help	3	2384	May 25, 2017
Renewal of certs fail Help	13	276	August 7, 2024
Certbot trying a challenge to old IPv6 instead of new IPv4 Help	9	1146	July 16, 2021
Preferring IPv6 for challenge validation of dual-homed hosts API Announcements	0	6791	May 23, 2017