I love Google's Chrome browser generally speaking, but for some reason, one of my laptops recently decided to stop displaying New World Notes in it, instead coughing up a "This webpage is not available" message with an "Error 101 (net::ERR_CONNECTION_RESET)" appended. (Somehow, it can still be viewed in an "Incognito" window. Curiously, the same message and workaround obtains for me with Terra Nova, another Typepad-based blog.) I've received at least one email from a reader having similar woes with NWN. Anyone else? And anyone have a solution?
Update, Noon: Added screen capture. To clarify further, I can still access NWN via Chrome on my second laptop on the same Internet connection, so it's not related to my particular DSL service. And I have the same problem when I take my no-NWN-on-Chrome-default laptop traveling outside San Francisco, so it's not related to my geographic region.
Oh! I thought it was just me! Yes, I can't read NWN in Chrome, I have to switch browsers to read it. Same error.
Posted by: Julia Banshee | Thursday, July 09, 2009 at 11:26 AM
Hmmm...I can read NWN with Google Chrome. I don't know if this is because I viewed the site with Firefox first or not.
Posted by: Kittenanne Mousehold | Thursday, July 09, 2009 at 11:32 AM
I have Chrome (2.0.172.33) installed in a VirtualBox running Windows XP Pro SP3. I was able to bring up NWN fine; in fact, this comment is being posted from Chrome.
Posted by: Erbo Evans | Thursday, July 09, 2009 at 11:49 AM
I have been reading NWN in Chrome for some time now without any major issues.
ERR_CONNECTION_RESET usually indicates that the webserver unexpectedly hung up in the middle of the conversation, so there may be something weird going on over there. Using a diagnostic tool like Fiddler may help track down the problem.
Posted by: Odysseus Fairlymeadow | Thursday, July 09, 2009 at 11:52 AM
Same thing in Mosaic. Weird.
Posted by: Adric Antfarm | Thursday, July 09, 2009 at 12:30 PM
Yeah, the problem is clearly conditional, but I have no idea what the conditions are. I used to read this blog with Chrome just fine. Then one day, while I was trying to preview a comment I wanted to post, I got the "connection reset" error. Ever since then, I can't even view the home page using Chrome, unless in an incognito window. That makes me suspect it has something to do with my cookies.
Posted by: Galatea Gynoid | Thursday, July 09, 2009 at 12:33 PM
I can see it in Chrome just fine. I've never had a problem.
Posted by: Neptune Rebel | Thursday, July 09, 2009 at 02:19 PM
I can read NWN with Chrome no problem. I ahrdly use any other browser these days. I can also read Terra Nova without a problem. I usually read both sites via RSS in Google reader, but made the trip to the site especially to check.
Posted by: Chris | Thursday, July 09, 2009 at 02:33 PM
I use Chrome and can view NWN and Terranova just fine every time.
Posted by: Gianna Borgnine | Thursday, July 09, 2009 at 02:33 PM
Yes I can see you in chrome...nice work on the blog
Posted by: me | Thursday, July 09, 2009 at 02:34 PM
I have Chrome running on both of my laptops & NWN looks fine on both. One is 3.0.192.1 and the other is 2.0.173.1. I also checked with version 2.0.178.0 (15300) of the Iron browser (based on Chromium, see: http://maketecheasier.com/iron-browser-a-secure-alternative-to-google-chrome/2009/07/08) and it looks fine there as well.
Posted by: IronGut McCallister | Thursday, July 09, 2009 at 02:38 PM
Thanks all, keep it coming. But ack, WTF is with my browser? I sure don't want to go back to Firefox, that sucker crashes like crazy on me (sorry Mitch.)
Posted by: Hamlet Au | Thursday, July 09, 2009 at 02:45 PM
I could read NWN in Chrome until yesterday, and then it just stopped working. Yesterday afternoon, I started getting error messages and blank screens. The problem persists.
Posted by: Doreen Garrigus | Thursday, July 09, 2009 at 02:50 PM
I've not had any problems reading NWN, and I've been using Chrome for months (currently using 2.0.172.33). If you can load it in an Incognito window, is there any chance that clearing history and cookies fixes the problem?
Posted by: Dupe Dollinger | Thursday, July 09, 2009 at 04:14 PM
Dupe, good advice; tried, no dice.
Posted by: Hamlet Au | Thursday, July 09, 2009 at 05:40 PM
Go into the settings and disable DNS prefetching. Clear history again and try it. Chrome works best for me with it disabled for some reason.
Posted by: Cerulean Zessinthal | Thursday, July 09, 2009 at 06:03 PM
I have no problems using Chrome for this site...
I don't use TypeKey or TypePad though, so maybe it is related to that somehow?
Posted by: Barefoot Ballinger | Thursday, July 09, 2009 at 06:57 PM
I've been using Chrome for a while now and have never had a problem reading this site. Maybe its you. ^^ :)
Posted by: Odette | Thursday, July 09, 2009 at 08:31 PM
I switched to Chrome a few months ago because Firefox suddenly started crashing constantly and I have never had a problem viewing any page - NWN or others.
It has no problems opening all 42 tabs at once in my "SL Fashions" bookmarks folder :)
Posted by: Faerie | Thursday, July 09, 2009 at 09:30 PM
Cerulean, thank you so much. I don't know if you helped Hamlet, but you helped me. I can see NWN in Chrome, now, with no problem at all.
Posted by: Doreen Garrigus | Friday, July 10, 2009 at 08:51 AM
It would appear that the webserver is bombing while attempting to process the request. There are scripts running on the webserver that are attempting to process information passed from the browser to the server on each request, and they must have a bug that's causing them to bomb under certain circumstances. I was having the exact same problem for about a week. But a few minutes ago, I went to "Clear browsing data...", selected "Delete cookies" and "Clear saved form data", selected "Everything" for the period, hit the "Clear browsing data" button, and now I am once again able to access this site in Chrome. Whatever data is was getting back from the browser was, either alone or in combination with the data in your backend database it was attempting to correlate that with, causing the webserver to terminate mid-processing. This isn't an obvious problem since webservers spawn many subprocesses to handle requests, and if one dies it just spawns a new one so people can still connect, but it kills the one request that was in progress when the crash occurred. Looking at the webserver error logs might reveal some clues as to the cause of the crash, although sometimes the server process can terminate before it gets a chance to log anything.
Posted by: Galatea Gynoid | Friday, July 10, 2009 at 10:51 AM
@Doreen
You are very welcome :)
Posted by: Cerulean Zessinthal | Saturday, July 11, 2009 at 06:38 PM
@Galatea ... ya what he said... Clear your private data and badabing.
Posted by: Adam | Monday, July 13, 2009 at 07:51 PM
OMFG Galatea, that worked! Thanks much much muchly!
Posted by: Hamlet Au | Monday, July 13, 2009 at 08:05 PM