can't open port 80

Question

Level 1

130 points

can't open port 80

I just can't open port 80 on my AEBS n 1st G. I want to use this port to enable access from the internet to my Mini server's wiki pages.

I've added port 80 in the "Port Mapping" tab of Airport utility under "personal web sharing", but when I check the port with the network utility, it remains closed.

What am I doing wrong. Please help.

This is the data of the mapping tab in Airport utility:

Public TCP port: 80

private IP address:10.0.1.201

Private TCP port: 80

rest empty.

 Mac Mini Server  MBA 13  MBP 15, Mac OS X (10.7)

Posted on Aug 8, 2011 12:04 PM

Reply

Answer 1

Tesserax

Level 10

148,757 points

Aug 8, 2011 12:11 PM in response to Mark Dannau

How are you determining that TCP port 80 is remaining closed after configuring the AirPort through the AirPort Utility?

Regardless, some ISP automatically block certain ports to prevent users from "running a business" if they are only "paying for consumer-grade" service. In this case, web server, mail server, file server, etc. ports would be blocked. One way around this is to use a port in a higher range. For example, for HTTP, use 8080 instead of 80.

Reply

Answer 2

Mark Dannau Author

Level 1

130 points

Aug 8, 2011 1:18 PM in response to Tesserax

I'm using the network utility/port scan with my server's IP.

I'll try your 8080 solution,see if that works. My ISP's router is a Zyxel p600 which seems to block the 80 ports by default. I've also contacted my ISP to see if there is a way to unlock it.

Thanks for your guidance. Mark

Reply

Answer 3

Tesserax

Level 10

148,757 points

Aug 8, 2011 1:26 PM in response to Mark Dannau

I'm using the network utility/port scan with my server's IP.

If you are running Network Utility from a computer on the local network, you are testing for open ports on the server itself, not of your Internet router.

If you actually want to test the router's ports, from your local network, you will need to use the Public (WAN-side) of your router.

Reply

Answer 4

Mark Dannau Author

Level 1

130 points

Aug 8, 2011 1:38 PM in response to Tesserax

You'rs right, so what I now did is unplug the Ethernet cable that was going from the router to my AEBS, plugged it to my MBP, noted the ethernet IP that I got 169.254.138.xxx in the network prefs and then did the same port scan test.

It seems to be scanning indefinitely with no result whatsoever. Am I doing something wrong?

Reply

Answer 5

Tesserax

Level 10

148,757 points

Aug 8, 2011 1:43 PM in response to Mark Dannau

A 169.254.n.n address would indicate a self-assigned address and not an actual Public IP address. A much easier way to get your Public IP address is to use a web site, like: http://www.whatsmyip.org/

Please reconnect your modem and AEBS, and then, open Safari from your MBP and go to this website to get your Public IP address.

Reply

Answer 6

Mark Dannau Author

Level 1

130 points

Aug 8, 2011 1:55 PM in response to Tesserax

Sorry for being such a $%&/!

Port Scanning host: 190.196.xx.xxx

Open TCP Port: 21 ftp

Open TCP Port: 53 domain

Open TCP Port: 554 rtsp

Open TCP Port: 3900 udt_os

Open TCP Port: 5009 winfs

Open TCP Port: 7070 arcp

Open TCP Port: 9100 hp-pdl-datastr

Open TCP Port: 10000 ndmp

Open TCP Port: 11525

and endless scan going on. No port 80 in sight :-(

Reply

Answer 7

Tesserax

Level 10

148,757 points

Aug 8, 2011 2:05 PM in response to Mark Dannau

No problem. Ok these are the ports that are reporting from the Internet as "open" on the WAN-side of your Internet router. Unless you specifically blocked port 80, then most likely, your ISP has. Again, the typical workaround is to use a port in the upper range. Your website would then have link that includes this port. For example if you choose TCP port 8080, then use: http://mywebsite.com:8080

When a user from the Internet clicks on that link, that request will come on port 8080, and then, be mapped or forwarded to TCP 80 on your internal web server.

Reply

Answer 8

Mark Dannau Author

Level 1

130 points

Aug 8, 2011 2:23 PM in response to Tesserax

Ok, but should I change the AEBS web sahring mapping port to 8080 or should I just leave it to 80?

Should I also change the Server's web incoming port to 8080?

Reply

Answer 9

Tesserax

Level 10

148,757 points

Aug 8, 2011 2:45 PM in response to Mark Dannau

First, 8080 is just a suggestion. You can pick any port you prefer. It will help if you have a list of commonly used ports to not pick one that may conflict with other applications. For that, check out this Apple Support link.

The drop-down options on the Port Mapping window are a number of common services with their default mappings already provided for your convenience. You can easily change any of the values provided to create a "Custom" mapping. So to answer your question, you will want to change the Public TCP Port(s) to whatever value you decide on, but leave the Private TCP Port(s) set to 80. Otherwise, you will have to change your web server program to listen to requests on a port other than 80. (Note: Disregard the Private IP Address shown in the figure as this is currently in the range of my local network.)

Reply

Answer 10

Mark Dannau Author

Level 1

130 points

Aug 11, 2011 11:52 AM in response to Tesserax

Sorry for not replying sooner, I was out of town.

I did the setup as you showed it, tested it and it still doesn't work.

I also contacted my ISP with some questions about the port 80 being open or not. Their answer is that port 80 is always open as that's the port used to access the internet (made me feel like my question was reeeaaaally stupid...). I explained I had found some info on the internet that said the Zyxel modems very often come with the port 80 closed, and that nearly made them laugh... :-(

So I once again did a scan of my public port and get this:

Port Scanning host: 200.124.48.xxx

Open TCP Port: 21 ftp

Open TCP Port: 53 domain

Open TCP Port: 554 rtsp

Open TCP Port: 3900 udt_os

Open TCP Port: 5009 winfs

No port 80 in view.

I also did a traceroute of the Dyndn'ssed domain I want to access on my server and get this:

traceroute to http://korkettes.com/groups/essai/calendar/ (67.215.65.132), 64 hops max, 72 byte packets

1 10.0.1.1 (10.0.1.1) 14.436 ms 12.512 ms 8.778 ms

2 10.9.88.1 (10.9.88.1) 24.442 ms 12.056 ms 10.001 ms

3 sblx12gw.gtdinternet.com (190.196.63.126) 18.751 ms 10.161 ms 10.517 ms

4 cn1.ge1-0-1.sblx12.gtdinternet.com (190.196.125.54) 38.874 ms 144.407 ms 12.339 ms

5 ci1.te1-2.v219.cn1.gtdinternet.com (190.196.125.29) 11.119 ms 25.334 ms 25.875 ms

6 tengigabitethernet9-3.ar3.scl1.gblx.net (64.209.88.25) 50.010 ms 8.308 ms 8.641 ms

7 ae3-30g.scr3.nyc1.gblx.net (67.17.104.189) 185.237 ms

ae0-30g.scr4.nyc1.gblx.net (67.16.139.2) 212.148 ms 248.437 ms

8 e5-1-30g.ar9.nyc1.gblx.net (67.16.142.54) 149.660 ms 147.576 ms 139.618 ms

9 xe-0-3-0-6.r05.nycmny01.us.bb.gin.ntt.net (129.250.8.129) 146.279 ms 200.869 ms 136.877 ms

10 ae-1.r23.nycmny01.us.bb.gin.ntt.net (129.250.4.68) 144.528 ms 262.677 ms 209.261 ms

11 ae-1.r20.asbnva02.us.bb.gin.ntt.net (129.250.2.9) 173.034 ms 390.095 ms 181.918 ms

12 ae-1.r01.asbnva02.us.bb.gin.ntt.net (129.250.3.11) 424.923 ms 233.061 ms 439.628 ms

13 ge-0-7-0-33.r01.asbnva02.us.ce.gin.ntt.net (129.250.12.114) 286.701 ms 138.696 ms 131.210 ms

14 hit-nxdomain.opendns.com (67.215.65.132) 128.300 ms 135.859 ms 136.805 ms

Just so you know: GTD is my ISP.

I can access the same domain locally with miniserver.local/groups/essai/calendar/ very well.

don't know what else to try.

Reply

Answer 11

Mark Dannau Author

Level 1

130 points

Aug 11, 2011 12:38 PM in response to Tesserax

Ok, just found the problem.

In the Airport setting/ mapping/ websharing the default private IP address is (...😝 of course!) Airport's, so it was to enough to replace this address with the server's ip to make it work.

Thanks for all your help!!!

Reply

Answer 12

Tesserax

Level 10

148,757 points

Aug 11, 2011 1:02 PM in response to Mark Dannau

Ok, other than I see you have run the port scan against a different Pubic IP address and you are using OpenDNS for your DNS serves, I don't necessarily see anything amiss.

I just ran a port scan on my Cisco router and port 80 was open. I happen to use OpenDNS as well.

One thing you can try, is to go back to using your ISP's DNS servers temporarily to see if this helps resolve the issue.

Reply

Answer 13

Tesserax

Level 10

148,757 points

Aug 11, 2011 1:03 PM in response to Mark Dannau

Good find! I'm glad you got it worked out.

Reply