Try disabling all your extensions except for MetaMask.

Try changing DNS over HTTPS (DoH) to "Off" or "Max Protection" and in Connection Settings change "Use system proxy settings" to "No proxy".

Thank you zeroknight for your reply.

I checked my extensions, MetaMask is the only one enabled. I changed the DNS over HTTPS (DoH) to "Off" (I also tried "Max Protection"). In Connection Settings I changed to "No proxy". Then I shut down my desktop and restarted. I opened MetaMask and got the endless spinning wheel, still not able to login to my wallet. Any additional suggestions would be greatly appreciated.

A odd suggestion maybe but could you try clearing your cache & deleting any cookies for MetaMask in the Settings area of Firefox? Some issues where sites refuse to load correctly or do other super weird things happen when their cookies get corrupted. Clearing them sometimes magically fixes the weirdness.

Clear cookies and site data in Firefox for current site you're viewing

If that doesn't work, you could try clearing out all the cookies (becareful you'll have to relogin to whatever sites that set cookies to stay logged in). That could catch another domain's cookies that MetaMask might rely on to properly login.

Try looking at all the cookies first though just to see what sites you have in there: https://support.mozilla.org/en-US/kb/clear-cookies-and-site-data-firefox#w_clear-cookies-for-any-website

You can check the Browser Console for messages related to metamask.

• https://firefox-source-docs.mozilla.org/devtools-user/browser_console/

You can check the Web Console (Tools -> Web Developer) for messages about blocked content and about the presence of mixed or unsafe content. Also enable XHR and Requests

• https://firefox-source-docs.mozilla.org/devtools-user/web_console/

You can check the Network Monitor to see if content is blocked or otherwise fails to load.

• https://firefox-source-docs.mozilla.org/devtools-user/network_monitor/

If necessary use "Ctrl+F5" or "Ctrl+Shift+R" (Mac: Command+Shift+R) to reload the page and bypass the cache to generate a fresh log.