Any SSL Guru's?

[Linkin]

If any of you are SSL guru's, I would appreciate any suggestions you may have. I am having an issue with a cert bought and installed. We have installed using the same cert vendor (geotrust) and on this particular server with no issues before.

The cert was ordered for client.mysite.com as the hostname. Went through the purchase process as normal, installed as normal and everything was smooth for that.

When you try to access the domain with the secure URL (https://client.mysite.com) it takes you to https://mysite.com.

Before we even created the csr, I moved the site to it's own IP (even though the old IP had no SSL certs on it, just being safe).

Here is a copy of what it returns when we install it, as e have done it three times now just to be sure:

Attempting to verify your certificate.....
Cerificate appears to be intact
/usr/share/ssl/certs/client.mysite.com.crt.test: OK

The CRT for the domain client.mysite.com was installed on the ip 64.191.**.**.

Then Httpd restarts as normal.


Any ideas what is happening to cause it to go to the main area instead of the subdomain it was created with?

Thanks for your help.

[soapsud]

are you sure there isn't some sort of redirect in place notwithstanding the actual cert? if it's connecting properly (ie, doesn't shoot errors of wrong hostname, etc...) it sounds like the SSL cert is fine?

[projo]

Not a SSL guru but:

Have you done subdomains on that domain before?

Could there be a wildcard ('*') in the httpd.conf for the domain.
Even if you have done subdomains on a domain before I have
found that a wildcard can supercede some subs but not others, depending on order of listing in httpd.conf.

Is the IP for the domain or just the subdomain? What about wildcard entries in the nameserver entry for the domain?

Gary

[Linkin]

Originally posted by soapsud:

are you sure there isn't some sort of redirect in place notwithstanding the actual cert? if it's connecting properly (ie, doesn't shoot errors of wrong hostname, etc...) it sounds like the SSL cert is fine?

That was my initial thought so I checked re-directs and there are none.

Then I thought it might be the software being used, clientexec as in setup there is an option for the URL. It was set to non-secure, so I changed it to https://client.mysite.com in there and it returns a 404 when it tries to access the various sections under the https urls. If you change the URL once logged in to a plain http, it works fine, but obviously outside the secure format.

[Linkin]

Originally posted by projo:

Not a SSL guru but:

Have you done subdomains on that domain before?

Could there be a wildcard ('*') in the httpd.conf for the domain.
Even if you have done subdomains on a domain before I have
found that a wildcard can supercede some subs but not others, depending on order of listing in httpd.conf.

Is the IP for the domain or just the subdomain? What about wildcard entries in the nameserver entry for the domain?

Gary

We haven't installed any certs on subdomains of this site before. The ip is for the domain.

I'll have to look at httpd.conf although I don't think a wildcard has ever been used w/this domain.

[Linkin]

Figured it out, in the httpd.conf file, the document root was set to public_html without the subdomain.

Thanks for your help!

[projo]

Good.
Thanks for following up.