Secure access to WHM/cPanel

[daimpa]

Hello, I've a paid SSL certificate installed on my domain. It's not wildcard. So I can't enable autossl for cpanel/whm, and when I try to login to both control panels I receive the "not secure connection" alert. I'm accessing them via example.com/cpanel or example.com/webmail. Are these connections secured with SSL? How can I have access to cpanel/whm in the safest way possible?

Thanks

 

[cPanelLauren]

Hello,

Hello, I've a paid SSL certificate installed on my domain. It's not wildcard. So I can't enable autossl for cpanel/whm

AutoSSL will not replace certificates not issued by AutoSSL unless you request this specifically. None the less, you are able to exclude specific domains from autoSSL so you can indeed enable this if you'd like, just exclude the domains that already have a certificate

I'm accessing them via example.com/cpanel or example.com/webmail. Are these connections secured with SSL? How can I have access to cpanel/whm in the safest way possible?

This should be secured by the domain's SSL certificate if not what is set for SSL Redirect Destination in Tweak Settings and/or when you go to domain/tld is the URL changed when you are on the webmail login page?

 

[daimpa]

AutoSSL will not replace certificates not issued by AutoSSL unless you request this specifically. None the less, you are able to exclude specific domains from autoSSL so you can indeed enable this if you'd like, just exclude the domains that already have a certificate

[CPANEL-22039] AutoSSL doesn't cover Service Subdomains when parent domain uses third-party cert

I refer you to an older thread (1 year old) Paid SSL on Domain, Free AutoSSL on Subdomains? I needed a paid SSL certificate installed for my clients www entry and the client wanted to use AUTOSSL for the service subdomains such as cpanel, webmail etc. because the client didn't want to shell...

forums.cpanel.net

So, has this problem been resolved?

 

[cPanelLauren]

Yes and no - the case was marked as won't fix as a result of in order to change this we would have to do 1 domain per VirtualHost which isn't really realistic. None the less these aren't service subdomains being discussed. A service subdomain is service.domain.tld like webmail.domain.tld not domain.tld/service