AutoSSL Quietly Dropped the Mail Name — a Cloudflare-Only Origin and the Move to DNS-01
A field story about a cPanel certificate that renewed on time and still broke every Outlook client — the port 80 rule almost nobody connects to mail — and the DNS-01 setup I now use for any origin locked to Cloudflare. The message came in the next morning. “Outlook is showing a certificate warning on every laptop. Nothing changed on our side.” The customer’s IT lead had already checked the…
A customer noticed that their Outlook client was displaying a certificate warning on all laptops, despite the website having a valid certificate. Upon investigation, it was discovered that the mail name was missing from the renewed certificate issued by AutoSSL. This occurred because the web names were proxied through Cloudflare, while the mail name had to be DNS-only.
AutoSSL uses Let's Encrypt with HTTP validation, which required connecting to the mail name on port 80. However, due to a hardening rule restricting TCP 80 access only from Cloudflare's IP ranges, the connection to the mail name timed out. As a result, AutoSSL issued a certificate without the mail name, causing Outlook to display the warning.
This issue can happen when web names are proxied and mail, FTP or control-panel names are DNS-only, especially after tightening port 80 rules. To resolve the problem, one must confirm the names served by the mail ports, examine the AutoSSL log for the missing name, and verify where the packets stop. In some cases, opening port 80 and renewing the certificate can temporarily fix the issue.
Rewritten by urgent.news; may contain errors — check the original.