Scenario:
My server's main IP is 123.123.123.123
So my Plesk entry is on IP 123.123.123.123:8443
I have host.mydomain.com as hostname
So, obviously the hostname is nested on the domain mydomain.com
Mydomain.com is hosted on the main IP 123.123.123.123
As the result my entery to Plesk shows https://host.mydomain.com:8443
Problem:
I ordered a starterSSL for mydomain.com, thinking that by applying the certificate to mydomain.com I can automatically certify the Plesk entry, which uses the same IP, and the hostname that is related to mydomain.com
I installed the certificate, and spent a whole lot of time trying to figure out why it not only fail to work on host.mydomain.com:8443, but also fail on https://www.mydomain.com. Read all documentation from Plesk and every thread here, and finally gave up and sent in a ticket.
The answer from EV1 support came as that I could not use the certificate for mydomain.com if it is hosted on the main IP, and that I must host mydomain.com on an additional IP if I wanted to apply the certificate on this domain.
OK. I am a little confused here. First, if I host mydomain.com on an additional IP, how could that cover the Plesk entry on a different IP?
Second, if I host mydomain.com on a different IP, how does it effect the hostname, host.mydomain.com, that is, to my understanding, pointing to the server IP? Since mydomain.com will be on 567.567.567.567, would I need to make the 'A' entry for host.mydomain.com back to the server IP 123.123.123.123?
Ultimately, my question is, what is the proper procedure to apply an SSL certificate to Plesk's entry so that the customers won't see that security warning when accessing Plesk?
Hope someone can help.
Sam