PORTS 80 and 8080 BLOCKED!

vbp6us · 10-09-2002, 11:31 PM

Hi,

I just got done talking to Roadrunner's tech and he said ports 80 and 8080 are blocked. What ports can i use for my webserver then? I need really unique ports. I changed my ports to some randome numbers and it didnt work. I tried 8081, 8088, 81 and any other port that is probably thought of. What am i missing? When i go to my url...it says "connection refused ...."

DAMN. What alternatives do i have??

moses · 10-10-2002, 12:47 AM

Port 81 is commonly used for testing webservers (unless the machine is
running a nameserver).
Look in the file /etc/services, this will tell you which ports are currently
reserved. Most other ports are available, though this isn't certain.

Telling your webserver which port to listen to is dependent on the server.
For example, apache probably has a file called "httpd.conf" in /etc/apache.
This file can be edited to tell apache to listen on another port. You need
to read the documentation for your specific web server before you start
mucking around with the configuration files. . .

You say you changed your ports to some random numbers, what do you
mean? where did you change them? how did you change them? are
those ports blocked as well? have you tried connecting to localhost:port#
with your web browser?

trickykid · 10-10-2002, 01:04 AM

Quote:

Originally posted by vbp6us
Hi,

I just got done talking to Roadrunner's tech and he said ports 80 and 8080 are blocked. What ports can i use for my webserver then? I need really unique ports. I changed my ports to some randome numbers and it didnt work. I tried 8081, 8088, 81 and any other port that is probably thought of. What am i missing? When i go to my url...it says "connection refused ...."

DAMN. What alternatives do i have??

Yeah, sometimes they aren't blocked depending on where you live at, but be careful, they catch you running a webserver, they will dosconnect you for abuse.

But one trick I know of, make your webserver seem to be non-public if you get it going by making it prompt for a password when accessing it. This is one way around, its a hassle I know but also to warn you, even if you get it going on another port, they do scan other ports, so if they catch you, they will shut you down for abuse.

What type of site are you wanting it to be ? A personal or something else ? Also, when trying to get access after changing ports, did you specify the port after typing the address or IP number ??

BTW, I work for Roadrunner, that's why I know all these things.. but lucky me, my last day is this Sunday, starting a new job cause I got tired of all the BS they had there. They started making us take cable tv tech calls a few months ago, only gets worse everyday now. Its not support anymore, more of a whiny complaint line.

But I'll be starting at www.digitalmotorworks.com for anyone who wants to know. A little more money doing support, not what I want to do, but I have a better chance of moving up to other departments.

vbp6us · 10-10-2002, 11:37 AM

Quote:

You say you changed your ports to some random numbers, what do you mean? where did you change them? how did you change them? are those ports blocked as well? have you tried connecting to localhost

ort#
with your web browser?

Im changing these ports by editing httpd.conf of course. How else would i do it w/ an apache server? When i insert the line "Listen 8081" i still leave my Listen 80 right? Or do i have to remove it for port 8081 to work?

All im doing is adding lines...i havent removed any other Listen lines.
Please remember im a

. I know enough to edit the conf file and start and stop the server.

Quote:

Yeah, sometimes they aren't blocked depending on where you live at, but be careful, they catch you running a webserver, they will dosconnect you for abuse.

You dont work in San diego do you? NM...Austin TX, Damn. I dont really care if they do disconnect me...i'll just sign up w/ DSL and get a static ip along w/ it. I know dsl isnt as "stable" as cable but whatever. I dont think dsl companies block ports.

Quote:

make your webserver seem to be non-public if you get it going by making it prompt for a password when accessing it. This is one way around, its a hassle I know but also to warn you, even if you get it going on another port, they do scan other ports, so if they catch you, they will shut you down for abuse.

What type of site are you wanting it to be ? A personal or something else ? Also, when trying to get access after changing ports, did you specify the port after typing the address or IP number ??

I don't know if i want to put a password. Its going to be a personal site. Nothing going to be sold.

I was on irc last night and some guy said to used port 23048. Is that a real port? Is it a safe port? Since you work for RR...do you know if you guys block this port or if any of your branches block it? Oh and can you give me a list of good ports, open ports to use or try since your a RR employee you have access to viewing ports and stuff.

When trying to access my server i type what i typed in my DNS control center at afraid.org. i put mydomain.com at the DNS site but when i type it in the browser i put mydomain.com:81 or whatever port im trying. Oh one more thing. When i do localhost in the browser it gives me "connection refused" also. 127.0.0.1 however works and goes to SUSE's webserver test page. I checked my conf file and 127.0.0.1 is next to localhost so they are the same thing! I have no idea what is going on. That could actually be the problem huh? Some thing about localhost not sounding right? Thats my guess. What do you guys think?

Thanks

trickykid · 10-10-2002, 11:50 AM

Well, unfortunately I work in Austin. They don't block any ports except 80 so I am unsure of what ports they block in San Diego. Not sure about 23048, ports range from 0 to around 65,000. I'm sure it would work but it seems more of a hassle to me cause then you would have to include the port number with your address.

Try removing the listen 80 in your config and try maybe ports 81 or so. Also did you just register this site and did you setup your own DNS or have some sort of DNS pointing to your IP number ?? Your probably given a dynamic which can change, might want to look into www.dyndns.org or something like that to host your own site with a dynamic IP.

vbp6us · 10-11-2002, 07:55 PM

Thanks.

moses · 10-12-2002, 01:12 AM

I use:
/usr/sbin/apachectl start
/usr/sbin/apachectl stop
/usr/sbin/apachectl restart

to start, stop and restart the apache webserver respectively.

My httpd.conf file is:
http://pirlwww.lpl.arizona.edu/~mmilazzo/httpd.conf

I can connect to both port 80 and 81 w/out a problem using:
http://localhost:80
http://localhost:81

Do you have port XX blocked on your computer (via firewall or inetd or
xinetd or hosts.deny)?

trickykid · 10-12-2002, 02:35 AM

Quote:

Originally posted by vbp6us
New problem:

when i try http://127.0.0.1 or http://localhost it gives me "connection refused."

IF you want to see my httpd.conf then here:

linux:/home/walham # /etc/init.d/apache status
Checking for httpd: running

Heres ALL of my httpd.conf in screenshots from the beggining to the end:

You know, you could have just done a:

cat httpd.conf > apache.txt

Or most browsers actually read the .conf files with no problem as text files, could have just uploaded the httpd.conf file for viewing as is..

And linked it to a text file for web viewing. 39 screenshots had to take you a while.

Syncrm · 10-12-2002, 10:56 PM

omg... i'd love to help, but there's no way i'm sitting here on dialup (at my parents', currently) and going through all those.

like tricky said, most browsers can read .conf or any type of text file without a problem. just put your httpd.conf file online somewhere so we can take a look at it.