Very Computer

I'm having problems with Virtual Hosts. I assigned a virtual host with
www.domain2.com (it shares the same IP as the main server). But ever
since I've done this, every request to the main server (domain1.com)
will place the user in the virtual host's (domain2.com) web directory.
Why is this? If I try to access domain2.com with my browser -- I get to
the correct directory. If I try to access the main server (domain1.com)
however, I get to the document root of domain2.com. Hmm. Any
workarounds?

Oh yeah, just for the record, I got this [warn] in my main apache log
file:

[Sun Jun 28 17:02:59 1998] [warn] NameVirtualHost 206.69.43.160:80 has
no VirtualHosts

When it does have a virtual host right underneath it. Hmm.

Regards,
_______________________________________________________________

 Wiliam Stephens                  Web Developer & Programmer

_______________________________________________________________

Obviously not.

In particular, pay attention to the fact that if an IP is set for a
NameVirtualHost then the main server is not used for that IP.

Of course, you don't even mention the detail of what webserver or version
you are running, but I'm guessing it is Apache 1.3.x.

I'm using Apache 1.3.1 on a Linux Platform. I've read all the Virtual
Host Documentation on the Apache Web Site, and I'm still stumped. What I
need is an example SRM.CONF or HTTPD.CONF file from someone with Virtual
Host Directives set for non-IP based domains. If that's possible?

Quote:> In particular, pay attention to the fact that if an IP is set for a
> NameVirtualHost then the main server is not used for that IP.

Thanks!
_______________________________________________________________

 Wiliam Stephens                  Web Developer & Programmer

_______________________________________________________________

Quote:>Hi Marc,
>I'm using Apache 1.3.1 on a Linux Platform. I've read all the Virtual
>Host Documentation on the Apache Web Site, and I'm still stumped. What I
>need is an example SRM.CONF or HTTPD.CONF file from someone with Virtual
>Host Directives set for non-IP based domains. If that's possible?

Quote:>> In particular, pay attention to the fact that if an IP is set for a
>> NameVirtualHost then the main server is not used for that IP.
>Yikes! I didn't know this. That means then, that I have to have two IPs.
>One for the main server and another for the Virtual Hosts that the
>server will serve? How about making all domains virtual hosts and not
>have a main, dedictaed server? Will this work off one domain?

 Note: When you specify an IP address in a NameVirtualHost directive
 then requests to that IP address will only ever be served by matching
 <VirtualHost>s. The "main server"  will never be served from the
 specified IP address.

Quote:> That means then, that I have to have two IPs.

Quote:> One for the main server and another for the Virtual Hosts that the
> server will serve?

Quote:> How about making all domains virtual hosts and not
> have a main, dedictaed server?

Quote:> Will this work off one domain?

Name-based virtual hosts have to have different host names, at least,
and they have to be DNS-registered.  Whether they are in the same or
different DNS domains isn't relevant.  Or what was your question really?

These examples spell it out pretty clearly:
http://www.apache.org/docs/vhosts/examples.html

john

--

John M. Walley                          Magpies
Webmaster                               You Deserve The Bird

Thanks!

 Wiliam Stephens                  Web Developer & Programmer

_______________________________________________________________

I've now created new Virtual Hosts, each one with their unique IP
address. All is well, IMO. I've set BindAddress to * and all. Anyway,
the problem is now, that none of the Virtual Hosts get served. The
server can't find the server, and requests gets timed out. This is what
the error log said:

[Mon Jun 29 14:35:26 1998] [notice] httpd: caught SIGTERM, shutting down

Any ieads on this error? Any ideas what I'm doing wrong?

Thanks for your help.

Regards,
_______________________________________________________________

 Wiliam Stephens                  Web Developer & Programmer

_______________________________________________________________

Quote:> >Yikes! I didn't know this. That means then, that I have to have two IPs.
> >One for the main server and another for the Virtual Hosts that the
> >server will serve? How about making all domains virtual hosts and not
> >have a main, dedictaed server? Will this work off one domain?

> Exactly.  If you only have one IP, then the concept of a main server
> doesn't work very well for various reasons.  That means you should
> just pretend the main server doesn't exist, and make it a virtualhost.

--
John Heyer :: University of Wisconsin - Madison :: http://heyer.ml.org

Quote:>Hi Folks,

>I've now created new Virtual Hosts, each one with their unique IP
>address. All is well, IMO. I've set BindAddress to * and all. Anyway,
>the problem is now, that none of the Virtual Hosts get served. The
>server can't find the server, and requests gets timed out. This is what
>the error log said:

Try pinging the ip address, to see if your machine is answering.  If
not, you have other issues to work.

Quote:>[Mon Jun 29 14:35:26 1998] [notice] httpd: caught SIGTERM, shutting down

>Any ieads on this error? Any ideas what I'm doing wrong?

You should see another line, like:

[Sun Sep 27 01:01:59 1998] [notice] Apache/1.3.1 (Unix) configured --
resuming normal operations

to tell you the server is running again..... The time stamp is Jun 29,
which would lead me to believe that the actual log file are perhaps
stored in another place.  That or your clock is off.

To see if apache is running, do a ps, and grep for httpd.  Something
like:

ps -aux | grep -i httpd or
ps -aef | grep -i httpd

depending on your OS type.

If you don't see any apache daemons running, then that's also a
problem.

In short, I'd say you may have multiple issues that need to be dealt
with.