Can't connect to Apache2 server remotely

sixerjman · 05-24-2007, 03:15 AM

I just installed Linux (Debian Lenny) on a friend's machine and slapped up a web page which I can see locally (localhost) but can't establish a connection from my house to her's. I've opened up port 80 on her router and have a DNS record in dyndns.org but the request just times out.

After inserting 'Listen 192.168.2.45:80' in 'httpd.conf' the server won't start:

Code:

apache2ctl start
(98)Address already in use: make_sock: could not bind to address [::]:80
(98)Address already in use: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs

The server has stopped and I don't see anything bound to port 80. What's the deal? Any help is appreciated, thanks in advance.

BTW, the next killer app for admins has got to be
a GUI configurator for Apache2, there must be 1000 directives, 100 config files and the doc is horrible. I just want to put up a stupid web page and look at it remotely (which I've done before on Windows and Linux, but it was awhile ago), not run secure database transactions.

sixerjman · 05-24-2007, 03:20 AM

They should change the name of the file to listen.conf.

sixerjman · 05-24-2007, 03:30 AM

just like I told it to. I told the router to route external requests for port 80 to internal port 80 and IP address 192.168.2.45. Nothing doing.

billymayday · 05-24-2007, 04:24 AM

Try

netstat -p --listen | grep http

as root to see what's listening on port 80

billymayday · 05-24-2007, 04:25 AM

ps - do you have a permission problem on the logs or is it the same issue?

sixerjman · 05-28-2007, 11:52 PM

I have a feeling the router is not letting the request through. I'll check the logs in tomorrow and try to see what's what.

sixerjman · 06-06-2007, 11:48 PM

I installed TCPDUMP on her machine and ran tcpdump 'tcp port 80'. Then I tried to hit the web server but no output from tcpdump. Then I tried netcat ('nc foo 80') but no connection and no output from tcpdump on her machine either (I was logged in via ssh). Neither 'firestarter' or the router showed any packets being dropped.

The odd thing I set up the route to the webserver vis-a-vis router and firewall just like I set up the ssh deal (i.e. open the port on the router, allow connection to the port from my IP), which works.