Forum Moderators: bakedjake

Message Too Old, No Replies

Apache works locally (on LAN) but not remotely (Internet)

         

ktulu

6:07 am on Jan 11, 2003 (gmt 0)

10+ Year Member



Ok...

I've got a linux box setup at work with apache running along with a few other services. On the LAN at work I have no problems whatsoever. Web, SSH, VNC, etc all work fine. We have a DSL connection and I've got my box set under the DMZ (so any incoming requests from the internet to the router are forwarded to the box). Now... I can SSH in from the internet to the box without a problem. I can VNC in without a problem. But for some reason, I can't pull up the website. IE just times out and I've tried using lynx from other places and they do the same.

I don't quite get it. On the local box I can load up the page with either IP address (the one of the box on the LAN 192.168.7.x and the internet connection). Something doesn't seem quite right. Could it possibly be a problem with the Linksys router just with port 80? I know apache can be configured to only allow local IP's to retreive websites, but I figure apache is configured correctly if I can enter in the IP address of the inet connection and it still work from localhost.

I'm not able to figure out (nor do I really know how) if the box is actually receiving the http requests and denying/not responding for some reason, or are the requests just not getting to it. I've tried using netstat to try and see if I can figure anything out but I admit, attempting to figure that out is a bit beyond my ability. I've checked the apache logs (error_log) and have not noticed *any* entries coming from machines other than ones on the LAN and the timestamp is when I was still at work, so it seems as though the packets aren't even getting to the linux box.

I've been messing around with the box turning off services here and there to try and increase security but I don't think anything I've done will cause these symptoms. It used to work just dandy for awhile then stopped. Any ideas?

littleman

7:23 am on Jan 11, 2003 (gmt 0)



Okay, you already answered one question, you CAN get it on your locally via your lan IP, so now, what about from other computers on your local network?

If you can, then I'd examine your Linksys settings. Another possibility is that your ISP is blocking port 80. You can always change the port on apache if that is the case.

Duckula

2:30 pm on Jan 11, 2003 (gmt 0)

10+ Year Member



You may also want to check your httpd.conf for directives like BindAddress or Listen. I use BindAddress to set my server just for local usage, for security. It haves the same behavior than yours, but here it's intentional.

ktulu

3:22 pm on Jan 11, 2003 (gmt 0)

10+ Year Member



Ok... Well I can't check it from other computers on the LAN cause they're all running Windows and can't remotely log-in. I'll have to wait till Monday for that.

The Linksys seems fine, I didn't change anything and I've verified that my box is on the DMZ. In addition, I went in and forwarded port 80 to my box as well for redundancy, but to no avail. Verizon does not block port 80 as far as I know, however... If they just started doing this recently (it worked a week ago), then that could possibly be the answer. All the clues seem to point towards that.

I've checked my httpd.conf settings, everything seems fine. I havn't changed it recently at all. I just tried changing the port to 8080... and I'll be damned. It worked.

Guess Verizon started blocking incoming port 80. ::mutters under breath::

Thanks for all the help.

littleman

6:50 am on Jan 12, 2003 (gmt 0)



I'm glad you were able to find the reason, but that sucks. That is really a messed up thing for an ISP to do.