Login by Google OpenID fails in FF 4.0.1 with an HTTP 403 error

Question

I cannot log in to StackExchange.com or Cooking.StackExchange.com.

I tried Cooking first, using this URL:

When I clicked "Allow," I got

HTTP Error 403 - Forbidden You do not have permission to access the document or program you requested.

So I tried StackExchange.com and had the same problem.

UPDATE
I just tried StackExchange again using IE7 instead Firefox and it worked. FF fail? I have v4.0.1.

@Chichiray - I cleared my cookies and now I can't even login to meta-stack using FF >.X...programmers is broke too. All my stacklogins are busted. suweet... — P.Brian.Mackey, Commented May 5, 2011 at 21:55
After searching through some related questions I see I can email [email protected] regarding the issue. So I shall... — P.Brian.Mackey, Commented May 5, 2011 at 22:06
Gee, I am so sorry. How do other browsers like FF3, Chrome and Safari behave? You can of course send the mail. Don't forget to mention that you already posted a Q on meta (this one :) ). — user138231, Commented May 5, 2011 at 22:07
Jeff on the SO team at [email protected] told me to disable all my browser add-ons. This resolved the issue. I don't know which add-on caused it, but the ones I want to keep don't affect it so I'm good to go. — P.Brian.Mackey, Commented May 6, 2011 at 13:07
Can someone tell us what generates this? I have this on Chrome — sorin, Commented Mar 5, 2013 at 11:56

Pops · Accepted Answer · 2011-10-25 15:13:04Z

4

According to the OP, this problem was caused by an unspecified Firefox add-on, and is resolved.

Please upvote this answer to get this question off the "unanswered" list.

answered Oct 25, 2011 at 15:13

community wiki

I have the same problem with Chrome, it happens quite often and is very annoying. How can we find the real cause?
– sorin
Commented Mar 5, 2013 at 11:55
@SorinSbarnea nobody is ever going to see your comment to this old, obscure post. (I only saw it because I got a notification about a comment on a post I wrote.) If you're still having this issue, you're better off posting a brand-new question and linking to this one.
– Pops
Commented Mar 5, 2013 at 15:15

Add a comment |

sjbx · Accepted Answer · 2013-06-05 10:59:08Z

1

I had this problem and disabled my Firefox Add-ons one by one to find it was Vimperator.

This was FF 19.0 on Ubuntu with Vimperator 3.7.

answered Jun 5, 2013 at 10:59

sjbx

1111 bronze badge

Add a comment |

2 Answers 2