Find the answer to your Linux question:
Results 1 to 3 of 3
I run Apache 2 on fedora 14 on a small network. All clients can ping webserver successfully but all clients find it difficult to connect with webserver via their individual ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Jul 2010
    Posts
    7

    clients can't connect with web server


    I run Apache 2 on fedora 14 on a small network. All clients can ping webserver successfully but all clients find it difficult to connect with webserver via their individual web browsers. If i access the server physically on its web browser using localhost it responds fine but it doesn't respond from an external client's web browser. I have a feeling that the sever configuration is a cause, i just can't pinpoint the actual cause. i'll be glad for your inputs. Thanks

  2. #2
    Linux Newbie
    Join Date
    Jun 2012
    Location
    SF Bay area
    Posts
    195
    I can give you a couple things to try to help isolate the problem. You can run the following commands to see if there's really a server listening for connections on the HTTP port of your server.

    Code:
    lsof -i tcp:80
    
    netstat -an | awk '/^tcp/ && /LISTEN/'
    They pretty much do the same thing. The difference is that the second one, while clunkier, can be run by normal users and only shows listening connections on the port 80 locally. The first one is simpler but you have to run it as "root" and it will show connections to port 80 on external systems if there are any on the server.

    If you do see a LISTEN active on port 80 for something other then "localhost" or "127.0.0.1", then Apache is waiting for connections to that IP address. To see if that's working you can run this command after logging into the host running the Apache server.

    Code:
    curl --url http:IP-ADDRESS-HERE
    where "IP-ADDRESS-HERE" is the IP address of the server, meaning the one that showed up on the output from the earlier commands. If you get a good response back with the "curl" command, then your Apache server is up, running and ready to handle HTTP requests.

    And at that point I'd recommend looking into firewall configs on your server or on the network. But I'd recommend verifying that the Apache server will response on it's external address from the local system first.

  3. #3
    Linux Engineer
    Join Date
    Apr 2012
    Location
    Virginia, USA
    Posts
    910
    you need to allow inbound connections on port 80.

    You can use iptables, or system-config-firewall

  4. $spacer_open
    $spacer_close

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •