AutoSSL inadvertently port sniffing on sub-domains

CODE grunt

• August 15, 2017 12:52

Howdy. While troubleshooting some failing AutoSSL renewals I noticed the following log entries (NOTE: domain, IP and keyfile name changed for privacy reasons): ------------ The system failed to send an HTTP "GET" request to " because of an error: Could not connect to 'mail.example.com:80': Connection timed out . The domain "mail.example.com" resolved to an IP address "192.168.1.1" that does not exist on this server. ------------ The issue is that cPanel automatically tries to enable autossl for a wide swath of subdomains (such as "mail") which may or may not be hosted on the local server. If the subdomain exists but is hosted offsite, it will create an outbound request to port 80 which will look like a port sniffing attempt. This could easily lead to reputation problems for the local machine, especially if anything like mod_security is running on the remote host. This becomes especially likely during troubleshooting when the check process may be triggered manually a number of times in succession. We really need to have the ability to limit what subdomains are used for AutoSSL. Cheers, Ron

• 

  cPanelMichael

  • August 15, 2017 18:11

  Hello Ron, cPanel version 66 includes a new feature that allows you to exclude individual domain names (e.g. mail.domain.tld) from the AutoSSL feature:

  0

Please sign in to leave a comment.