![Firefox logo](https://assets-prod.sumo.prod.webservices.mozgcp.net/media/uploads/products/2020-04-14-08-36-13-8dda6f.png)
Google Account Log In Problem - Buttons Fail To Work
Greetings:
Win11Enterprise_X64 , Firefox 114.0.2 (64-bit). Restart in safe mode yields the same result.
"Clear Cache and cookies": Now, I very often have this issue. I have 38 auto-logged in pinned tabs, of various sites, most of primary importance. Clearing the cookies ... is not quite an option, as this logs me out, what means, I have to manually log in to each site I am logged into right now.
Seeing this is a returning issue, which in my case happens quite a whole lot, and often to others (though likely in less amounts due to the fact I have many sites auto-logged in pinned and open)( I am wondering:
What exactly causes this? And since this is a recurring issue, not just for me, how come this has not been solved yet? I mean, there has to be a way, it can be fixed, right?
Seeing I do not add new extensions, and those I have do not update that often, it is not the add-ons. This is further proven by the fact that Safe Mode yields the same result.
Thus ... it is either caused within Mozilla Firefox, OR some site giving out "naughty cookies" that kill the button functions.
If the first: Then Mozilla has to fix this. If the latter, then Mozilla can create a system that "nukes" the naughty cookies. Call it for instance "The Sinterklaas Protection" (It's the Dutch Santa Claus version, who has a bag to put "naughty kids" in. Seems fitting. bagging "Naughty Cookies").
Thoughts?
Also, is there a way we can overcome this, an add-on or such?
Thank you: Xog.
All Replies (4)
PS: (Sorry, no edit function): I deleted all but the cookies (thus site prefs and whatnot: Issue remains, meaning, it has to be a "Naughty Cookie".
These seem to turn up more and more lately, which thus means, we need "Sinterklaas Protection" to safeguard our sanity and system by bagging (and clubbing into a bloody crumbs mess) these assailants.
Never liked cookies ... and for a good reason.
You can find "Edit this question" under the "Question Tools" menu in the sidebar. For a reply, "Edit this post" is in the three-dot menu next to a reply.
Do you mean that you did some troubleshooting with the Google login problem, but that you hesitate to clear the Google cookies ? Note that you do not need to clear all the cookies, only cookies for site that cause a problem Fore issues with Google website, this would mean the cookies for https://google.com
This could be a problem with the TLS 1.3 Early Data feature also known as Zero Round Trip Time Resumption (0rtt). You can try to set security.tls.enable_0rtt_data = false on the about:config page to disable this feature until this is fixed by Google or Mozilla to see if that helps.
See also:
- /questions/1376015 Issue with most Google sites on Firefox v100 64bit
You can try these steps in case of issues with webpages:
You can reload webpage(s) and bypass the cache to refresh possibly outdated or corrupted files.
- hold down the Shift key and left-click the Reload button
- press "Ctrl + F5" or press "Ctrl + Shift + R" (Windows,Linux)
- press "Command + Shift + R" (Mac)
Clear the Cache and remove the Cookies for websites that cause problems via the "3-bar" Firefox menu button (Settings).
"Remove the Cookies" for websites that cause problems:
- Settings -> Privacy & Security
Cookies and Site Data: "Manage Data"
"Clear the Cache":
- Settings -> Privacy & Security
Cookies and Site Data -> Clear Data -> [X] Cached Web Content -> Clear
- https://support.mozilla.org/en-US/kb/clear-cookies-and-site-data-firefox
- https://support.mozilla.org/en-US/kb/how-clear-firefox-cache
Start Firefox in Troubleshoot Mode to check if one of the extensions ("3-bar" menu button or Tools -> Add-ons -> Extensions) or if hardware acceleration or if userChrome.css/userContent.css is causing the problem.
- switch to the Default System theme: "3-bar" menu button or Tools -> Add-ons -> Themes
- do NOT click the "Refresh Firefox" button on the Troubleshoot Mode start window
cor-el said
Do you mean that you did some troubleshooting with the Google login problem, but that you hesitate to clear the Google cookies ? Note that you do not need to clear all the cookies, only cookies for site that cause a problem Fore issues with Google website, this would mean the cookies for https://google.com
Thank you, kind sir.
Edit function: Brilliant, thank you, very helpful.
Targetted cookies: Equally brilliant, most appreciated!!! This means, I can keep my logged into tabs as effectively logged into. Saves me quite a lot of manual logging in, each darn time this happens.
As for this error: TLS 1.3 Early Data: It is an ancient issue, which is confuzzeling me, that it is still around, after all this time. How come this has not been addressed by Mozilla? I am not the first, nor the only, to have reported this issue. Through the Mozilla Feedback as well.
Kind of bizarre, if you ask me?
Sorry, the latter part "As for this error" is not an actual question, sir. More me thinking out loud, hoping (probably totally uselessly, but hey, one can hope, right, sir?) a Mozilla Dev or so notices this. And does something about it.
On a different point: I often have like 28GB RAM in use for Firefox. Firefox REALLY loves my DRAM DDR5, but I dislike it liking it.
I have set my previous SSD System Drive into a VRAM drive, and told Windows to use that for the virtual ram. Firefox then, happily ignores this, for whatever reason.
Now, one can say, DDR5 is faster, sure. SSD then, is fast too, even if a bit slower. How do I tell Firefox to use my VRAM drive rather than my DDR5 DRAM? If at all possible, that is?
Thank you beforehand: Ben
Apologies, seems Quote double posted the quote, which I now undid.
Endret
cor-el said
Do you mean that you did some troubleshooting with the Google login problem, but that you hesitate to clear the Google cookies ? Note that you do not need to clear all the cookies, only cookies for site that cause a problem Fore issues with Google website, this would mean the cookies for https://google.com
Thank you, kind sir.
Edit function: Brilliant, thank you, very helpful.
Targetted cookies: Equally brilliant, most appreciated!!! This means, I can keep my logged into tabs as effectively logged into. Saves me quite a lot of manual logging in, each darn time this happens.
As for this error: TLS 1.3 Early Data: It is an ancient issue, which is confuzzeling me, that it is still around, after all this time. How come this has not been addressed by Mozilla? I am not the first, nor the only, to have reported this issue. Through the Mozilla Feedback as well.
Kind of bizarre, if you ask me?
Sorry, the latter part "As for this error" is not an actual question, sir. More me thinking out loud, hoping (probably totally uselessly, but hey, one can hope, right, sir?) a Mozilla Dev or so notices this. And does something about it.
On a different point: I often have like 28GB RAM in use for Firefox. Firefox REALLY loves my DRAM DDR5, but I dislike it liking it.
I have set my previous SSD System Drive into a VRAM drive, and told Windows to use that for the virtual ram. Firefox then, happily ignores this, for whatever reason.
Now, one can say, DDR5 is faster, sure. SSD then, is fast too, even if a bit slower. How do I tell Firefox to use my VRAM drive rather than my DDR5 DRAM? If at all possible, that is?
Thank you beforehand: Ben
Apologies, seems Quote double posted the quote, which I now undid.