On Sat, 2007-05-26 at 11:51 -0500, Scott Berry wrote: > Here is what I have found out so far. I am following your message you sent > last night. > > 1. I tried it locally on the linux box going to http://127.0.10.1 the under > construction html file I put up came up. > 2. Then I followed along and went to http://192.168.1.100 on my Windows > computer that came up fine. So what I am assuming is that either port 80 is > being blocked or I don't have the router set right. That does seem to be the case. That somewhere around your modem/router or ISP, port 80 is blocked. > My next step will be to see if I can open port 80 through the router and get > it too work if that does not work I would say the next logical step would be > to change the httpd.conf for a different port. Do you agree? Yes, as my other message discussed. The listen directive is the one to use, did you restart Apache between configuration changes, and are you familiar with SELinux? Listen 8080 Should cause Apache to listen on port 8080. Listen 80 Listen 8080 Should cause it to listen to both ports at the same time. However, SELinux also applies restrictions, on top. So you'll have to change how SELinux is running to be able to run Apache on ports other than 80, 3128, 8080, or 8118. The ones other than 80 are used by various HTTP proxies. Before mangling or disabling SELinux, try one of the other ports that it allows, by default. Just be sure to pick one that you're not already making use of (Squid uses 3128, Privoxy uses 8118, I don't know what commonly uses 8080). I definitely recommend keeping SELinux working. But you don't have to make Apache listen to another port, you can just forward connections between different port numbers at your modem/router. -- (This box runs FC6, my others run FC4 & FC5, in case that's important to the thread.) Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists.
