ubuntu LAMP server, can't access site remotely, locally works by local ip and wan

weylin · 04-25-2012, 05:24 AM

So I can access the site from the wan ip, the lan ip, localhost on the actual server, but people can't seem to connect to it. I have the server in DMZ mode, and I even opened port 80 in the router as well. I also turned off the default firewall that comes with ubuntu and i do not have iptables. My friend said he was able to ping the box and said that it was app side.

sudo lsof -i

apache2 1376 root 3u IPv4 9496 0t0 TCP *:www (LISTEN)
apache2 1473 www-data 3u IPv4 9496 0t0 TCP *:www (LISTEN)
apache2 1474 www-data 3u IPv4 9496 0t0 TCP *:www (LISTEN)
apache2 1475 www-data 3u IPv4 9496 0t0 TCP *:www (LISTEN)
apache2 1476 www-data 3u IPv4 9496 0t0 TCP *:www (LISTEN)
apache2 1477 www-data 3u IPv4 9496 0t0 TCP *:www (LISTEN)
apache2 2035 www-data 3u IPv4 9496 0t0 TCP *:www (LISTEN)

which he said looked good

acid_kewpie · 04-25-2012, 05:31 AM

what is their experience when they can't connect? A standard test to divide and conquer the issue would be to telnet to port 80 and see if that connects. You can also run tcpdump on the server to see if any requests are indeed reaching the box.

weylin · 04-25-2012, 05:52 AM

Quote:

Originally Posted by acid_kewpie

what is their experience when they can't connect? A standard test to divide and conquer the issue would be to telnet to port 80 and see if that connects. You can also run tcpdump on the server to see if any requests are indeed reaching the box.

I believe it just kind of loads for a while and eventually fails, not sure what message they get, but it does load for a while.

acid_kewpie · 04-25-2012, 05:59 AM

we'd really need more than that. if it just doesn't fail instantly, it could be a network timeout issue, which could certainly make people believe it's loading in some form when it's actually not.

weylin · 04-25-2012, 06:03 AM

telnet 192.168.1.102 80
Trying 192.168.1.102...
Connected to 192.168.1.102.
Escape character is '^]'.
Connection closed by foreign host.

acid_kewpie · 04-25-2012, 06:10 AM

right, but you already said it DID work locally... so what about from the remote locations?

weylin · 04-25-2012, 06:13 AM

I don't have a way of testing remotely at the moment. Unless, maybe...

weylin · 04-25-2012, 06:34 AM

So when I went to the IP from a different internet connection it loaded a login page to some healthcare site. I wasn't able to telnet.

acid_kewpie · 04-25-2012, 06:37 AM

right, so a routing or firewall issue at some place. run "tcpdump -vn port 80" on the server when you try to connect and see if the server itself sees anything. even if iptables is knocking it on the head, tcpdump will see it, so if tcpdump doesn't see anything, the traffic is not reaching the box.