Hi,
So I have an apache 2.2.15 box running on CentOS 6.4. It took me a while
to get it fine-tuned the way I want, but I eventually got there. So I buy
a certificate, redirect from http to https, and it seems to be working
perfectly. That was about six weeks ago.
This morning, I head into the o
> NameVirtualHost *:80 ##$ fine
>
> ##$ << you need *:80 here !
All right! It seems to be working, and I am confused, since I could have sworn
that that was my configuration.
Anyway, many thanks!
J.
> Okay, if you're not doing ssl on domain2 then, no, that's not related. I
> thought maybe from the post title that you were asking about virtual hosts
> for ssl and that gets complicated depending on exactly what you're trying to
> do.
Guys, coming back at you with this, as I still can't get
Le 1 octobre 2013 à 22:25, Eric Covener a écrit :
> Don't use domains or IP addresses inside or
> NameVirtualHost. It's causing two sets of name-based vhosts. Use
> *:80.
Hi,
When I did that, and restarted the server and then went to my URL, I got a
warning about the certificate not being ap
nd that gets complicated depending on exactly what you're trying to
> do.
>
>
> On Tue, Oct 1, 2013 at 11:57 AM, John McIntyre wrote:
> Hi,
> Thanks for that. Unfortunately, even after the changes, entering domain2.com
> on a browser still goes directly to domain1.com
01, 2013 at 04:25:05PM +0100, John McIntyre wrote:
> > Am I doomed to failiure, or is what I'm trying to do, actually possible?
>
> No, you are almost there. The problem is that for some reason you have
> an asterisk in your VirtualHost declaration for domain2. Change that the
Hi,
I have an apache 2.2.15 instance running on a CentOS 6.4 server.
This server is (or will be, if I ever get it working...) two domains. One
of them has an SSL certificate, and one doesn't. I've been struggling with
this for two days solid, and if my research is correct, then the SSL
handshake
