Read the detail underneath Failed to authenticate with Twitch before changing OBS settings. Reconnect the account if it reports an invalid refresh token. If the login window stays blank or the token request times out, check sign-in in your browser and keep the exact error. A stream key gives video a separate route while the account link stays broken.
| What you see | Where it stops | Go to |
|---|---|---|
| Invalid refresh token, possibly with HTTP 400 | Renewing the account authorization | Reconnect the account |
| A white or blank sign-in window | The embedded login page | Check the stalled login |
| Failed to get token from remote, followed by a timeout or resolver message | The token request | Keep the exact error |
| Could not query stream key, with a two-factor authentication prompt | Retrieving the account’s stream key | Follow the specific prompt |
| Video works with a key, but linked Twitch panels don’t load | The account integration is still unresolved | Understand the key route |
| A key also produces a cannot-connect error, or the startup dialog prevents reaching Settings | The fallback hasn’t fixed it | Stop and record the details |
Account authorization and video delivery are different paths. OBS’s Twitch integration obtains account information before loading its linked panels; Twitch’s video ingest accepts a broadcast using a stream authorization key. Working video doesn’t prove the account link is repaired.
Before disconnecting anything, check Twitch status. Look at Login and Video (Broadcasting) separately. If a relevant incident is active, follow its updates before repeating account changes. An operational status page can still miss a regional fault.
The control names below follow the English interface of OBS 33.0.1, the current release on the OBS download page. For a first-time setup, follow how to connect Twitch to OBS; the steps here start from a connection that has failed.
Refresh a rejected account authorization
I’d reconnect for an invalid refresh token because the account needs fresh authorization before OBS can retrieve its Twitch information. Twitch’s refresh-token guide says these tokens can become invalid after a password change or after you disconnect an app, and that an app should ask for consent again when refresh fails. An HTTP 400 code on its own doesn’t identify the cause; keep the error description beside it.
Have access to your Twitch sign-in and any account verification challenge before you disconnect. Stop any active output first. Disconnect Account applies immediately, so don’t use it repeatedly while you can’t finish the sign-in window.
- Open Settings > Stream and check that the service is Twitch.
- If the account is connected, choose Disconnect Account and confirm the immediate change. If you already see the account-connect choice, skip this step.
- Choose Connect Account (recommended). Sign in to the intended Twitch account and complete the verification Twitch requests.
- Finish the authorization, then apply the settings. Look for the linked Twitch panels to load without the same authentication error.
OBS 33 has no clear-browser-data control in Settings; Disconnect Account and Connect Account clear Twitch’s cookies for you, so expect to sign in again.
If OBS instead shows Could not query stream key and asks you to check two-factor authentication, follow that prompt in your Twitch security settings. It’s a separate warning from the generic authentication error, so don’t read missing two-factor authentication into every authentication error or every HTTP 403.
The login window is blank, or the token request times out
Read the complete message after Failed to get token from remote. A timeout reports a request that didn’t finish; it isn’t proof that your password is wrong. OBS reports a request that never got an answer differently from an error the sign-in service sent back, so keep the full line when you ask for help.
If the window stays blank, stop the disconnect-and-reconnect loop. Check whether you can complete Twitch sign-in in your normal browser before trying to authorize OBS again. A browser login confirms account access; it doesn’t prove the embedded OBS login or its token request worked.
The fault can also sit between OBS and Twitch. In January 2026, OBS developer R1CH attributed one authentication-timeout incident to regional network peering and said the authentication process had been moved back to OBS’s own server. Use today’s exact error and the status page to choose your next check.
A white window isn’t a reason to delete OBS browser folders or the whole profile: that isn’t a documented fix, and it can sign you out of other docks. The relink above already clears the Twitch cookies.
If the account-connect option is missing on Linux, check the display platform before treating it as a broken Twitch login. OBS 33 doesn’t register the Twitch account login when it runs natively on Wayland, so use the stream key there.
If the startup error never lets you reach Settings, leave your settings folder as it is and ask for help with the exact error, OBS version and operating system. From the main window, choose Help > Log Files > Upload Current Log File, confirm Upload, then use Copy Log URL and post that link in the support section for your system on the OBS forum. Say whether normal Twitch sign-in works and whether the key route connects, if you can reach it. Don’t post a stream key, token or unredacted account details. If the key also fails, it’s a connection problem, not a login one; work through it from OBS troubleshooting.
Keep the Twitch service and use a stream key
To send video while the account link stays broken, open Settings > Stream, keep the service on Twitch, choose Use Stream Key, and use Get Stream Key to open Twitch’s dashboard and copy the key into the local field. The key restores the broadcast, not the linked Chat or Stream Information panels. Resetting the key doesn’t renew an invalid account token either: the key authorizes video, while the token serves the account integration.
Leave bitrate and encoder choices alone while you isolate this authentication error. Once the video path connects, choose the bitrate and encoder for the broadcast you intend to send.
Confirm the recovered path without live viewing
Before going public, run the same Twitch bandwidth test from the connection guide, then judge the video path by Twitch Inspector and the account link by the panels. If Inspector receives nothing, the fault is on the video path, so keep that exact connection error for the next check.
