ChatGPT has stopped working in Firefox

Broken. Blank screen on Firefox today. Dumped my browser cache, cookies, restarted, etc., still nothing. Works on Chrome :frowning:

1 Like

Same issue, came looking for a solution, tried all of the above too, to no avail.

When I go to chatgpt .com and click on “Log in”, nothing whatsoever happens. Even the left, animated side of the homepage is missing. The whole thing’s just completely dead in Firefox (115.15.0esr (64-bit)).

I can log in using Opera (85.0.4341.22), but the UI stays blank except for the three buttons at the top, same as it was in Firefox before I cleared the cache/cookies etc. to try again. When I click on “New chat”, nothing happens.

It works in Chrome (Version 109.0.5414.120 (Official Build) (64-bit) … I know … :wink: ).

Came here from a search result. Same issue. Blank screen in Waterfox (a Firefox fork) which had been fine up until a few days ago. What gives?

i can not working 2-3 days. It 's blank chat, then after clearing cache, unresponsive login button…Firefix 115.15.0esr (64 bit) in MacOS

1 Like

hi guys, encountered same exact issue as one of the recent replies. im using mercury which is a firefox fork. tried cleaning all caches and cookies for both chatgpt and openai domains, using a vpn and incognito mode, but had no luck. what helped was updating my browser to the latest release which is v.129.0.2.

1 Like

i also got same problem blank screen on firefox where i only use firefox !!!
blank screen with only text are not working !!!

2 Likes

I started having this problem a few days ago. I’m using an Ubuntu 22.04 machine. I can use chatgpt on chromium but i can’t on firefox. Just a blank screen with the chatgpt textbox opens but i can’t input anything

3 Likes

The same here. Firefox on Debian Bookworm. Disabling all extensions does not help.

The current issue is, that openai changed its website to use “Intl.Segmenter” which is not supported by Firefox ESR 115.

“Intl.Sgementer” is a new features widely supported by current browsers. It’s part for Firefox since Version 125 but not implemented for FF 115 ESR.

Using a Tampermonkey script can implement a workaround for users on older browsers. Hence I’d recommend to upgrade to a newer version of Firefox. FF 128 will be the next ESR and supports Intl.Segmenter. Login to ChatGPT is possible!

Solution: Update to Firefox 128 ESR.

Download links are not supported here, so just Google for site:mozilla.org /pub/firefox/releases/128.2.0esr/

The problem for me was my FireFox-ESR v115.1.0. I updated to regular FireFox 130.0.1 from the command line. It solved all my problems.

There is a clue in the Developer Tools | Console output window.
“Intl.Segmenter is not a constructor…”

I queried ChatGPT on a laptop that actually still works. It noted that Intl library is newer and suggested that v115 ESR might not support it properly. Thus the need to update to the latest version instead of the Extended Service Release (ESR) version.

HTH

I was able to get ChatGPT to start working in Firefox (115.15.0esr, snap version, Ubuntu 24.04) by:

  • sign in using Edge
  • delete the most recent topic
  • restart Firefox

Hope this helps.

I stopped using chat gpt for month because of this issue, tried again with the newest firefox on arch, still doesn’t work, I’m getting input stream errors, chromium works ok.

EDIT:
greasemonkey polyfill link from the previous comment worked for me

Here is how I fixed the issue of ChatGPT not working on Firefox:

  1. Open Inspector tools (right-click → Inspect, or use the shortcut Ctrl + Shift + I).
  2. Go to Storage and delete all local data (right-click on Cookies → Delete All, then do the same with the other options there).
  3. Refresh the page.
  4. Reconnect.

it stopped working for me as well try clearing your cache, for me i just cleared the cookie’s from the connection icon ( the lock) that is next to the url simply click on it and then click on (clear cookies and site data)

Perfect, so easy and it worked!

Same here. I’ve been having nothing but issues for the past 3 or 4 days.

Just a +1 from Firefox on Windows. I hate that ChatGPT is forcing me to open Chrome ..

(Clearing cache and cookies didn’t do anything (except log me out))

1 Like

Another +1 from me. The page loads but none of my chats will load and I can’t click on any of the buttons. A full browser restart sometimes works for a bit but then it goes back to this broken state.

2 Likes

Okay, actual solution involving code.

If you look in the console you’ll a lot of warnings and in my case, an error at the top saying Uncaught (in promise) TypeError: Performance.mark: Expected startTime >= 0. My hunch is that maybe Firefox doesn’t allow Performance.mark to have a startTime < 0, but OpenAI (or a package they use) is doing some funk with specific timings and state causing a race-condition.

I’d have a cool image of the error here, but I can only add one image as a newbie

This race condition sometimes causes errors. So what I did was click the file-link top right of the error. You can see in this next page that the r - performance.timeOrigin is the issue here. So right-click on the file and select “Add script override” (which lets you use a file on your computer rather than their code).

Dump the file somewhere. Then do a Ctrl-Replace with “performance.mark(t,{startTime:r-performance.timeOrigin})” to “performance.mark(t,{startTime:Date.now()})”. Save, wait for any linters you have enabled to have a breakdown, then refresh the page.

And if your problem was the same as mine, it should work. It’ll likely last for about three days until they release a new update, but I figured I’d tell people.

Tom

Okay, just expanding on this answer. My solution above resets every time you reopen Firefox, so I built an extension that goes further and mostly solves the issue. Wildly, this forum doesn’t let us post LINKS!? So.. go to my profile and check my bio or just look here.

.

That repo has a link to code, that if you know how, you can package up as an extension and it’ll fix the issues some of us have been facing. I’m also working on wrapping it up as a proper extension. I’d link that, but apparently a forum can’t have hyperlinks in todays world.

Tom