SNI looks interesting. We set up this using a SAN cert and info from
http://blog.revolunet.com/index.php/reseau/administration/hosting-multiple-ssl-vhosts-on-a-single-ipportcertificate-with-apache2
Regards,
Jason
On 21 Aug 2009, at 16:35, Jerrad Pierce wrote:
> Hmm, actually it looks like Apach
Hmm, actually it looks like Apache just picked up SNI a few months ago in 2.3
--
Cambridge Energy Alliance: Save money. Save the planet.
___
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
Community help: http://wiki.bestpractical.com
On Fri, Aug 21, 2009 at 11:09, Curtis Bruneau wrote:
> Each SSL site pretty much needs to be on it's own IP address, the
> reasoning is the cert negotiation isn't name based header as apache
> would. The only other way would be to have them on different ports but
> then you'd have to specify the po
I tried and the second one
but still https://rt.hostname.com goes to https;//firstone
While restarting apache, the warning message now was:
[Fri Aug 21 11:20:23 2009] [warn] VirtualHost firstname:443 overlaps with
VirtualHost rt.hostname.com:443, the first has precedence, perhaps you need
a Name
Try naming the virtual hosts. *:443 means any domain that resolves to that
machine will get the first one, since it matches.
Curtis may also be right (never tried two https sites on the same box), but
try having the first one be and the second one
and see if it works for you.
On 8/21/09 11:1
Actually, I should have mentioned before that our rt installation is on a
different IP.
On Fri, Aug 21, 2009 at 11:09 AM, Curtis Bruneau wrote:
> Each SSL site pretty much needs to be on it's own IP address, the reasoning
> is the cert negotiation isn't name based header as apache would. The onl
Each SSL site pretty much needs to be on it's own IP address, the
reasoning is the cert negotiation isn't name based header as apache
would. The only other way would be to have them on different ports but
then you'd have to specify the port when going to the site.
testwreq wreq wrote:
> *
> I h
* I have managed to get it all set up and RT running OK with named virtual
host over http. However, I am having problems with getting them to work over
https. When I set a virtual host name, it always serves the first listed
domain. See settings below. https:firstone serves the correct folder, but
