• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

server program?

nightelfmaster

Limp Gawd
Joined
Mar 28, 2004
Messages
267
whats the best server program out there besides apache, thats easy to use, and windows compatable (winxp)? i'm thinking about setting up a server, but when i use apache i can't get it to work when its not on my lan (yes i have static nat/dmz/whatever you wanna call it, enabled for my computer) and my isp blocks port 80, so i need a program that can get around it by using a different port.

well for those that think apache is the best, can someone explain to me how to use a domain name such as mydomain.dyndns.net and use a port like 81 for requests?
 
lol, search the apache .conf for port .. theres a far amount of 'faq' content already in there :)
 
Um

I really don;t think you ISP Block port 80 but if they do change it to port 81 and if that doesn't work change it to port 82 and if that doesn't work change it to port 8527 :p
 
Why is it so unlikely? I know a few ISPs which block inbound requests on port 80, to stop exactly this situation occurring ;)

slyguy63 said:
Um

I really don;t think you ISP Block port 80 but if they do change it to port 81 and if that doesn't work change it to port 82 and if that doesn't work change it to port 8527 :p
 
:LJ: said:
Why is it so unlikely? I know a few ISPs which block inbound requests on port 80, to stop exactly this situation occurring ;)

Happened to me. I went from Wide Open West (which really was wide open--no ports blocked at all) to Charter, and found that I could no longer use port 80. Like others have said, it's no big deal--just switch ports to something not-so-standard. I tend to like 8080.

Remember, though, that this means that you'll be requesting something like:

http://www.example.com:8080/

That extra bit :)8080) specifies the port to which you want to connect.

I suppose, too, that you wouldn't even have to reconfigure your server if you had a good router. (Others may correct me if I'm wrong.) That is, couldn't you just have people request www.example.com:8080 but have your router re-route that to port 80? Like I said, I'm not really sure, but I think it might be possible...
 
no 'cos the routing where the ports are concerned are done at a higher level
 
p3n said:
no 'cos the routing where the ports are concerned are done at a higher level

No, see, I'm still saying to request port 8080, but I'm not sure you'd have to have your server reconfigured.

To be honest, strike everything I said. Loopback craziness can happen with different ports, so just have everything on port 8080 (or whatever number you choose) and be done with it. :)
 
:LJ: said:
Why is it so unlikely? I know a few ISPs which block inbound requests on port 80, to stop exactly this situation occurring ;)

Ha

If my isp blocked any ports below the first 1024 I would be looking for a new ISP. Your right some do most don't. They do this to only make more money. You call them up and say, " Why is port 80 and 20 block, and they say those are reserved for business connections, you need to pay this to get a business connection to be able to use port 80 and 20."

That to me is a crock of shit :)

nobody owns port 80/20 and if I want to setup a web page or ftp and my ISP is blocking them, so long.

There is probably 10 to 1 per web page and ftp. 10 personal use to every 1 business use.

If this is only a way to make more dough for there pocket I don;t think there are a very classe` business, which is really sad I think :(
 
ok i did everything you guys told me to, but it still doesn't work... i set the listen in the conf file to 10101, and went to (my ip):10101 but it still doesn't work, but 127.0.0.1 works
 
To get to (your IP):10101 You'll have to enable packet forwarding, if I'm not mistaken.

Er, you do have a router, right?
 
my router doesnt understand my WAN address when im inside it, if you catch my drift - just use localhost or wahtever the ip is locally and get someone to test it for you from 'outside' .. ie us :)
 
In case you were thinking about doing this, DO NOT POST YOUR IP ADDRESS HERE. If you want someone here to test it, just PM them.
 
you can always change the http port in httpd.conf to respond to another port besides port 80.
 
how do i change it to respond to a different port? i changed the "listen 80" to "listen (port x) and changed the part where it says "(domain name):80" to "(domain name):(port x)"
 
Back
Top