Operating Systems > Linux and UNIX

apache

<< < (2/7) > >>

voidmain:
Do a "netstat -a | grep www" which if you have Apache running and bound to all interfaces should show a line like:

tcp 0 0 *:www *:* LISTEN

If it is just bound to one interface or the other the "*" in "*:www" will contain the interface address or hostname.

I can ping/traceroute to you but I get "no route to host" when I try to telnet to your port 80 which I'm guessing means your provider is dropping http traffic to you.  Maybe they don't want you putting up a web server.  It would explain why you can get to your outside interface from your inside machines as you would not be going through their routers to get there.

I have an idea. Why don't you try running your web server on a port other than 80.  Maybe they are only blocking 80. Try 8000 for instance, then restart your httpd service.  Test it with http://chatroom.fuckmicrosoft.com:8000

[ May 07, 2002: Message edited by: VoidMain ]

Master of Reality:
try going to http://chatroom.fuckmicrosoft.com:3000

voidmain:
Nope, connection refused. Do you have anything in your ipchains rules that would be blocking 80 (or now 3000)? /sbin/ipchains -L

Master of Reality:
i looked at everything else and now i searched through the apache error logs. I found out that apache couldnt bind with port 80.
the error reads:
[date here is right after i restarted apache][crit] (98)Address already in use: make_sock: could not bind to port 80

what do you think would cause this?

voidmain:
Exactly what it says. You already have a process bound to port 80 so Apache can't start.  When you stop Apache (/etc/rc.d/init.d/httpd stop) then do a "netstat -a | grep www" you should get nothing back. If you do you have another process listening on port 80.

Navigation

[0] Message Index

[#] Next page

[*] Previous page