Michael Gray

Google Reader Throwing Errors

Posted on October 10th, 2007
by Michael Gray in Google



If you're new here, you may want to subscribe to my RSS feed. Read my top posts or learn more about Michael Gray. Want more frequent updates follow me on Twitter. Thanks for visiting!

Anybody else having a problem with Google Reader throwing errors? I’ve been getting this for the past 2 days and I’ve tried a dozen times, rebooted, restarted, and all that jazz.

Image

Sphere: Related Content

Text Link Ads


9 Responses to “Google Reader Throwing Errors”

  1. User GravatarDankind Says:

    I’ve been having the same problem. It’s happening with firefox only it seems. Works fine in IE and Safari.

    http://groups.google.com/group/google-reader-troubleshoot/browse_thread/thread/bbe00826345963f8/0bcd1bc00532eb07

  2. User GravatarDankind Says:

    Actually.. it appears to be google gears, if you disable that and restart firefox it works again.

  3. User GravatarMichael Stubblefield Says:

    I don’t have google gears installed and I’ve been having issues with google reader the last couple days as well using firefox, mostly with refreshing unread counts and displaying new posts.

  4. User GravatarTodd Mintz Says:

    I get this error periodically in IE…and not just in the last couple of days. I don’t use Google Gears.

  5. User Gravatarsimon Says:

    Errors, as well as some trouble marking as “read.” Seem to get better results with IE though.

  6. User Gravatarbranden Says:

    diddo. won’t work in FF but ok in IE. i assumed its gears as well but can’t make work despite disabling that.

  7. User GravatarEric Lander Says:

    Like those before me, I’ve been getting similar errors in FF.

  8. User GravatarSusan Says:

    I was having trouble yesterday but after I went off and sulked for a bit, it stopped giving me errors. I don’t use Google Gears but I do use FF.

  9. User GravatarMihai Parparita Says:

    Sorry about the “Oopses”, that was a bug that was exacerbated by having Gears installed. We’ve pushed a fix a couple of hours ago, a reload should pick it up.

    Mihai Parparita
    Google Reader Engineer