OBS "Could Not Connect to Server" - Fix by Platform

OBS "Could Not Connect to Server": Fix by Platform

OBS reports connection failures with a single generic message no matter which platform refused you. That is unhelpful, because the platforms fail for genuinely different reasons. A YouTube connection that will not open usually has a cause that cannot occur on Twitch, and a Kick failure is frequently a URL format issue that Twitch users never encounter.

This guide is the platform layer. If you have not yet run the universal checks — stream key, ingest server, network binding, firewall — do those first: OBS "Failed to Connect to Server": Fix walks that ladder in order and resolves most cases on its own. Come back here when the generic steps come up clean and the platform is still refusing you.

First: The Two Traps That Look Like Platform Problems

Two causes account for a surprising share of "I tried everything" cases, and neither is platform specific.

You are already connected somewhere. Most platforms accept one live session per key. A second OBS instance, a phone app left broadcasting, a restreaming service still holding the connection, or a session the platform has not yet timed out after a crash will all reject the new connection with this error. Close every other broadcasting client, then wait five minutes — platform-side session timeouts are not instant. If OBS crashed during your last stream, that wait is mandatory rather than optional.

You pressed the wrong button. Start Streaming opens a network connection to an ingest server. Start Recording writes a file to your disk and involves no server at all. A large share of people hitting this error are recording a tutorial and clicked the upper button. If no server should be involved in what you are doing, the button one row down is the one you wanted.

Twitch

Enhanced Broadcasting. If you have opted into Twitch's Enhanced Broadcasting beta, OBS negotiates a different connection than standard RTMP, and it requires a current OBS version and an authorised account rather than a pasted key. If you enrolled and then reinstalled OBS, or pasted a manual key over an authorised connection, the negotiation fails. Open Settings > Stream, click Disconnect if an account is connected, then Connect Account again and re-authorise.

The key rotates more than you expect. Twitch invalidates stream keys on password change, on enabling two-factor authentication, and during security rotations you are not notified about. Reset it in the Creator Dashboard under Settings > Stream, and paste rather than retype.

Ingest servers are regional and do go down. Twitch publishes a live ingest status page. If the nearest server is degraded, Auto keeps aiming at it. Pick a named server two or three cities away rather than the closest one.

One stream per channel. Twitch will not accept a second concurrent connection on the same key, and returns this error rather than saying so.

YouTube

YouTube is the platform where the error most often means something other than a bad key.

The stream has to exist before OBS can connect. Unlike Twitch, YouTube will not accept an incoming connection to a stream you have not created. Open YouTube Studio, click Go Live, and get to the "waiting for stream" screen before you press Start Streaming in OBS. If you skip this, the key is valid and the connection is still refused.

Reusable versus single-use keys. YouTube offers both. A single-use key is dead after its broadcast ends, and reusing one from last week's stream produces this error with no explanation. In YouTube Studio's stream settings, create a reusable stream key if you stream regularly, and use that one every time.

Live streaming may not be enabled yet. First-time live streaming on a channel requires verification and then a 24-hour activation wait. During that window the key exists, looks correct, and will not connect. There is no way to shorten it.

Channel-level restrictions. An active copyright strike or a live-streaming restriction disables ingest entirely. YouTube Studio shows this under the live streaming section; OBS just reports a connection failure.

Kick

The URL and key are split, and the split is not obvious. Kick gives you a stream URL that typically ends in /app and a separate stream key. In OBS, set Service to Custom, put the URL — including the /app — in Server, and the key on its own in Stream Key. Appending the key to the URL, or dropping the /app segment, both produce this error.

Regional ingest matters more here. Kick's ingest network is smaller than Twitch's. If the endpoint you were given is geographically distant, connections that establish will also drop. Check whether Kick publishes a nearer ingest for your region.

Custom RTMP, and Anything Self-Hosted

If Service is set to Custom, the two most common failures are formatting rather than credentials.

The URL and key belong in separate fields. The platform gives you rtmp://server.example.com/live and a key like abc123. Pasting rtmp://server.example.com/live/abc123 into Server and leaving Stream Key empty fails. So does the reverse. Split them.

Trailing slashes and application paths. rtmp://server.example.com/live and rtmp://server.example.com/live/ are not always treated the same by the receiving server. Use exactly what the platform documented, with nothing added.

Use RTMPS where it is offered. Standard RTMP runs on port 1935, which corporate networks, university networks, hotel Wi-Fi and some residential ISPs block outright. RTMPS runs on port 443 — the same port as ordinary web traffic — and is almost never blocked. If the platform publishes an rtmps:// address, prefer it. If a stream connects on RTMPS but not RTMP, the port was blocked upstream and no local setting would have fixed it.

Multistream Relays: Restream, Castr, and Similar

Multistreaming services introduce a second set of credentials, and mixing them up is the standard failure.

OBS connects to the relay, not to the destination platforms. So OBS needs the relay's ingest URL and the relay's key. Your Twitch and YouTube keys go into the relay's dashboard, not into OBS. Pasting a Twitch key into OBS while pointing at a Restream server is a connection the relay will refuse.

If the relay connects but a destination does not go live, the failure has moved past OBS entirely and belongs in the relay's dashboard.

Platform Router

If None of This Applies to You

It is worth naming the outcome this error most often has. Someone opens OBS to record a product demo, a walkthrough, or a course lesson, hits the button at the top of the controls dock, and spends the next hour learning about RTMP ingest servers for a video that was only ever going to be a file on their own disk.

If that describes you, the whole streaming stack is machinery you are maintaining for no reason. Cubix Capture records locally on Windows and Mac — no server, no key, no firewall rule, no ingest region — and applies the zoom and cursor smoothing during capture, so the file is finished when you stop rather than needing an edit pass. The free Starter plan runs without an account.

Keep Reading

• OBS "Failed to Connect to Server": Fix for the universal diagnostic ladder underneath this page.
• OBS Dropping Frames: Why It Happens and How to Stop It if the connection opens and then degrades.
• OBS Encoding Overloaded Error: How to Fix if you go live but the stream stutters.
• OBS "Starting the Output Failed": Fix if the failure is the encoder rather than the network.