Koozali.org: home of the SME Server

Apache problem

Aurelien Derouineau

Apache problem
« on: August 20, 2001, 04:09:10 AM »
I run apache on e-smith 4.1.2. I try to access my web sites from the internet and it doesn't work exept with SSL (https) and FTP.

If you want, you can try to access it:
http://65.13.123.52

if it doesn't work, use https://65.13.123.52 (it should work fine)

Please send me your comments or solutions about it at aurelien.derouineau@home.com

Dan Brown

Re: Apache problem
« Reply #1 on: August 20, 2001, 05:35:21 AM »
Ten bucks says they've blocked inbound connection attempts on port 80.  Many broadband ISPs did this in the wake of Code Red II (which was overkill, but not too unreasonable considering that most of their AUPs prohibit servers anyway).

Aurelien

Re: Apache problem/ port 80 & isp / which isp
« Reply #2 on: August 21, 2001, 02:54:54 AM »
How do I send you the 10 bucks ?

You are right, they blocked port 80.

Beside going to T1, which I don't think I can afford, what are the other solutions to run a small server from a home ?

TKS for your help.

Dan Brown

Re: Apache problem/ port 80 & isp / which isp
« Reply #3 on: August 21, 2001, 03:04:30 AM »
Well, I guess you could send it via PayPal... (-:

A T1 (or fractional T1, or frame relay) would do the trick, but would (as you say) be expensive.  If your AUP doesn't prohibit servers, lean on them a bit and see if you can get them to re-open port 80.  Otherwise, consider DSL.  Some DSL ISPs, like Speakeasy (www.speakeasy.net), allow servers on their home connections.

Scott Smith

Re: Apache problem/ port 80 & isp / which isp
« Reply #4 on: August 21, 2001, 06:21:14 PM »
DNS2GO, the dynamic DNS provider, has an option to redirect anything beginning with "www." to any port. It is specifically to allow bypassing providers that attempt to thwart home web servers by blocking port 80. Other dynamic DNS providers may offer a similar feature.

You would need to reconfigure e-smith to run on something other than port 80, for example port 8080. I think this has been discussed on the forums before, so I'll leave you to search for that particular bit.

Once done, www.yourdomain.dns2go.com would be redirected to yourdomain:8080 thereby running the blockade on port 80. Other URIs not starting with "www." are not affected, so FTP and SSH for example work normally.

hth

Scott

Bill Scobie

Re: Apache problem/ port 80 & isp / which isp
« Reply #5 on: August 21, 2001, 06:47:58 PM »
I would suggest redirecting web traffic, not to port 8080, as that is another alternate "traditional" web service port which may be blocked by some providers.

See http://www.iana.org/assignments/port-numbers for a list to pick from. Search for the "Unassigned" ones, if you want to avoid problems with other ports you may be using now or in the future.