Hi guys,
Having some trouble to get a SSL cert working on our server for accessing cpanel/WHM.
Installing the SSL cert itself wasn't a big deal. Done that hundreds of times for 'normal' domains, but this now keeps me stumped:
Let's say our server has the IP 123.123.123.123 and we used to log in via
https://123.123.123.123:2087 to get to WHM. Normally the browser would come up with the big warning that the side is not trusted etc etc and we just added an exception. But now we are starting to let clients access their cpanel accounts and we normally would give them the address
https://123.123.123.123:2083 to log into cpanel. Of course clients then will get the same security warning, which we would like to avoid.
After a bit of research and consultation with RapidSSL (thats where we get our SSLs from), I found out that you can't get SSL certs for IPs. Fair enough. So what about our domain name? Lets say the server behind above IP is called
server1.mydomain.com
Logging in via
https://server1.mydomain.com:2087 works fine so I installed an SSL cert for that domain name. Installation of the cert worked fine. Browsing to https://server1.mydomain.com (without the portnumber) comes up with the nice padlock we want. No security warning.
BUT, and thats where I get lost, if I type in https://server1.mydomain.com:2087 to login to WHM, no padlock and the security warning again.
What am I doing wrong?
Cheers,
Bjorn
Having some trouble to get a SSL cert working on our server for accessing cpanel/WHM.
Installing the SSL cert itself wasn't a big deal. Done that hundreds of times for 'normal' domains, but this now keeps me stumped:
Let's say our server has the IP 123.123.123.123 and we used to log in via
https://123.123.123.123:2087 to get to WHM. Normally the browser would come up with the big warning that the side is not trusted etc etc and we just added an exception. But now we are starting to let clients access their cpanel accounts and we normally would give them the address
https://123.123.123.123:2083 to log into cpanel. Of course clients then will get the same security warning, which we would like to avoid.
After a bit of research and consultation with RapidSSL (thats where we get our SSLs from), I found out that you can't get SSL certs for IPs. Fair enough. So what about our domain name? Lets say the server behind above IP is called
server1.mydomain.com
Logging in via
https://server1.mydomain.com:2087 works fine so I installed an SSL cert for that domain name. Installation of the cert worked fine. Browsing to https://server1.mydomain.com (without the portnumber) comes up with the nice padlock we want. No security warning.
BUT, and thats where I get lost, if I type in https://server1.mydomain.com:2087 to login to WHM, no padlock and the security warning again.
What am I doing wrong?
Cheers,
Bjorn