System Wide Shared SSL trouble...

[kamino]

Hello,

I bought QuickSSL certificate with GeoTrust.
I installed it as requested in the very good jlasman's howto thread.

The domain I have setup with the main server IP is ssl01.kamino.eu.com.

It works perfectly for domain ssl01.kamino.eu.com except that shared ssl doesn't work for the users accounts... In other words users can not access https://ssl01.kamino.eu.com/~username .

Users can only access their sites with shared ssl with the IP:
https://216.32.94.19/~username

Probably I missed up something, but what ? Did someone experienced this before ?
Any ideas to solve it ?

Thanks for help

 

[kamino]

Hello,

I found the solution

According the howto:

1) Logged in to the DA control panel as admin, we set up a domain in the user control panel, using the main server IP#. We named the domain "secure.example.com".

I certainly missunderstood...

Actually you can create the secure domain name logged as admin, in the "DNS Administration" menu, at the admin level.

And then it works

Regards,

 

[nobaloney]

My HowTo includes setting up the domain space on the server to put directory space for shared SSL.

If you're going to use the server hostname and something like https://hostname.example.com/~username for your shared SSL certificates, your method would work.

But we want to use: https://secure.example.com/domain.name (where secure is NOT the hsotname and domain.name is the complete domain name, not the username. We just like it better our way .

Jeff

 

[kamino]

My HowTo includes setting up the domain space on the server to put directory space for shared SSL.

...

we want to use: https://secure.example.com/domain.name (where secure is NOT the hsotname and domain.name is the complete domain name, not the username. We just like it better our way .

That was exactly what I missunderstood:
I was thinking the howto should make the hostname secure... Then I found this solution...

Now that I understand what I missunderstand earlier I agree with you, https://secure.example.com/domain.name looks better
than https://secure.example.com/~username !

Regards,