Open Settings > Stream and confirm the selected service and account or stream key. If the service rejects the connection, refresh the account or key in that service's own dashboard; if the details are accepted but OBS still cannot connect, try another server offered in the same Stream panel. Do not change scenes or encoder settings for an authentication error.
Select Start Streaming once and copy or photograph the complete message. Note the service selected in OBS and whether you connected an account or pasted a stream key. Never include the key in a screenshot, log post, or support message.
2
Check the service and account
Open the streaming service in a browser, confirm that you are signed into the intended channel, and check its status page for a live-streaming incident. In OBS, select Settings > Stream and make sure Service names that same provider. If the service is unavailable, keep the OBS settings unchanged and wait for the owner to restore it.
3
Refresh the account or stream key
If OBS uses a connected account, reconnect only that account and verify the channel name. If it uses a stream key, copy a current key from the service's own live dashboard and replace the value in Settings > Stream. For a Custom service, copy both the exact server URL and key from its owner; do not guess a URL or use a key from another channel.
4
Try another listed server
In Settings > Stream, open Server and choose another server offered for the same service, then select Apply > OK. Leave Settings > Advanced > Network > Bind to IP on Default. A successful connection here points to the previous ingest route, not to a scene or encoder problem.
5
Make a private connection test
Set the destination stream to private or unlisted in the service dashboard, select Start Streaming, and wait for the service preview or stream-health panel to receive video. Success means OBS connects and the intended channel receives the test; stop the stream before changing anything else.
6
Use the error session's OBS log
If the same error returns, leave OBS open and choose Help > Log Files > Upload Current Log File > Copy URL. The current session must contain the failed attempt. Share that URL with OBS or the streaming service's support team, together with the time, service, and server, but never the stream key.
7
Separate disconnects from connection refusal
If OBS starts streaming but later disconnects or reports dropped frames, the account and key were accepted. Follow OBS's network guide instead: test another server, use wired Ethernet when possible, and lower Video Bitrate only when the stable upload cannot sustain it. Do not repeat account resets for a stream that already started.
If it does not work
If the service says the key is invalid, generate or copy a current key in that service's official dashboard and update OBS; do not paste a key from email, chat, or a third-party site.
If one service fails but a permitted private test on another service connects, send the failed service the OBS log URL, timestamp, and selected server. The OBS installation and local upload path are not the first suspects.
If every service and server fails, disconnect a VPN you intentionally enabled, try wired Ethernet, and contact the network administrator or ISP with the OBS log and timestamps. Keep firewall and security protection enabled while diagnosing.
If OBS connects but the preview stutters or frames drop, use the separate dropped-frames branch. Encoder, bitrate, and upload stability affect an active stream, but they do not repair a rejected account or stream key.
ⓘ Sources and verification
Checked against official documentation on . Scope: OBS Studio desktop.
Source-checked against current OBS Project and YouTube owner documentation. The page is deliberately image-free because the Stream panel changes with the selected service and account-link method, while a screenshot could expose a stream key; the exact controls and success result are named in the text.
