So the other day I was doing some work in WHMCS (managing billing) and all of a sudden all my sites went down. VPS was still up and I found that httpd was simply no longer running anymore. Everything else seemed to be up but httpd was missing from the process list.

I restarted (well started, it said it wasn't running) apache and the sites all came back.

Now its a few days later and I tried to use my shared cert to access my whmcs and I get the expected site mismatch warning, but then after I accept the cert, I get the generic cpanel/apache welcome message.

Any ideas why I'm not getting the site?

Thanks!

depends on which website you have installed your ssl cert. Usually shared ssl is used by accessing https://sslinstalleddomian.com/~user or similar methods

To install SSL certificate, you need a dedicated IP for your site first.

It seems that your shared ssl cert is expired. You will have to re-new the cert using WHM.

It could be ether, You didn't install it on a Dedicated IP or you have to renew it in WHM control panel. Have you found a solution?

According to WHM, the shared cert is installed and valid.

Hmm, I think activelobby4u might have hit it.. maybe I was mistaken in remembering using the shared cert in the way I was trying to (directly using the domain instead of the host name the shared cert is registered to)

I just don't ever remember getting the default server page. Is there something I should do to redirect https traffic when there is no cert for that domain?

Thanks for all the replies!

May be getting dedicated SSl is better idea instead using shared.

Agreed, for the prices of some basic SSL certs these days it is very much worth it to switch from a shared SSL cert.

Agreed, for the prices of some basic SSL certs these days it is very much worth it to switch from a shared SSL cert.

Well said, Rapid SSL can be a choice too for low cost. Shared SSL often bring crappy issues.