[Wylug-help] setting up Apache for virtual hosts for LAN only access

[mikeb at gbdirect.co.uk]

On Wed, Dec 22, 2004 at 06:31:33PM +0000, Mike wrote:

> After a deathly wall of silence on the SSL question, can anyone help
> with the following? I am trying to set up virtual hosts on Apache 1.3.33
> to serve for testing purposes 4 web sites (number could grow). I've read
> loads of stuff, hard copy and on the web, including the manual. I'm
> trying to set it up so I can view the
> sites from either of the other two machines on the network, but not to
> go out to the public. After a lot of messing about, I've got as far as
> the following error message when using test.php, which at least is
> showing the script to be where I put it!:
>
> Warning: Unknown(/usr/local/web/vhost/test.php): failed to open stream:
> Permission denied in Unknown on line 0

Is the php file readable by Apache? Apache will be running as user www or
something like that and there may be a permissions issue. Make the file
world readable. That will also be needed for directories in the path
of course.

> I made the directories in /usr/local/ from /web onwards myself, because
> in spite
> of what the manual says there was not one there. Web browsing has told
> me that those directories often come under /var/www/ but, although that
> directory exists, none of the files or directories I am led to believe
> should be there are actually there!

They won't be if you build Apache from source, but that's a rare thing to
have to do nowadays. What's the DocumentRoot setting in httpd.conf? That's
what determines where those files need to be.

>
> Oh, yes, there is one more thing: If I type into the browser command
> line something like http://nameofsubdir I get the following URL
> appearing:
> https://exchange.1and1.com/exchweb/bin/auth/owalogon.asp?url=https://exchange.1and1.com/exchange&reason=0
> How on earth do I get M$ sticking its ugly snout in? And not an M$
> programme in site on my machine!

Did you really type just http://nameofsubdir rather than
http://someserver/nameofsubdir?

If you don't put a server name in there you'll get whatever your browser does when
it can't resolve a DNS name - maybe a redirect to some other site.