Now my named virtual host is working correctly, I've another problem,
and I think this is an easy one. It's just a matter of what "flavor,"
if you will, of the directive to use.
On the site hosting the A-record for my server, the A-record address
is what shows up in the address bar of a browser wh
Edgar, Eric, et al.:
All problems solved. For what reason I don't know, I did not need a
VirtualHost block in httpd.conf for the main address. It may already
have been defined in the main config file apache.conf, but when I
removed the globalvoice.info block from httpd.conf and re-inserted the
Nam
On Sat, 08 Nov 2014 12:49:18 -0600, you wrote:
>Make a backup copy of your httpd.conf:
>
>cp /path/to/httpd.conf /path/to/httpd.conf.bk
>
>and replace with the attachment and see what happens.
I'll have to do some minor editing because our document root paths are
quite different than the defaults
On 11/08/2014 01:58 PM, Steve Matzura wrote:
> On Sat, 8 Nov 2014 13:39:07 -0500, you wrote:
>
>> On Sat, Nov 8, 2014 at 12:53 PM, Steve Matzura wrote:
>>>
>> Don't put a hostname there. Use *:80 throughout if you don't care what
>> local interface was used (you don't).
> I tried that and it's s
On Sat, 8 Nov 2014 13:39:07 -0500, you wrote:
>On Sat, Nov 8, 2014 at 12:53 PM, Steve Matzura wrote:
>>
>
>Don't put a hostname there. Use *:80 throughout if you don't care what
>local interface was used (you don't).
I tried that and it's still not right. Give it a try.
>That's why theglobalvo
On 11/08/2014 12:39 PM, Eric Covener wrote:
> On Sat, Nov 8, 2014 at 12:53 PM, Steve Matzura wrote:
>>
> Don't put a hostname there. Use *:80 throughout if you don't care what
> local interface was used (you don't).
>
> That's why theglobalvoice.info steals all of your requests. It
> resolves to
On Sat, Nov 8, 2014 at 12:53 PM, Steve Matzura wrote:
>
Don't put a hostname there. Use *:80 throughout if you don't care what
local interface was used (you don't).
That's why theglobalvoice.info steals all of your requests. It
resolves to the IP address all of your vhosts use, but is an exact
Edgar:
On Sat, 08 Nov 2014 11:09:36 -0600, you wrote:
>I have a feeling the answers to your problems can be found in:
>
>Include /etc/apache2/conf.d/
Nothing in there worth including except mailman.conf and
squirrelmail.conf. Unless you want the security file, too.
>Include /etc/apache2/sites-e
On 11/08/2014 11:00 AM, Steve Matzura wrote:
> Eric:
>
> On Sat, 8 Nov 2014 11:37:31 -0500, you wrote:
>
>> On Sat, Nov 8, 2014 at 11:30 AM, Steve Matzura wrote:
>>> I suspect my old installatioin of Apache 2.2.4 is buggered. There is
>>> absolutely no httpd program anywhere on the system, and th
Eric:
On Sat, 8 Nov 2014 11:37:31 -0500, you wrote:
>On Sat, Nov 8, 2014 at 11:30 AM, Steve Matzura wrote:
>> I suspect my old installatioin of Apache 2.2.4 is buggered. There is
>> absolutely no httpd program anywhere on the system, and the official
>> documentation keeps telling me if I use:
>
On Sat, Nov 8, 2014 at 11:30 AM, Steve Matzura wrote:
> I suspect my old installatioin of Apache 2.2.4 is buggered. There is
> absolutely no httpd program anywhere on the system, and the official
> documentation keeps telling me if I use:
>
> httpd -S
Debian chose a different name. Use apachectl
Apollogies for having taken so long to reply with updated status.
I suspect my old installatioin of Apache 2.2.4 is buggered. There is
absolutely no httpd program anywhere on the system, and the official
documentation keeps telling me if I use:
httpd -S
I can get an analysis of what's going on i
12 matches
Mail list logo
