Why would Apache refuse to serve any pages?

Discussion in 'Apache' started by Cap'n Steve, Mar 30, 2008.

  1. #1
    Ok, I have a little bit of an unusual problem: I'm trying to run Apache 2.2 on my router. The router is running DD-WRT and Apache is installed via Optware.

    I've gotten it to start, and according to netstat it's listening on port 8000, but when I try to connect with a web browser to 192.168.1.1:8000, it just loads forever. Actually, according to the Live HTTP Headers plugin for Firefox, no request is even sent after the connection is made. I've also tried connecting by running telnet on the router itself, and it doesn't respond to the GET request.

    The only thing I've changed in httpd.conf was the ServerName. I've tried setting LogLevel to "debug", but there's nothing interesting in the log. There's another web server running the router's administration interface, is there any way that could interfere even though it's on port 80?
     
    Cap'n Steve, Mar 30, 2008 IP
  2. SSANZ

    SSANZ Peon

    Messages:
    861
    Likes Received:
    10
    Best Answers:
    0
    Trophy Points:
    0
    #2
    The firmware on the router most likely doesn't like the port that your running.

    Try a lower port - 85 or around the normal web 80.

    Why install apache onto a router :S ?
     
    SSANZ, Apr 6, 2008 IP
  3. Cap'n Steve

    Cap'n Steve Peon

    Messages:
    2
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    0
    #3
    Thanks for the reply. I tried it on port 85 and 88 with the same results.

    To answer your question, I'm installing on the router because I'd like to have a test server without leaving my computer on constantly.
     
    Cap'n Steve, Apr 12, 2008 IP