Port 80 Blocked by ISP

[dt23]

Apparently my ISP is blocking port 80. I can get to my website fine if I use: mywebsite:162, but I would like to be able to allow user to get to my website without typing the port at the end.

Is there some way to do that in my router settings or in the httpd.conf??

TIA,
dt23

[Icarus]

If the ISP is blocking port 80 incomming (inbound from the internet) then you will not get ANY traffic for port 80, you need to get the ISP to make that change

Start handing out your links with the port number :)

[Gertrude]

I think there is a company that can act as a middle man between you and other peoples requests.. What it does is when someone trys to go to www.yourdomainname.com it first goes to that company on port 80 then they redirect those requests to your computer on whatever port you want. In your case 162. I dont know the name off the top of my head though.

[dt23]

Wow, I would love to know what companies can provide this middleman service. If anyone out there has an idea, please let us know.

Unfortunately, I doubt I'll be able to have my isp allow port 80 again, since they say it's "against their rules". Ugh.

[dt23]

Got it. www.zoneedit.com provides such a service for dealing with blocked ports, using their WebForward feature. Here is a part of their FAQ:

------------------------------------------------------------------------------------

My ISP blocked port 80. How can I run a web server?

Don't worry, you can still run one!

Sign up and get started with ZoneEdit.
Make your web server listen on port number like "6000" or "5000"
Check to see if your web server works in a browser by using a URL: http://3.4.5.6:6000/. Use the port number that you're listening on and the real IP address of your machine.
Add the "IP Address" for your web server in ZoneEdit: "ww2.domainname.com" points to "ip address".
Add a Web Forward entry for your domain called "www.domainname.com" that points to http://ww2.domainname:6000/
We recommend turning cloaking off in this case, letting people know thay are going to http://ww2.domainname.com:6000 is usually OK, and it allows the browser to perform better.
----------------------------------------------------------------------------------------

I'm sure there are other services out there... this was just the one I came accross.

[Gertrude]

Good detective work Grasshopper!

[quip]

I don't know if zoneedit charges for its services, but I believe dyndns (http://www.dyndns.org) does web redirection for free.

[posterboy]

Yup, AT&T has 80 blocked, and I have been using dns2go for some time now. They do charge, but it's a very small amount yearly, and the service is quite reliable. I use it to tack on my httpd port number at the end of IP addy, only if the name sought is www.raymondjones.net. If the name is simply raymondjones.net, they just provide my IP, allowing other services to work, unaffected. They have a rather friendly linux client for download.

[mrBen]

Don't forget to check your agreement with your ISP - just because you _can_ run a web server on a port other than 80, doesn't mean that it's allowed.

[posterboy]

For me, ANY server is strictly forbidden by the TOS. I have been running a dozen of them for years. AT&T, my provider, sends a "webpage snooper" in here, maybe every 3 months. It indexes every page, perhaps for a human to look at, to see if I am selling anything. I am not, and they don't say a word. I also subnet their IP addy, as you can see. I run sendmail, and from time to time, they "snoop" it, also, running a series of open relay tests. Not a word is said to me about all this, although, I am sure it would be if there was an open relay. A pal who works over there, told me it's a bandwidth issue. If you don't rise head and shoulders above other users in bandwidth, they really don't care. There are DSL providers who ALLOW servers, and the cable people know that. Not good business to run off paying customers, ya know? YMMV, but that's my experience.

[JohnT]

Go shopping...free and pay.....HERE (http://www.google.com/search?hl=en&ie=UTF-8&oe=UTF-8&q=dns+redirection&btnG=Google+Search)