After upgrade to Firefox 147.0.1 Gemini no longer works
I waited for a long time to do an upgrade to avoid problems. Today finally I decided to upgrade to the latest version of Firefox for my iMac, 147.0.1. Before the upgrade I successfully used with zero issues gemini.google.com/app . Now the website comes up, but regardless what I enter as a question I only get an error message stating "something went wrong". The same website works with no issues (TG) with Safari.
Does anyone else experience the same? Is this a known bug with this version of Firefox? Is there a work around for it? Is the solution just using Safari?
被選擇的解決方法
Hi Sue,
Sorry to hear that! Here are some standard troubleshooting steps that may resolve the issue:
- Please check if you have Enhanced Tracking Protection (ETP) enabled. You can do that by clicking the shield
icon at the left of the address bar.
- If ETP is enabled, try disabling it.
- If the problem is not fixed, try clearing Firefox cache.
- If it does not help, also try clearing cookies and data for Gemini (warning: you will be logged out on this website).
- If it also does not help, try running Firefox in Troubleshoot Mode. If the problem doesn't persist, please follow the steps from this article to troubleshoot further.
Does any of that help? Looking forward to your update!
從原來的回覆中察看解決方案 👍 1所有回覆 (2)
選擇的解決方法
Hi Sue,
Sorry to hear that! Here are some standard troubleshooting steps that may resolve the issue:
- Please check if you have Enhanced Tracking Protection (ETP) enabled. You can do that by clicking the shield icon at the left of the address bar.
- If ETP is enabled, try disabling it.
- If the problem is not fixed, try clearing Firefox cache.
- If it does not help, also try clearing cookies and data for Gemini (warning: you will be logged out on this website).
- If it also does not help, try running Firefox in Troubleshoot Mode. If the problem doesn't persist, please follow the steps from this article to troubleshoot further.
Does any of that help? Looking forward to your update!
Thank you very much @Denys. Clearing the cache and cookies appears to have solved the problem.