[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Name based virtual host forwarding from Tux to Apache



> -----Mensaje original-----
> > It's an apache configuration problem, as apache is listening on
> > 127.0.0.1:8080 (for example) it assumes that for virtual hosts
> > configuration. You have to force it ussing the real ip an port
> where tux is
> > listening. Change this parameters in your apache configuration:
>
> That to me implies I should have explicit Listen lines. That might be
> something to try. I am currently using BindAddress * because I thought
> that might be a problem. Perhaps a Listen x.x.x.x:8080 would help.

If you set up NameVirtualHost and VirtualHost propertly Listen or
BindAddress can be set to 127.0.0.1:8080 without problems

> > NameVirtualHost x.x.x.x:80 (replace x.x.x.x with your real ip)
>
> Have that, without the port. Shouldn't the port, if included, be 8080?

Is must be 80 because apache does not handle conections directly, so apache
thinks the connection came to port 80 where TUX is listening on (read TUX
source for more info or Ingo's post in this thread)

> > <VirtualHost hostname.tld:80>
> >  ...
> > </VirtualHost>
>
> Yes, I have that to, with all the correct info. Apache works fine by
> itself.

Make sure the :80 is present. Apache whitout TUX works with *, _default_,
specifing port, omiting it, etc. but with TUX the only working config is
this (as far as i tried).

> > If you use * or you do not specify de ip, the hostname and the
> port it does
> > not work.
>
> OK. I have some ideas now. Thanks.

Any other combination of options different from what i originally posted
makes virtualhosts stop working on apache (I tried every possible
combination i think)

Angel.





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index] []