I found the problem, but can't explain it.
In my original site-specific .conf file I had a directory block giving
access to a directory that does not exist. It was a holdover from the
old system that was not duplicated/replicated on the new one. The odd
thing is that Apache didn't complain about t
;On 02/04/2015 08:19 PM, Steve Matzura wrote:
>> I've taken a copy of a site-specific configuration that worked on a
>> 2.2 server and applied it, with changes reflecting different directory
>> names, to a 2.4 server. The 2.4 machine lets me into the protected
>> area wi
I've taken a copy of a site-specific configuration that worked on a
2.2 server and applied it, with changes reflecting different directory
names, to a 2.4 server. The 2.4 machine lets me into the protected
area without asking for login credentials. I've sent a copy of the
.conf file I'm using to Er
On Sun, 1 Feb 2015 17:45:14 -0500, you wrote:
>On Sun, Feb 1, 2015 at 5:21 PM, Steve Matzura wrote:
>> If it didn't match, wouldn't httpd -t kick it back as a mismatch? I
>
>No, it doesn't know at startup that no URL will be mapped below this directory.
Well here&#
ctory
for the private area. There are two separate areas, one public, one
private. The public one, which I didn't show, works fine. The private
one, which is the one I did show, does not ask for the password in
.htpasswd.
>On Sun, Feb 1, 2015 at 2:15 PM, Steve Matzura wrote:
>> On
e or password is asked for.
>On Sun, Feb 1, 2015 at 11:55 AM, Steve Matzura wrote:
>> Upon re-reading this message, I find there was something about which I
>> was extremely unclear and ambiguous. I said that the access to the
>> password-protected area wasn't working,
Upon re-reading this message, I find there was something about which I
was extremely unclear and ambiguous. I said that the access to the
password-protected area wasn't working, but failed to specify just
what wasn't working. The problem is that Apache isn't asking for the
password, and letting any
I maintain a 2.2 server and am building a 2.4 one. I have a file in a
sites-enabled directory containing all the directives I need to define
security for my open and password-protected directories. There is an
"include" directive in the master configuration file
/etc/httpd/conf/httpd.conf. httpd -t
Yeah. The whole thing is a bloody mess! Will work it out later this
morning. I wonder why my FF shows the raw IP address but yours
doesn't. Strange.
On Sun, 09 Nov 2014 22:51:52 +0100, you wrote:
>On Sun, 09 Nov 2014 10:46:36 -0500, you wrote:
>
>> It changes from the very first access request. G
Oh how strange. In Internet Explorer, you're right, but in Firefox, it
shows the IP address. Wonder how *THAT* is.
On Sun, 9 Nov 2014 11:09:05 -0500, you wrote:
>On Sun, Nov 9, 2014 at 10:46 AM, Steve Matzura wrote:
>> It changes from the very first access request.
On Sun, 9 Nov 2014 08:19:23 -0500, you wrote:
>On Sun, Nov 9, 2014 at 1:22 AM, Steve Matzura wrote:
>> 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 when I browse to the
>> URL of the named virtual ho
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 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
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
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 keep
ncludes?
>On 11/06/2014 10:14 PM, Steve Matzura wrote:
>> It occurred to me that apache2.conf might be what's wanted. Here it
>> is, without the comments, and lots of white space removed.
>>
>> ServerRoot "/etc/apache2"
>> LockFile /var/lock/apache2/accept
It occurred to me that apache2.conf might be what's wanted. Here it
is, without the comments, and lots of white space removed.
ServerRoot "/etc/apache2"
LockFile /var/lock/apache2/accept.lock
PidFile ${APACHE_PID_FILE}
Timeout 300
KeepAlive On
MaxKeepAliveRequests 100
KeepAliveTimeout 15
Sta
I did. Here it is again. Actual domain names obfuscated to preserve
anonymity.
ServerName www.domain1.com
ServerAlias domain1.com *.domain1.com
DocumentRoot /webfiles-root/www/domain1.com
ServerName www.domain2.com
ServerAlias domain2.com *.domain2.com
DocumentRoot /webfiles-root/www/domain2.c
I've swung my second domain over to the first address. The first
domain URL still works, but the second newly added address does not.
What happens is that when browsing to the new address, the correct
server responds, but the default document root is used. This indicates
to me that I've specified s
I did, and it worked. I just don't know if it will server the other
domain yet. Waiting for DNS catch-up.
On Thu, 06 Nov 2014 11:02:13 -0600, you wrote:
>What happens if you omit the NameVirtualHost directive?
>
>On 11/06/2014 10:56 AM, Steve Matzura wrote:
>> On Thu, 06 Nov
I got to thinking, if I have a mismatch, what if I remove the
NameVirtualHost line? I did, and the error went away. Now I have to
test it to see that the second domain will be server by name.
On Thu, 6 Nov 2014 11:33:42 -0500, you wrote:
>On Thu, Nov 6, 2014 at 11:22 AM, Steve Matzura wr
On Thu, 06 Nov 2014 10:30:32 -0600, you wrote:
>Try giving NameVirtualHost 0.0.0.0:80 or the actual ip:80. Not sure if
>it will change anything, but its worth the 10 seconds it will take to
>implement.
Sorry, same error, just substituting * with either 0.0.0.0 or the
actual address.
---
t;try this to test your virtual host config.
>
>#apache2ctl -S
>
>On 11/06/2014 09:43 AM, Steve Matzura wrote:
>> When restarting the server with 'apache2ctl restart', or when using
>> the -t option to check the syntax of files, I get the following after
>> the
On Thu, 6 Nov 2014 11:06:06 -0500, you wrote:
>On Thu, Nov 6, 2014 at 10:43 AM, Steve Matzura wrote:
>> NameVirtualHost *:80
>
>
>You probably have two or more of these, you only want 1.
How does that jibe with the article saying I need a blo
OK, the bad news is, apachectl didn't work, but the good news is that
apache2ctl did. The server restart fine with a 0-length httpd.conf.
See next message for new problem.
-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.o
When restarting the server with 'apache2ctl restart', or when using
the -t option to check the syntax of files, I get the following after
the current date-and-time stamp:
[warn] NameVirtualHost *:80 has no VirtualHosts
Before I added anything to httpd.conf, it was empty--a 0-length
file--which I
I'm running version 2.2 on a Debian 4 system (OK, don't laugh please).
It's been running swell for years. And before anyone says the answer
to life, the universe and everything is to upgrade to 2.4, that's
already been done on a test bed, and yes, I'm having the same problem
over there. It's this:
29 matches
Mail list logo
