Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
My ISP blocks port 80. Any way around this to run Apache web server?
- Thread starter amberashby
- Start date
- Sort by reaction score
You should be able to edit your httpd.conf and change the port number apache runs on. My Mac is away for repairs at the moment so I can't really tell you anymore, maybe somone else can help more.
Nikko1965 said:
My cable modem service is with Cox. I don't really have any alternatives. DSL in my area seems much slower.
I forgot to mention that I am using a Linksys router if that matters.
this might help:
http://www.macosxhints.com/article.php?story=2000112713143850
in a nutshell: you'll have to change your port number, and set up port forwarding on your router.
http://www.macosxhints.com/article.php?story=2000112713143850
in a nutshell: you'll have to change your port number, and set up port forwarding on your router.
You will need superuser access to your /etc/httpd/httpd.conf file
then change the line
#
# Port: The port to which the standalone server listens. For
# ports < 1023, you will need httpd to be run as root initially.
#
Port 80
to read, for example, if port 8000 is not blocked
#
# Port: The port to which the standalone server listens. For
# ports < 1023, you will need httpd to be run as root initially.
#
Port 8000
Then you will need to restart the httpd server, maybe reboot if you don't know how else to do this.
test it works buy putting
http://127.0.0.1:8000
into your browser and you should see either the default apache page or your index page depending if yoou set one up.
You will then need to setup your router to forward port 8000 (or whatever port you choose) to the ip address of your webserver
your site will then be accessible as
http://yourdomainname:8000/
Good Luck
then change the line
#
# Port: The port to which the standalone server listens. For
# ports < 1023, you will need httpd to be run as root initially.
#
Port 80
to read, for example, if port 8000 is not blocked
#
# Port: The port to which the standalone server listens. For
# ports < 1023, you will need httpd to be run as root initially.
#
Port 8000
Then you will need to restart the httpd server, maybe reboot if you don't know how else to do this.
test it works buy putting
http://127.0.0.1:8000
into your browser and you should see either the default apache page or your index page depending if yoou set one up.
You will then need to setup your router to forward port 8000 (or whatever port you choose) to the ip address of your webserver
your site will then be accessible as
http://yourdomainname:8000/
Good Luck
RoadKill said:
Hit the nail on the head there. It's going to be a pain to tell everyone, "Hey go to my web site at www.mydomain.com:8000, so I'd also recommend another ISP. You might also call Cox and ask what they can do.
I'm quite sure that there is a way to forward stuff so that even if you use port 8000 people will be able to get the site on the default http port (80). I'm not exactly sure how to do this though. Also, if you don't want to tell people to go to mydomain.com:8000, you could set up a free account at something like Tripod *shudders*, that redirects to your site with the port number.
No-IP.com has that now too.
If you don't want ports blocked, be prepared to pay some $$$. Speakeasy is one company that doesn't, but their service is much more expensive than Cox and since it's DSL, it has all that baggage too.
Counterfit said:
What baggage are you referring to? My DSL in Cincinnati is getting better than the cable providers, especially with upload speeds, which is the big factor in running a web site.
Now they are rolling out Broadband-over-Power-Lines (BPL) that is supposed to give you up to 3Mb up/down. It will be nice if it stays near the 3Mb mark, but if it is constantly dipping below 1Mb, then I think I'll stick with my current DSL. At least it is constant.
Well, considering most of my info is based on ads from Cox, I'd take my own words with a grain of salt.tomf87 said:
Of course, Verizon isn't exactly 100% in their "Cable vs. DSL" page either.
Well, considering Verizon isn't a Cable ISP, it would be rather hard to get any sort of cable line directly to the Verizon CO.
This is exactly the same as "Use the same line for Cable TV and Internet access"
And we pay for our internet access on our monthly Cox Cable bill, so again, this is exactly the same argument used for both sides.
Let's hear it for marketing! Were did the 100%-honest-no-spin companies go?