And now port blocking!

Over the last couple weeks, half of my main entries have been announcements of one technical problem or another, and the trend continues tonight. It appears that port 80 is now being blocked by my provider (Cox) on SOME connections (but not all), despite the fact that I'm on a business account that is not supposed to have any blocking whatsoever.

Those who are seeing this anyway should take note that port 443 is NOT being blocked, so you can still access the site by:

https://www.resonant.org/

(Note the https rather than the http.)

I tested this by connecting from a few different hosts where I have accounts. Routing through one particular local proxy lets me access by http. Connecting by https always seems to work. Connecting by http doesn't seem to work from most of the sites, but then works on one. I'm not quite sure yet exactly what is going on, but I have some suspicions.

Trackback URL for this post:

http://www.resonant.org/trackback/485

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Or maybe not port blocking, but fixed now

Cox denies having done this deliberately, and whatever it was seems to have cleared up. I guess I can blame a freak router misbehaviour somewhere upstream of me.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.