Topic: non standard port

[Matthew]

Hi My ISP recently decided to block all traffic to port 80. I run e-smith 4.2 qmail, IMP, Apache Webserver with Apache MP3. I decided to purchase an http relay service from TZO. they forward all :80 requests to your domain to a non standard port. I choose :8069. I configured a custom template for httpd.conf to listen on port :8069 instead of :80. it works for the initial start page, but when I try to link to an i-bay or Apache Jutebox, or webmail, it wont work. it just does nothing.
I would appriciate any help
Thanks
Matthew

[Bruce Friedman]

Matthew,

Did you get the i-bays to work with a redirected port?  I have the same problem - works fine for static html, but not for php code.

Thanks
Bruce

[Matthew]

Hi Bruce
I gave up.
I hate my ISP and that is about as good as it gets. They are not only blocking incoming ports but outgoing as well.
I can of course change the default port in httpd.conf for the interface of my choice but then I have to deal with e-smith templates which was a pain in my situation. Any how changing the default port works but then other services like streeming audio and video are affected. So this was not a real solution for me.
When my contract is over with my cable provider i will look into DSL as a possible solution.  

[Bruce Friedman]

Matthew,

My situation seems to be OK now - I did run

/sbin/e-smith/signal-event post-upgrade

and reboot and now even the I-Bays seem to work OK on my new port.

I am using a cable provider (ATT@Home), and while they are blocking port 80 incoming, they are not blocking https or redirected ports.

Good luck on your new service with DSL.

BTW - Who is your cable provider?

Bruce