This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

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

This thread was archived. Please ask a new question if you need help.

Gmail will not open starting 1/12/22.

  • 2 replies
  • 2 have this problem
  • 4 views
  • Last reply by Gary

Gary
Gary
more options

Gmail stopped working 1/12/22. Latest updates for Win11, FF96. Works just fine on Win11 using Chrome, or iOS15.2. Need a fix.

FF will open Google and other apps from Google, but not Gmail. Just get a blank screen. No error message, no partial opening.

Gmail stopped working 1/12/22. Latest updates for Win11, FF96. Works just fine on Win11 using Chrome, or iOS15.2. Need a fix. FF will open Google and other apps from Google, but not Gmail. Just get a blank screen. No error message, no partial opening.

Chosen solution

Show this section when on Gmail. see screenshot Sounds like something is being blocked.

Read this answer in context 👍 0

All Replies (2)

jonzn4SUSE
jonzn4SUSE
  • Top 10 Contributor
more options

Chosen Solution

Show this section when on Gmail. see screenshot Sounds like something is being blocked.

Gary
Gary Question owner
more options

Didn't understand the response, but went into Google's privacy settings and made a few changes that I can't recall. Then opened FF again, and it asked me to sign into my Gmail account. Now it is functioning correctly.

Apparently the issue had nothing to do with either the OS or the browser. Interestingly, that was on my laptop which I use most of the time. My desktop didn't have the problem, and using Chrome the problem didn't exist on the laptop, which is what made me believe it was related to Firefox.

In any case, all is well now.