Discussion in 'General' started by alexillsley, Apr 9, 2007.
----- expired ----
You basically share the host's certificate.
Google SHSS and/or shared SSL.
I guess they're using a wildcard certificate (like here: http://www.instantssl.com/ssl-certificate-products/ssl/wildcard-ssl-premiumssl_wildcard.html )
This works only for subdomains of the same domain.
Try this link for more info..
I do believe this is the only valid solution to share a certificate without getting certificate errors like those sites have.
You can not have individual SSL for every site with one IP, thats a limit of the SSL protocol! The only things you can do is e.g. create one SSL enabled host and use the apache mod_proxy module to access the pages in the form:
or you use the wildcard solution that falko suggested.
It's possible if you don't care about certificate errors, but otherwise it's impossible.
I dont care about certficate errors, how would i do it with cerficate errors?
Forgive me for asking but...
Why would you want to supply invalid SSL services? That kind of defeats the purpose of SSL. Nobody in their right mind would install the CA Root if certificate errors are present.
In any case, try enabling SSL for your sites and put the same certificate, etc on all sites. That might work.
SSL encrypts the data between you and thge server with or without a vaild certificate
What would i do to ispconfig or what would i add to the virtual hosts to enable this ?
But your customers and their customers care and nobody will use sites with invalid certificates. If you have customers that run e.g. a online shop, nobody will give them their credit card data when the SSL cert is invalid.
It doesnt matter, i just need to get SSL to work.
Lots of companys do it, all sites on [link_expired] have invalid certificates
SSL is only supported on paid hosting at awardspace.
Shared SSL for them IS sitename.awardspace.com. Do some investigation, that is how it is.
That is why all sites there have invalid certificates on non-SSL supported sites. And the error is there to alert people NOT to give sensitive information to that site.
I really doubt that you will receive any help on setting up invalid SSL. This is something you need to do on your own. And I'm sorry if that's too strong of a way to word it, but that's the way I see it.
All awardspace sites have invalid certficates! [link_expired]
I just need to get SSL working,
See http://www.onlamp.com/pub/a/apache/2005/02/17/apacheckbk.html .
This should work, but as you already know, users will still get browser warnings. As the article states, SSL is two part--encryption and authentication. From what I understand, you will get the encryption part, but not the authentication. Your users may or may not trust the connection (as Till mentioned).
Doesn't the new version of Apache now support multiple SSL cert's on the same IP? I would imagine it would have to be built in to ISPConfig to make it work. Also browsers have to be updated to support this also from what I read.
No. This doesn't have anything to do with Apache or ISPConfig. The restriction "one cert per IP" is set by the way how the HTTPS protocol works. There's nothing you can do about it.
Separate names with a comma.