AutoSSL Renewal Issues

[Bossmanuk]

Morning Everyone,
I have started to get the following errors on auto renewals DNS Redirection problem for Domain Name with www and without it. No idea why this has started to happen as it was working perfectly fine before without issues. Has anyone else experienced this recently?

Thanks

Bossmanuk

[overseer]

Intermittently seen this. Not consistent enough to nail down.

[Starburst]

Been seeing it intermittently with mail.

After renewal, mail clients like Outlook/Thunderbird are reporting an invalid SSL.

Manually delete & reissue the certificate (WebServer Settings -> SSL Certificates) and then everything is fine.

[chrisk]

I have been seeing failures on some renewals. in both cases the domain is fronted by Cloudflare. Any one else experiencing renewal failures lately? Any solutions?

[overseer]

Cloudflare, yes. I am using the AutoSSL method on my CWP servers. On another dedicated mail server I maintain, it uses the DNS method with certbot and I have never had issues with renewals using that method.

[dustinduse]

I assume no fix for this was ever found? I have this happening 75%+ of the time after an update last week.

Wouldn't be a huge issue if the system kept retrying like it had in the past. Today, a cert with 31 days remaining, doing its first attempted renewal, failed due to this error and was replaced with a self-signed cert. Which cut my 31 days to look at the issue into GET UP RIGHT NOW AND FIX IT.... So here I am, pissed off and tired.

What do I need to collect from the 3 servers I have doing this constantly to get this resolved ASAP?


EDIT: Digging through logs. It looks like maybe there is a validation step from CWP 158.69.227.165. I seem to see a connection from that IP on every successful SSL renewal and no connection when there are failures. Failures appear in two ways. 1. Instant failure, no return. 2. "SSL proxy response status: 0," which appears to be related to no callback from 158.69.227.165? These then, in turn, appear to surface as the DNS missing WWW issue.