We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

FireFox 13 Beta won't log in to my Google Calendar Web Page

more options

I just upgraded from FireFox 12 to FireFox 13 Beta, and it seems to have solved the problems I was having with slow loading web pages in FF12. However, I find that I can't log in to my Google Calendar with FF13 Beta, although I can with other browsers - I.E., Opera, Chrome.

Any suggestions?

I just upgraded from FireFox 12 to FireFox 13 Beta, and it seems to have solved the problems I was having with slow loading web pages in FF12. However, I find that I can't log in to my Google Calendar with FF13 Beta, although I can with other browsers - I.E., Opera, Chrome. Any suggestions?

Chosen solution

I've edited this post to delete some questionable information and keep only what I'm sure works for me.

The network.http.keep-alive setting to false seems to provide the biggest improvement, but I think setting network.http..max-connections to 64 may have helped a little in my case, since I have a fairly slow "high speed" connection

I've also re-installed FF12 with these changes, and the issue seems to be resolved.

For now, this seems to have resolved my issues. If things start going downhill, I'll be back.

Thanks to everyone for all the help and suggestions. ent, but I think some of the other may have helped also.

For now, this seems to have resolved my issues. If things start going downhill, I'll be back.

Thanks to everyone for all the help and suggestions.

Read this answer in context 👍 0

All Replies (9)

more options

hey - another user on the forum has reported, that the problem only occured when the network.http.keep-alive preference in about:config was set to false.

could you have a look if this is also the case on your system? if so please try toggling network.http.keep-alive to "true" (the default value) & network.http.spdy.enabled also back to "true" and see if the sites are still loading normally. because if SPDY is enabled & actually works right this would bring you a performance benefit when loading pages that support the protocol...

if network.http.keep-alive was already set to true, could you look at the other preferences that start with network.http. & see if any of those is not on its default value (=shown in bold) & report it here. this would help further troubleshooting the issue.

more options

This really helped, thank you for your time.

more options

Confirm. Keep-alive and spdy.enabled both "true" works. I had keep-alive set to false. That seems to have been the culprit. Many thanks!

more options

That works!! I also had keep-alive set to false from being problematic on certain setups but SPDY enabled and keep-alive enabled now works fine on gmail/google stuff, thanks for solving!! :)

more options

ok, thanks for checking back & confirming the cause of the issue. this bug will apparently be fixed by other changes in the networking core of firefox 14 anyway. so for other users affected, who don't want to change the network.http.keep-alive pref to true (for whatever reason), using the beta version of firefox 14 might be an alternative.

more options

I can't access any accounts of Google or YouTube

Here is a screen shot of what I get when I try, http://i1065.photobucket.com/albums/u399/ehecatl2/random%20images/code.jpg

I had this problem months ago and fixed it one time by clearing cookies but that does not work anymore.

Of course it is impossible to go on any Google forums to find out about this.

If it is this SPDY thing, would somebody describe exactly how to disable SPDY. I looked around a little and don't have a clue.

I really hope someone can help with this. My OS is XP.

Modified by DanielMiller

more options

Ok, I found the SPDY settings. I have 3 of them; enabled, enabled.v1, and enabled.v2. I tried toggling them and nothing seemed to work. Do I need to reboot?

more options

Wow Dude, I kept screwing around with things turning things on and off at random to see what would happen, and got this combination to work, by turning off the following switches -

network.http.spdy.coalesce-hostnames  ;false

network.http.spdy.enabled  ;false

network.http.spdy.enabled.v2  ;false

network.http.spdy.use-alternate-protocol  ;false

Modified by DanielMiller

more options

Oh, and I got to that by putting this in the address bar - About:config

You techies seem to know this but other people visiting this thread may not.

  1. 1
  2. 2