http://www.resonant.org/node/485 Comments for "And now port blocking!" en http://www.resonant.org/node/485#comment-63 <p>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.</p> Wed, 16 Mar 2005 11:18:28 -0500 Zed comment 63 at http://www.resonant.org http://www.resonant.org/node/485 <p>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.</p> <p>Those who are seeing this anyway should take note that port 443 is NOT being blocked, so you can still access the site by:</p> <p><a href="https://www.resonant.org/" class="bb-url"><a href="https://www.resonant.org/">https://www.resonant.org/</a></a></p> <p>(Note the https rather than the http.)</p> <p><a href="http://www.resonant.org/node/485">read more</a></p> http://www.resonant.org/node/485#comments Annoyed Frustrated Announcement Wed, 16 Mar 2005 00:58:49 -0500 Zed 485 at http://www.resonant.org