Server works on Lan but not over internet.

[danshea]

try with my i.p. 76.29.34.164 and my lan is now 192.168.1.104

[Doug S]

No ICMP "unreachable" now.

doug@doug-64:~$ sudo tcpdump -n -nn -tttt -i eth1 host 76.29.34.164
[sudo] password for doug:
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth1, link-type EN10MB (Ethernet), capture size 65535 bytes
2013-04-10 08:37:16.098118 IP XXX.XXX.XXX.XXX.50605 > 76.29.34.164.80: Flags [S], seq 3760402329, win 8192, options [mss 1460,nop,wscale 2,nop,nop,sackOK], length 0
2013-04-10 08:37:16.098364 IP XXX.XXX.XXX.XXX.50606 > 76.29.34.164.80: Flags [S], seq 629044539, win 8192, options [mss 1460,nop,wscale 2,nop,nop,sackOK], length 0
2013-04-10 08:37:19.084345 IP XXX.XXX.XXX.XXX.50606 > 76.29.34.164.80: Flags [S], seq 629044539, win 8192, options [mss 1460,nop,wscale 2,nop,nop,sackOK], length 0
2013-04-10 08:37:19.084498 IP XXX.XXX.XXX.XXX.50605 > 76.29.34.164.80: Flags [S], seq 3760402329, win 8192, options [mss 1460,nop,wscale 2,nop,nop,sackOK], length 0
2013-04-10 08:37:25.090581 IP XXX.XXX.XXX.XXX.50606 > 76.29.34.164.80: Flags [S], seq 629044539, win 65535, options [mss 1460,nop,nop,sackOK], length 0
2013-04-10 08:37:25.090618 IP XXX.XXX.XXX.XXX.50605 > 76.29.34.164.80: Flags [S], seq 3760402329, win 8192, options [mss 1460,nop,nop,sackOK], length 0
2013-04-10 08:37:37.100424 IP XXX.XXX.XXX.XXX.50610 > 76.29.34.164.80: Flags [S], seq 3164592437, win 8192, options [mss 1460,nop,wscale 2,nop,nop,sackOK], length 0
2013-04-10 08:37:40.082520 IP XXX.XXX.XXX.XXX.50610 > 76.29.34.164.80: Flags [S], seq 3164592437, win 8192, options [mss 1460,nop,wscale 2,nop,nop,sackOK], length 0
2013-04-10 08:37:46.088506 IP XXX.XXX.XXX.XXX.50610 > 76.29.34.164.80: Flags [S], seq 3164592437, win 8192, options [mss 1460,nop,nop,sackOK], length 0
2013-04-10 08:38:19.285445 IP XXX.XXX.XXX.XXX.50620 > 76.29.34.164.80: Flags [S], seq 3481709119, win 8192, options [mss 1460,nop,wscale 2,nop,nop,sackOK], length 0
2013-04-10 08:38:19.286576 IP XXX.XXX.XXX.XXX.50621 > 76.29.34.164.80: Flags [S], seq 252670855, win 8192, options [mss 1460,nop,wscale 2,nop,nop,sackOK], length 0
2013-04-10 08:38:22.265872 IP XXX.XXX.XXX.XXX.50620 > 76.29.34.164.80: Flags [S], seq 3481709119, win 8192, options [mss 1460,nop,wscale 2,nop,nop,sackOK], length 0
2013-04-10 08:38:22.296991 IP XXX.XXX.XXX.XXX.50621 > 76.29.34.164.80: Flags [S], seq 252670855, win 8192, options [mss 1460,nop,wscale 2,nop,nop,sackOK], length 0
2013-04-10 08:38:28.272029 IP XXX.XXX.XXX.XXX.50620 > 76.29.34.164.80: Flags [S], seq 3481709119, win 65535, options [mss 1460,nop,nop,sackOK], length 0
2013-04-10 08:38:28.303148 IP XXX.XXX.XXX.XXX.50621 > 76.29.34.164.80: Flags [S], seq 252670855, win 8192, options [mss 1460,nop,nop,sackOK], length 0
2013-04-10 08:38:40.270629 IP XXX.XXX.XXX.XXX.50623 > 76.29.34.164.80: Flags [S], seq 3261244509, win 8192, options [mss 1460,nop,wscale 2,nop,nop,sackOK], length 0
2013-04-10 08:38:40.317809 IP XXX.XXX.XXX.XXX.50625 > 76.29.34.164.80: Flags [S], seq 3412744677, win 8192, options [mss 1460,nop,wscale 2,nop,nop,sackOK], length 0
2013-04-10 08:38:43.264051 IP XXX.XXX.XXX.XXX.50623 > 76.29.34.164.80: Flags [S], seq 3261244509, win 8192, options [mss 1460,nop,wscale 2,nop,nop,sackOK], length 0
2013-04-10 08:38:43.326413 IP XXX.XXX.XXX.XXX.50625 > 76.29.34.164.80: Flags [S], seq 3412744677, win 8192, options [mss 1460,nop,wscale 2,nop,nop,sackOK], length 0
2013-04-10 08:38:49.270343 IP XXX.XXX.XXX.XXX.50623 > 76.29.34.164.80: Flags [S], seq 3261244509, win 8192, options [mss 1460,nop,nop,sackOK], length 0
2013-04-10 08:38:49.332476 IP XXX.XXX.XXX.XXX.50625 > 76.29.34.164.80: Flags [S], seq 3412744677, win 8192, options [mss 1460,nop,nop,sackOK], length 0

[Drenriza]

Have not read the replies on page #2.

The way i would get a host on a LAN on the WWW, is to create a static NAT rule in your router.
To share your single public ip address and reserve the port 80 for your local server.

So you say, anything that hits the public ip address (random address i created) 171.100.52.1:80 has a static NAT to 192.168.1.1, which is your local server.

Or any other port, just remember which one you use ,) So you can say http://171.100.52.1:[port number] from another PC.

EDIT.
So i read the replies on #2. And it sounds like you are making it unnecessary complicated for yourself.
How are you even trying to make it public from your LAN to the WWW? It seams like your using some kind of application on the server behind your router on the LAN.

[Slim Odds]

I can access my site on my lan using the domain name, so I assume that port 80 is not blocked. Weird.....

Of course port 80 is not blocked LOCALLY. He was referring to your ISP blocking port 80 before it gets to you.

[danshea]

Well now when I go to my local i.p. (192.168.1.104) and go to http://192.168.1.104/phpinfo.php it pops up a box for me to download the file instead of showing me my php info page. Doug, I don't have an error log file where you show for me to look. Which config file are you referencing? the php.ini or the php-fpm.conf? I am googling and working on it so lets see what happens. the site is www.socialpitchman.com that I am working on and that page will come up when I go to my lan (192.168.1.104). Now to get it out to the to the net. It has to be something simple that I am missing.

[danshea]

Hey Hey Doug,,,,, you da man. I copied your config to my "socialpitchman.conf" and the phpinfo file works now!!!! Now the lasty step is how do I get my site to be visible from the net and not just my lan....

[Doug S]

I think you meant to thank Charles, as I do not know anything about nginx or php5-fpm. I only know about standard LAMP stuff installed with ubuntu server.

On the port 80 blocked or not blocked stuff: We have shown serveral times, over now two threads, that the ISP is not blocking port 80 (or at least, wasn't).

[danshea]

ooops sorry, I did mean Charles. My phpinfo page works, and port 80 is not blocked, so I wonder what the problem could be? I must be missing a setting somewhere, but Nginx does not havbe a ports.conf like apache does. that was the issue in apache, not sure what it is with Nginx.

[Doug S]

I don't know why I was not getting the ICMP reply this morning, but I am getting it now. I think your router still thinks it is supposed to forward port 80 to 192.168.1.102:

2013-04-10 19:50:05.163075 IP 76.29.34.164 > XXX.XXX.XXX.XXX: ICMP host 192.168.1.102 unreachable, length 60

[CharlesA]

On the port 80 blocked or not blocked stuff: We have shown serveral times, over now two threads, that the ISP is not blocking port 80 (or at least, wasn't).

I don't know the specifies of how you tested to see if port 80 was open or not, but their site is still timing out for me. I guess they could try changing their port forwarding configuration to use port 8080 and see if they can access the site or not. That would rule out a configuration issue, at least.