Mail SSL with AutoSSL gives wrong cert on shared ip

karlog

• February 18, 2018 14:56

Hello This must be a problem that other users have been having, but I have been unable to solve it my self and spend a lot of time trying to google it. I have a VPS with WHM on, on the server I have multiple domains on a shared IP and everything is great. (At least I thought so) One of my users told me that everyone in his domain got a certificate warning while connecting to their SMTP server. Therefore I started digging around some more and noticed that this was a general problem for all the domains on the shared IP and a few of the domains on a dedicated IP. I am unable to make my server return the correct SSL certificate when connecting to a domain on a shared IP. Even when SNI is set to "Yes" I get the wrong certificate listed when connecting. If we say that the host is using "whmhost1.somedomain.dk" and the domain on the shared IP is mydomain.dk, then I want to be able to use the "Secure SSL/TLS settings" configuration that cPanel recommends. The settings cPanel shows me (and my customers) is something like: Username: test@mydomain.dk Password: *********** Incoming server: mail.mydomain.dk (Imap port: 993, POP3 port: 995) Outgoing server: mail.mydomain.dk (SMTP Port: 465) The settings work fine, except that many mail clients will show a warning while connecting, the reason for the warning is that the certificate for the host server (whmhost1.somedomain.dk) is returned instead of the certificate for mail.mydomain.dk. When I look at "[COLOR=rgb(51, 51, 51)]Manage SSL Hosts" I can see that there is a certificate for the domain at "mail.mydomain.DK" (Along with cpanel, webdisk webmail subdomains.) My server is running CENTOS 6.9 WHM v68.0.29

• 

  cPanelMichael

  • February 19, 2018 16:16

  Hello, Can you open a support ticket using the link in my signature so we can take a closer look? Thank you.

  0
• 

  karlog

  • February 27, 2018 20:27

  The issue was solved by cPanel support. The reason for the issue was that the server was using a newer version of SSL than what was supported by Outlook and Thunderbird.

  0

Please sign in to leave a comment.