Blocked Port 80 -=- Outgoing HTTP Server

[JustinK101]

Hello All, Unfortunately I have Cox Cable High Speed Internet. I mean the speeds are great for how much I pay a month. But anyway the real complaint I have with Cox is that they block port 80 for outgoing http serving.

Currently I am running an email, ftp, and DNS server. Trying to run HTTP via Apache. The email, ftp, and DNS all work fine because Cox doesn?t block any of those ports.

I consider myself knowledge of Apache, DNS, and the inter-workings of the Internet. But, the blocking of port 80 has perplexed me. I have tried everything I can think of, currently I am running apache on port 8080 which works because this port is not blocked but there are a few issues with running a HTTP server on the non-standard port 8080.

-=- Users must specify the full address, such as: http://mysite.com:8080 including the port number.

-=- Users CANT call mysite.com:8080 from their browser, they must specify prefix http:// because 8080 is not the standard http web service port.

As you can probably observe, this is not going to cut it for serving a site. So hopefully one of you network gurus can come up with a fix. Let me explain what I have access to:

-=- FULL DNS Server control. { a records, cname records, mx records, ns records, etc }
-=- FULL Control of Apache httpd.conf

Other people have recommend no-ip services but I don't want to rely on another service to provide my site, after all, inst the point of running your own DNS, and Web Server, to have control and ovoid monthly charges?

Any information, insight, comments, would be great and appreciated. There was some talk about a redirect by a fellow I know. I would not care if users saw the port in the address, just as long as they did not have to call it directly. Thanks again.

 

[Bleep]

I would recommend that you not use port 8080 as this is the port that the Linksys router uses for its configuration. There are a lot of forwarding services out there that are free
Bleep

 

[Fuzznuts]

your screwed basically you could set up a site at www.domain.com that redirects to your home ip:8080 only way around it.

you will not be able to redirect the port through dns or any other means the firewall is out of your control you are goign to have to redirect in some way or another im afraid.

 

[skyking]

You are in violation of your Terms OF Service (TOS) if you are running a server. Sure they may not catch you, but go read the fine print on that thing you signed when they installed the service. You gave them the right to levy huge fines against you, and disconnect you from the web. If you get a bunch of traffic over 8080, they may find out.
There is cheap hosting available for 25-30 per year, I would suggest doing that instead of risking losing that cheap web access.

 

[idea]

afraid.org is one dyndns service that you could use, i have the same problem with optonline.net. but i setup a fwding host and pointed it towards myip:85, and it's fine.

 

[jonmullen]

Originally posted by: Fuzznuts
your screwed basically you could set up a site at www.domain.com that redirects to your home ip:8080 only way around it.

you will not be able to redirect the port through dns or any other means the firewall is out of your control you are goign to have to redirect in some way or another im afraid.

only way around it.