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
On Tue, Oct 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
the actual IP ad
Well, question is, are you trying to have domain2.com *also* do that same
http->https ( http://domain2.com to https://domain2.com )? If so, do you
have separate certificates for each (domain1 and domain2)?
On Tue, Oct 1, 2013 at 10:36 AM, Pete Houston wrote:
> On Tue, Oct 01, 2013 at 04:25:05P
Hi,
Thanks for that. Unfortunately, even after the changes, entering domain2.com
on a browser still goes directly to domain1.com.
No, I don't have any intention to do SSL on domain2.com. Is this causing a
problem?
D.
Le 1 octobre 2013 à 17:29, Nick Tkach a écrit :
> Well, question is, are
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.
On Tue, Oct 1, 2013 at 11:57 AM, John McIntyre wrote:
> Hi,
> Tha
So I'm still unable to serve that domain2.com :(
Le 1 octobre 2013 à 18:04, Nick Tkach a écrit :
> 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 depen
Don't use domains or IP addresses inside or
NameVirtualHost. It's causing two sets of name-based vhosts. Use
*:80.
On Tue, Oct 1, 2013 at 4:06 PM, John McIntyre wrote:
> So I'm still unable to serve that domain2.com :(
>
>
>
>
> Le 1 octobre 2013 à 18:04, Nick Tkach a écrit :
>
> Okay, if yo
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
On Wed, Oct 2, 2013 at 1:35 AM, John McIntyre wrote:
> 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 wen
> 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
On Sat, Oct 5, 2013 at 3:22 PM, John McIntyre wrote:
>
> 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.
>
>
>
Ok, I had similar problems. When seeing your original config, it triggers
following comments (after ##$) from me:
NameVirtualHost *:80 ##$ fine
##$ << you need *:80 here !
ServerAdmin r...@domain1.com
DocumentRoot /var/www/html
ServerName domain1.com
ErrorLog /var/log/http
> 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.
13 matches
Mail list logo
