Apache is not working behind the router

On Feb 23, 3:52 pm, "Lars" <jon.....TakeThisOut@xxxxxxxxxxxxxxxxxx.xxx> wrote:
> Hi
>
> When I had my own Linux server up and running at my office I had to set the
> IP address to the one outside the router. For example
>
> IP forwww.doimain.eu = 123.123.123.123
>
> Connection IP for the router (Coputer-Router) = 192.168.0.183 (D-Link 604)
>
> In this case I had to set the IP to 123.123.123.123. That's the addresss the
> other needs to connect to. The router then needs to forward por 80 to
> 168.168.0.183.
>
> BTW
> The same goes for vsftpd expecially of vscftp must support Passive Mode.
>
> Lars
>
> "kimiraikkonen" <kimiraikkone....TakeThisOut@gmail.com> skrev i meddelandetnews:ebdb4366-6f19-412e-8e3a-18fbf12080f8@62g2000hsn.googlegroups.com...
> On Feb 23, 11:50 am, Davide Bianchi <davideyeahs....TakeThisOut@onlyforfun.net>
> wrote:
>
>
>
>
>
> > On 2008-02-23, kimiraikkonen <kimiraikkone....TakeThisOut@gmail.com> wrote:
>
> > > That's why i've done port forwarding but it doesn't work.
>
> > Explain what "doesn't work" means. Do you get an error page? Can you see
> > the connection in your log file?
>
> > > What am i missing? Is it a router failure or do i need to modify
> > > http.conf manually as addition?
>
> > I think you need to check your router and eventually talk to your ISP.
>
> > Davide
>
> > --
> > Price has nothing to do with quality when it comes to software: you
> > could walk, or bounce along on a pogo-stick shoved up your ass -
> > walking is free, you have to pay for the pogo-stick.
> > -- Adam the Tired on alt.sysadmin.recovery
>
> >I mean, though i forwarded necessary ports, i don't get my Apache
> >homepage using external IP, i get router's configuration web-page.
>
> I think you need to set the Location to the external IP address you router
> is using. In case you have a DHCP connection to that's the router connects
> to you need to get a sub domain atwww.no-ip.org. That will help your users
> to connect whatever the IP your ISP provides you with.
>
> Lars
>
>
>
>
>
> >What about ISP?- Hide quoted text -
>
> - Show quoted text -- Hide quoted text -
>
> - Show quoted text -

I use static IP which has nothing to do with DHCP (192.168.1.2).
Also my ISP is said that no port is blocked by this provider.
 >> Stay informed about: Apache is not working behind the router 

This message is not archived
 >> Stay informed about: Apache is not working behind the router 

On 23/02/2008 in message
<ebdb4366-6f19-412e-8e3a-18fbf12080f8.RemoveThis@62g2000hsn.googlegroups.com>
kimiraikkonen wrote:

>I mean, though i forwarded necessary ports, i don't get my Apache
>homepage using external IP, i get router's configuration web-page.

This looks like a network issue rather than an Apache issue so you may get
better help in a network group.

If people can currently get to your router's configuration page then make
sure you are not using the default name/password!

You need to forward requests for your external IP address to a specific PC
on your LAN. How to do it depends on the router which is why a network
group may be more useful to you.

--
Jeff Gaines Damerham Hampshire UK
I can please only one person per day. Today is not your day.
Tomorrow, isn't looking good either.
 >> Stay informed about: Apache is not working behind the router 

On Sat, 23 Feb 2008 02:05:18 -0800 (PST), kimiraikkonen
<kimiraikkonen85.RemoveThis@gmail.com> wrote:

>On Feb 23, 11:50 am, Davide Bianchi <davideyeahs....RemoveThis@onlyforfun.net>
>wrote:
>> On 2008-02-23, kimiraikkonen <kimiraikkone....RemoveThis@gmail.com> wrote:
>>
>> > That's why i've done port forwarding but it doesn't work.
>>
>> Explain what "doesn't work" means. Do you get an error page? Can you see
>> the connection in your log file?
>>
>> > What am i missing? Is it a router failure or do i need to modify
>> > http.conf manually as addition?
>>
>> I think you need to check your router and eventually talk to your ISP.
>>
>> Davide
>>
>
>I mean, though i forwarded necessary ports, i don't get my Apache
>homepage using external IP, i get router's configuration web-page.

You may have to switch off the router's configuration
web interface. It's a bad idea to expose it to the WAN
side anyway.

Then check the port forwarding rules again (NAT).

NAT will only work reliably if the webserver has a
fixed LAN address, and doesn't rely on getting an IP
address from the routers DHCP server. Of course the
server's network settings should stay within the
routers LAN subnet (10.x.y.z or 192.168.x.y). You will
have to enter the gateway address (the router NIC on
the LAN side) and DNS server addressses in the
webservers IP settings as they aren't provied by DHCP
anymore.

Some routers support DHCP with fixed IP addresses for
specified MAC addresses. That might be easier to set
up.

To access your webserver on its WAN address from a PC
on your LAN your routers needs to be configured for
"NAT loopback".

If that's impossible, you have to make sure your
request doesn't stay inside the LAN, but goes out to a
proxy on the WAN side first, and gets forwarded back to
your router, so the router will apply the NAT/port
forwarding rules to the request.
So, you have to configure the web proxy of your
Internet Service Provider in your webbrowser.

All the above is related to networking.
The only way this problem touches the Apache
configuration is the Listen directive and possibly the
virtual host configuration.

Will not work from WAN:
Listen 127.0.0.0:80
Listen localhost:80

Should work from WAN:
Listen 80
Listen 0.0.0.0:80

Don't try vhosts before the basic server works.

>What about ISP?
Your Internet Service Provider might block certain
ports. Some ISPs prohibit running any servers on a home
connection. Check the contract conditions.

HTH
--
( Kees
)
c[_] When you're arguing with a fool, make sure he isn't doing the same thing. (#73)
 >> Stay informed about: Apache is not working behind the router 

On Feb 23, 1:40 pm, Kees Nuyt <k.n....RemoveThis@nospam.demon.nl> wrote:
> On Sat, 23 Feb 2008 02:05:18 -0800 (PST), kimiraikkonen
>
>
>
>
>
> <kimiraikkone....RemoveThis@gmail.com> wrote:
> >On Feb 23, 11:50 am, Davide Bianchi <davideyeahs....RemoveThis@onlyforfun.net>
> >wrote:
> >> On 2008-02-23, kimiraikkonen <kimiraikkone....RemoveThis@gmail.com> wrote:
>
> >> > That's why i've done port forwarding but it doesn't work.
>
> >> Explain what "doesn't work" means. Do you get an error page? Can you see
> >> the connection in your log file?
>
> >> > What am i missing? Is it a router failure or do i need to modify
> >> > http.conf manually as addition?
>
> >> I think you need to check your router and eventually talk to your ISP.
>
> >> Davide
>
> >I mean, though i forwarded necessary ports, i don't get my Apache
> >homepage using external IP, i get router's configuration web-page.
>
> You may have to switch off the router's configuration
> web interface. It's a bad idea to expose it to the WAN
> side anyway.
>
> Then check the port forwarding rules again (NAT).
>
> NAT will only work reliably if the webserver has a
> fixed LAN address, and doesn't rely on getting an IP
> address from the routers DHCP server. Of course the
> server's network settings should stay within the
> routers LAN subnet (10.x.y.z or 192.168.x.y). You will
> have to enter the gateway address (the router NIC on
> the LAN side) and DNS server addressses in the
> webservers IP settings as they aren't provied by DHCP
> anymore.
>
> Some routers support DHCP with fixed IP addresses for
> specified MAC addresses. That might be easier to set
> up.
>
> To access your webserver on its WAN address from a PC
> on your LAN your routers needs to be configured for
> "NAT loopback".
>
> If that's impossible, you have to make sure your
> request doesn't stay inside the LAN, but goes out to a
> proxy on the WAN side first, and gets forwarded back to
> your router, so the router will apply the NAT/port
> forwarding rules to the request.
> So, you have to configure the web proxy of your
> Internet Service Provider in your webbrowser.
>
> All the above is related to networking.
> The only way this problem touches the Apache
> configuration is the Listen directive and possibly the
> virtual host configuration.
>
> Will not work from WAN:
> Listen 127.0.0.0:80
> Listen localhost:80
>
> Should work from WAN:
> Listen 80
> Listen 0.0.0.0:80
>
> Don't try vhosts before the basic server works.
>
> >What about ISP?
>
> Your Internet Service Provider might block certain
> ports. Some ISPs prohibit running any servers on a home
> connection. Check the contract conditions.
>
> HTH
> --
>  (  Kees
>   )
> c[_] When you're arguing with a fool, make sure he isn't doing the same thing.  (#73)- Hide quoted text -
>
> - Show quoted text -

Kees,
Thanks, great! I changed listen 127.0.0.1 with "listen 80" now it's
fixed. The problem wasn't the router, because i've done forwarding
port 80 previously.

Now i want to add password option to my server, which line should i
edit?
 >> Stay informed about: Apache is not working behind the router 

Hi

When I had my own Linux server up and running at my office I had to set the
IP address to the one outside the router. For example

IP for www.doimain.eu = 123.123.123.123

Connection IP for the router (Coputer-Router) = 192.168.0.183 (D-Link 604)

In this case I had to set the IP to 123.123.123.123. That's the addresss the
other needs to connect to. The router then needs to forward por 80 to
168.168.0.183.

BTW
The same goes for vsftpd expecially of vscftp must support Passive Mode.


Lars


"kimiraikkonen" <kimiraikkonen85 RemoveThis @gmail.com> skrev i meddelandet
news:ebdb4366-6f19-412e-8e3a-18fbf12080f8@62g2000hsn.googlegroups.com...
On Feb 23, 11:50 am, Davide Bianchi <davideyeahs... RemoveThis @onlyforfun.net>
wrote:
> On 2008-02-23, kimiraikkonen <kimiraikkone... RemoveThis @gmail.com> wrote:
>
> > That's why i've done port forwarding but it doesn't work.
>
> Explain what "doesn't work" means. Do you get an error page? Can you see
> the connection in your log file?
>
> > What am i missing? Is it a router failure or do i need to modify
> > http.conf manually as addition?
>
> I think you need to check your router and eventually talk to your ISP.
>
> Davide
>
> --
> Price has nothing to do with quality when it comes to software: you
> could walk, or bounce along on a pogo-stick shoved up your ass -
> walking is free, you have to pay for the pogo-stick.
> -- Adam the Tired on alt.sysadmin.recovery
>
>I mean, though i forwarded necessary ports, i don't get my Apache
>homepage using external IP, i get router's configuration web-page.

I think you need to set the Location to the external IP address you router
is using. In case you have a DHCP connection to that's the router connects
to you need to get a sub domain at www.no-ip.org. That will help your users
to connect whatever the IP your ISP provides you with.


Lars

>
>
>What about ISP?
>
 >> Stay informed about: Apache is not working behind the router 

On Sat, 23 Feb 2008 08:09:21 -0800 (PST), kimiraikkonen
<kimiraikkonen85 RemoveThis @gmail.com> wrote:

>Now i want to add password option to my server,
>which line should i edit?

That's a totally different topic.

First, read:

http://httpd.apache.org/docs/2.2/howto/auth.html

If you have any questions about it, start a new thread
here.
--
( Kees
)
c[_] When you're arguing with a fool, make sure he isn't doing the same thing. (#73)
 >> Stay informed about: Apache is not working behind the router 

On Feb 23, 9:06 pm, Kees Nuyt <k.n....TakeThisOut@nospam.demon.nl> wrote:
> On Sat, 23 Feb 2008 08:09:21 -0800 (PST), kimiraikkonen
>
> <kimiraikkone....TakeThisOut@gmail.com> wrote:
> >Now i want to add password option to my server,
> >which line should i edit?
>
> That's a totally different topic.
>
> First, read:
>
> http://httpd.apache.org/docs/2.2/howto/auth.html
>
> If you have any questions about it, start a new thread
> here.
> --
>  (  Kees
>   )
> c[_] When you're arguing with a fool, make sure he isn't doing the same thing.  (#73)

Thanks, but still i wonder why Apache is NOT configured to accept all
connections without limiting only to 127.0.0.1 (localhost). How would
i know if the problem's solution is to change Listen 127.0.0.1 to
Listen 80.

Mustn't Apache set Listen parameter to all IPs? I read documentation
and it says:

"The Listen directive instructs Apache to listen to more than one IP
address or port; by default it responds to requests on all IP
interfaces, but only on the port given by the Port directive"

but i HAD TO change listen 127.0.0.1 to listen 80 to get it work
running OK it behind my router.

Why?
 >> Stay informed about: Apache is not working behind the router 

"kimiraikkonen" <kimiraikkonen85 DeleteThis @gmail.com> wrote in message
news:ec9f6ea3-06d1-4913-85ae-> 01892848832a DeleteThis @c33g2000hsd.googlegroups.com...
>
> Thanks, but still i wonder why Apache is NOT configured to accept all
> connections without limiting only to 127.0.0.1 (localhost). How would
> i know if the problem's solution is to change Listen 127.0.0.1 to
> Listen 80.
>
> Mustn't Apache set Listen parameter to all IPs? I read documentation
> and it says:
>
> "The Listen directive instructs Apache to listen to more than one IP
> address or port; by default it responds to requests on all IP
> interfaces, but only on the port given by the Port directive"

The important part here is "by default", it is not the only way that listen
will work.

> but i HAD TO change listen 127.0.0.1 to listen 80 to get it work
> running OK it behind my router.
>
> Why?

Because 'Listen 127.0.0.1' is invalid, you either specify a port or an
IP-address:Port, you cannot just specify an IP-address.

Listen 127.0.0.1:80
would be valid and listen only on localhost on port 80 (and because the
localhost address is internal to the machine this will not work from an
external machine / through your router)
Listen 80
will listen on all interfaces on port 80
 >> Stay informed about: Apache is not working behind the router 

On Feb 25, 12:15 pm, "phantom" <nob....DeleteThis@blueyonder.invalid> wrote:
> "kimiraikkonen" <kimiraikkone....DeleteThis@gmail.com> wrote in message
>
> news:ec9f6ea3-06d1-4913-85ae-> 018928488....DeleteThis@c33g2000hsd.googlegroups.com....
>
>
>
> > Thanks, but still i wonder why Apache is NOT configured to accept all
> > connections without limiting only to 127.0.0.1 (localhost). How would
> > i know if the problem's solution is to change Listen 127.0.0.1 to
> > Listen 80.
>
> > Mustn't Apache set Listen parameter to all IPs? I read documentation
> > and it says:
>
> > "The Listen directive instructs Apache to listen to more than one IP
> > address or port; by default it responds to requests on all IP
> > interfaces, but only on the port given by the Port directive"
>
> The important part here is "by default", it is not the only way that listen
> will work.
>
> > but i HAD TO change listen 127.0.0.1 to listen 80 to get it work
> > running OK it behind my router.
>
> > Why?
>
> Because 'Listen 127.0.0.1' is invalid, you either specify a port or an
> IP-address:Port, you cannot just specify an IP-address.
>
> Listen 127.0.0.1:80
> would be valid and listen only on localhost on port 80 (and because the
> localhost address is internal to the machine this will not work from an
> external machine / through your router)
> Listen 80
> will listen on all interfaces on port 80

Sorry, there's misunderstanding, i meant, after i installed Apache ,it
was set to Listen 127.0.0.1:80 "by default" . Then i need to change it
to Listen 80 to get access from WAN.

I just wonder why it was set to Listen 127.0.0.1:80 by default instead
of accepting all incoming connections as stated in official Apache
documentation.
 >> Stay informed about: Apache is not working behind the router 

On Feb 25, 10:41 pm, "phantom" <nob....DeleteThis@blueyonder.invalid> wrote:
> "kimiraikkonen" <kimiraikkone....DeleteThis@gmail.com> wrote in message
>
> news:3c063129-2c3d-4e1c-aeff-6554b1ded791@72g2000hsu.googlegroups.com...
>
>
>
> > Sorry, there's misunderstanding, i meant, after i installed Apache ,it
> > was set to Listen 127.0.0.1:80 "by default" . Then i need to change it
> > to Listen 80 to get access from WAN.
>
> > I just wonder why it was set to Listen 127.0.0.1:80 by default instead
> > of accepting all incoming connections as stated in official Apache
> > documentation.
>
> If you had downloaded a version of apache fromwww.apache.org, you would
> find the configured defaults to bin in agreement with the official
> documentation.
> Apache is distributed by a variety of different channels, not many of them
> stick to the original defaults.

Phantom,
I got Apache server with a third party bundle software named EasyPHP
2.01b. I remember i was using Apache 1.3 and was working fine on WAN
without needing to modify httpd.conf.

Thanks for the information.
 >> Stay informed about: Apache is not working behind the router 

On Mon, 25 Feb 2008 08:37:08 -0800 (PST), kimiraikkonen
<kimiraikkonen85.DeleteThis@gmail.com> wrote:

>On Feb 25, 12:15 pm, "phantom" <nob....DeleteThis@blueyonder.invalid> wrote:
>> "kimiraikkonen" <kimiraikkone....DeleteThis@gmail.com> wrote in message
>>
>> news:ec9f6ea3-06d1-4913-85ae-> 018928488....DeleteThis@c33g2000hsd.googlegroups.com...
>>
>>
>>
>> > Thanks, but still i wonder why Apache is NOT configured to accept all
>> > connections without limiting only to 127.0.0.1 (localhost). How would
>> > i know if the problem's solution is to change Listen 127.0.0.1 to
>> > Listen 80.
>>
>> > Mustn't Apache set Listen parameter to all IPs? I read documentation
>> > and it says:
>>
>> > "The Listen directive instructs Apache to listen to more than one IP
>> > address or port; by default it responds to requests on all IP
>> > interfaces, but only on the port given by the Port directive"
>>
>> The important part here is "by default", it is not the only way that listen
>> will work.
>>
>> > but i HAD TO change listen 127.0.0.1 to listen 80 to get it work
>> > running OK it behind my router.
>>
>> > Why?
>>
>> Because 'Listen 127.0.0.1' is invalid, you either specify a port or an
>> IP-address:Port, you cannot just specify an IP-address.
>>
>> Listen 127.0.0.1:80
>> would be valid and listen only on localhost on port 80 (and because the
>> localhost address is internal to the machine this will not work from an
>> external machine / through your router)
>> Listen 80
>> will listen on all interfaces on port 80
>
>Sorry, there's misunderstanding, i meant, after i installed Apache ,it
>was set to Listen 127.0.0.1:80 "by default" . Then i need to change it
>to Listen 80 to get access from WAN.
>
>I just wonder why it was set to Listen 127.0.0.1:80 by default instead
>of accepting all incoming connections as stated in official Apache
>documentation.

I guess it's the default because Apache httpd shouldn't
be run as a public server of the box anyway. It always
needs some customizing before you want to expose it to
the evil internet.
The default works well for a local test website and is
safe.
--
( Kees
)
c[_] If I'm supposed to live every day like it's my
last, I want a gallon of morphine. (Russ Wallace) (#393)
 >> Stay informed about: Apache is not working behind the router 

On Mon, 25 Feb 2008 20:56:33 +0100, Kees Nuyt
<k.nuyt.TakeThisOut@nospam.demon.nl> wrote:

>I guess it's the default because Apache httpd shouldn't
>be run as a public server of the box anyway.

Oops, that should be:
I guess it's the default because Apache httpd shouldn't
be run as a public server out of the box anyway.

--
( Kees
)
c[_] The only reason some people get lost in thought
is because it's unfamiliar territory. (#325)
 >> Stay informed about: Apache is not working behind the router