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.

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

Twitch Error with Version 105.0.1

  • 14 பதிலளிப்புகள்
  • 3 இந்த பிரச்னைகள் உள்ளது
  • 1 view
  • Last reply by Tychris

Recently updated to version 105.0.1 and I've started to have problems with Twitch. I'm unable to login and keep getting the message: "Something went wrong. Please try again." so I cleared the cookies/site data. Still unable to login. I know this isn't an error with my account as I can login via Chrome with no issues. Then I tried downgrading to the previous version 104.0.2 and had no issues with Twitch. Most likely, this new version is creating an error with the Twitch site. Hopefully new updates will address this issue - in the meantime, hoping someone has a solution.

Recently updated to version 105.0.1 and I've started to have problems with Twitch. I'm unable to login and keep getting the message: "Something went wrong. Please try again." so I cleared the cookies/site data. Still unable to login. I know this isn't an error with my account as I can login via Chrome with no issues. Then I tried downgrading to the previous version 104.0.2 and had no issues with Twitch. Most likely, this new version is creating an error with the Twitch site. Hopefully new updates will address this issue - in the meantime, hoping someone has a solution.

All Replies (14)

fixed this afternoon for me. Maybe twitch devs made an update.

Still not working for me. I updated to 105.0.2 hoping there would be changes that resolve the issue but unfortunately, still unable to login to Twitch on Firefox. No issues on Chrome still.

clear your cache/data ? Maybe their fix only work for fresh new data/cookies.

You can check for issues with Total Cookie Protection.


You can remove all data stored in Firefox for a specific domain via "Forget About This Site" in the right-click context menu of an history entry ("History -> Show All History" or "View -> Sidebar -> History").

Using "Forget About This Site" will remove all data stored in Firefox for this domain like history and cookies and passwords and exceptions and cache, so be cautious. If you have a password or other data for that domain that you do not want to lose then make sure to backup this data or make a note.

You can't recover from this 'forget' unless you have a backup of involved files.

If you revisit a 'forgotten' website then data for that website will be saved once again.

None of those recommendations worked unfortunately, but thank you for the suggestions.

Can you press F12, go to network tab, then try again to login ? You may see some warnings or errors in the tool. Can you paste them here ?

For me it was an "error 400" for one of the twitch domains. Just to check where is the issue for you.

Yeah I got that error 400 as well for the passport.twitch.tv domain.

Just tried again in private mode, and issue 400 is back :D

But I managed to find a way to login : restart your browser in troubleshoting mode : https://support.mozilla.org/kb/diagnose-firefox-issues-using-troubleshoot-mode

then open a new tab in private mode. For me it works in that way.. I will dig more...

Do you use plugin "CanvasBlocker" ? If yes, can you try to disable it, then start again in private mode if login works ? For me it seems to be the issue... when I disable it, no more error 400...

No, I don't use it. Also, I ran troubleshoot mode which disables themes/extensions, and the problem persisted. So most likely unrelated to extensions/themes.

Tychris மூலமாக திருத்தப்பட்டது

Clear your browser's cache, cookies, and history Simply clear the cache, cookies, and history of your browser before trying to refresh Twitch and check if the network error continues to persist.

This May Work, Peter

That was one of the first things I tried, did not solve the issue.