Atomicorp

So not being the smartest at understanding why and how when you install a SSL in plesk for the CP that it does'nt make it the server wide ssl is causing me a problem. Basically i have a new server that i have started migrating customers to already and the problem i have is that we have a wildcard ssl for the CP which also has the same name as the host ex. *.domain.com . What i need to do and don't understand how to do it is i need the *.domain.com cert to cover the CP which it is doing correctly but if i hit any other port other than the plesk admin login at 8443 i get the plesk/self issued cert.

See if i go to the CP login https://ecsi2.ecsihosting.com:8443 the cert works properly but if i go to any other port ex. port 30000 for the ASL web login i get the self issued cert for the hostname of the box.

How do i make the wildcard ssl cover the whole server and not just the plesk CP login at port 8443?

You actually have two or three different webservers running on your server, and each one needs to have the SSL certificate in place. The different ports represent different webservers.

Plesk has its own webserver listening on 8443.

The ASL GUI has its own separate one on 30000.

[ And the "main" apache webserver for client sites is on 80 (non-ssl) and 443 (ssl) ]

You have done the Plesk one. That's good. There's a feature request somewhere asking if the ASL GUI could use the same SSL cert as installed in Plesk, but for now it is necessary to manually install your certificate separately for the GUI (I think?).

You probably also have a hosting account set up for www.ecsihosting.com which you may also want covered by the wildcard certificate. Plesk makes it easier here because it allows you to use an SSL you have already installed to cover the control panel to also cover a hosting account, so it is then just a matter of selecting the right certificate in the right place. I think. I could be wrong about this you know. I don't remember the details so I can't be sure.

Faris.