On 05/14/16 18:19, Frank Gingras wrote:
On 14/05/16 07:53 PM, phil wrote:
On 15/05/2016 6:16 AM, Beech wrote:
Forwarded Message
Subject: Re: [users@httpd] Virtual Host Not working
Date: Sat, 14 May 2016 21:46:41 +0200
From: miguel gonzalez
To: Beech , users
On 14/05/16 07:53 PM, phil wrote:
On 15/05/2016 6:16 AM, Beech wrote:
Forwarded Message
Subject: Re: [users@httpd] Virtual Host Not working
Date: Sat, 14 May 2016 21:46:41 +0200
From: miguel gonzalez
To: Beech , users@httpd.apache.org
I always have used either the ip
On 15/05/2016 6:16 AM, Beech wrote:
Forwarded Message
Subject: Re: [users@httpd] Virtual Host Not working
Date: Sat, 14 May 2016 21:46:41 +0200
From: miguel gonzalez
To: Beech , users@httpd.apache.org
I always have used either the ip address or the wildcard * in the
Forwarded Message
Subject: Re: [users@httpd] Virtual Host Not working
Date: Sat, 14 May 2016 21:46:41 +0200
From: miguel gonzalez
To: Beech , users@httpd.apache.org
I always have used either the ip address or the wildcard * in the
virtualhost directive.
Have you checked
I always have used either the ip address or the wildcard * in the virtualhost
directive.
Have you checked the logs?
Beech wrote:
>I have added a new virtual domain and it's not working. No error
>messages, just won't connect. I have triple checked the paths and
>spelling. DNS is propagated a
I have added a new virtual domain and it's not working. No error
messages, just won't connect. I have triple checked the paths and
spelling. DNS is propagated and dig returns the correct IP. The other
domains work. Here's the setting, it's Apache24:
ServerAdmin akbe...@gmail.com
Docu
My goodness, that worked! I am blown away! Thank you very much for
your help with this.
Jim
On 2/12/2014 2:58 AM, Tom Evans wrote:
On Mon, Feb 10, 2014 at 10:24 PM, Jim Borland wrote:
My server, which is located in the Amazon cloud, was just moved to a new
location with a new IP address.
On Mon, Feb 10, 2014 at 10:24 PM, Jim Borland wrote:
> My server, which is located in the Amazon cloud, was just moved to a new
> location with a new IP address. Nothing else was changed. However, the
> Apache Virtual Host, which has worked flawlessly for several years, is
> broken. Apache serve
My server, which is located in the Amazon cloud, was just moved to a new
location with a new IP address. Nothing else was changed. However, the
Apache Virtual Host, which has worked flawlessly for several years, is
broken. Apache server version is: Apache/2.2.16 (Ubuntu).
I went to my DNS ho
