Topic: Web Site Issue

[Milan Stejic]

I have been running E-Smith for several months now quite happily.  Recently I thought it might be a good idea to reboot my system (after 100+ days) to see if the Code Red virus would stop looking for my server.

After rebooting I have found that the only way to access my web site is by making the web access SSL secure (i.e. access https://www.mydomain.com rather than http://www.mydomain.com).  This has got me somewhat perplexed since I have not found any reason that this should have changed.  I have gone through all of the web based configuration and found nothing that should have affected this.

BTW, the site in question is stejic.dyndns.org if anyone is interested to look.  Currently the only way to access the site is https://stejic.dyndns.org.

Help on this issue would be greatly appreciated.

Thanks in advance,

Milan

[John Goodwin]

Hi Milan,

Thanks for the post because it was very helpful to me in regaining some level of external access to my website.  Hopefully my post will help you also.  Many ISP started blocking the http port last week in an attempt to control the code red virus.  I know that AT&T has done this and I assume many other ISP's are doing the same thing.  Of course, I didn't think about the fact that secure connections are on a different port.  After looking at your post, I tried a secure external connection and it worked. Now at least I have some level of access externally.  Of course, I now have to go change all of my hyperlinks to https, but its better than no access at all!

Thanks,
John Goodwin

[Milan Stejic]

Hi John,

I'm glad I was of help to you  You've been of help to me as well

Yesterday I had the thought that my service provider started blocking their incoming http ports to control the virus.  I called @Home to confirm this.  I talked to several people until I finally got to their virus control team.  He said that they had done nothing that would prevent access to my system and that they were not blocking any ports.  These comments had me perplexed given my diagnosis.

My system currently has all of it's existing functionality except that you can not access the web site via http.  I was left thinking I had misconfigured something on reboot given what my provider told me.

Based on your response I'm now pretty sure my provider gave me incorrect information ... which means I'd be waisting my time if I tried to fix my server  Hopefully they will restore service to normal in a few days.

BTW, you do not need to change any links on your web site.  Your entire site should work fine with https if you are using relative links.

Have a good day and good luck with your provider!

Milan

[Craig Foster]

Ditto for that. I'm checking some other possible reasons.

https://fostware.dyndns.org works perfectly as well as SSH, FTP, etc - just not http. My provider denies blocking port 80 as it's a large part for their business. (And they can sell their prebuilt virus-scanning gateway boxes to keep you're machines happy)

Regards,

Craig Foster