SSL Install

manopb

Perch
I am having problems installing a SSL Cert for a domain alias "secure.mydomain.com" and support is telling me that what I have for an alias needs to be a sub-domain. The problem is that I have multiple directories that need to be covered by the Cert and can't place all of the "secure" folders under one. Part of the site is fusebox (store) and other areas are not, however there are "secure" areas in each. I have created the alias with no problem and the Cert seems to install correctly using the alias, but when I click to edit the SSL Cert to see the domain listed, it only shows "mydomain.com"

I have done this with another client I host here at JodoHost and had no problems creating the alias and installing the Cert using that alias and when I click to edit the SSL Cert it lists "secure.thatdomain.com".

The site I am having problems with is currently live on another hosting server, and I can't see pointing the domain to the JodoHost server until the SSL Cert is installed correctly.

Has anyone else run into this problem before?

Refference Email support ticket #48760
 
The CSR was made using "secure.mydomain.com" as the common name or Fully Qualified Domain Name. The problem is that the server will not list the alias selected and used to install the cert. When going in to edit the SSL in the control panel it list the regular domain name (mydomain.com) and not the alias (secure.mydomain.com), as it does in my other clients control panel.

The SSL is functional and working now on another hosting server.
 
Edit:

Just to get this right, you are using the same cert as at a different provider and did not use a new CSR from here?
 
That is correct and the private key was extracted by JodoHost support from the .pfx file generated from the other hosting provider. I have migrated domains and the existing SSL Cert using the info from the .pfx before with no problems.

The Cert was originally installed on the JodoHost server by JodoHost support, and I assume it was installed using the regular domain name "mydomain.com", not using the required alias.
 
Ok, the domain https://secure.yourdomain.com works perfectly, as well as the domain.com working properly, hsphere does not by default support SSL just on a server alias, but it is working fine.

Can you please explain what the problem is?

Edit: you cant have secured images outside the secure.domain.com as it would give errors, you need a wildcart cert for that to even be possible. It has always been this way with ssl certs.
 
If you went to the domain in question, it works perfectly because the domain is still pointed to the old name server for the other provider. I am trying to get this worked out prior to updating the domain at the registrar for a smooth change over.
 
Back
Top