OBS "Failed to Connect to Server" - Fix

OBS "Failed to Connect to Server": Fix

You press Start Streaming and OBS returns a dialog reading Failed to connect to server. Nothing goes live, and the error says nothing about which part of the chain broke.

It is worth knowing what OBS is actually reporting. OBS encodes locally and then opens a network connection to your platform's ingest server to push that data. This error means the connection was refused, dropped, or never established. It says nothing about your scenes, your sources, your encoder, or your graphics card, which is why changing video settings never fixes it.

There are four things that can break that connection: your credentials, the server you are aimed at, your local network routing, and something between you and the internet blocking the traffic. Work through them in that order, because the first accounts for the clear majority of cases and takes two minutes to rule out.

The Thirty-Second Check First

Before changing any settings, confirm the platform itself is up. Open your creator dashboard in a browser. If the dashboard is loading and reporting no incoming stream, the problem is on your side and the steps below apply. If the platform's own status page is reporting an ingest incident, no amount of configuration will help and you are waiting it out.

Also confirm you are not already live somewhere. Some platforms refuse a second concurrent connection on the same key, and an OBS instance you forgot to close, or a session the platform has not yet timed out, will reject the new one with this exact error.

Step 1: Reset Your Stream Key

Stream keys are invalidated more often than people realise. Changing your account password, enabling two-factor authentication, a platform security rotation, or simply having copied the key with a trailing space are all enough to break it.

1. Open your streaming platform's creator dashboard.
2. Find the stream key setting and click Reset.
3. Copy the new key.
4. In OBS, go to Settings > Stream.
5. Confirm the Service dropdown matches your platform, paste the key into Stream Key, and click Apply.

Paste rather than type, and check there is no whitespace at either end of the field. A single trailing space produces this error and is invisible in the input box.

Better still, use the Connect Account button instead of a raw key wherever the platform supports it. OAuth tokens refresh on their own, which removes this failure mode permanently.

Step 2: Stop Using the "Auto" Server

The Server dropdown defaults to Auto, which asks the platform to pick the lowest-latency ingest node for your location. When that node is under maintenance or congested, Auto keeps aiming at it and keeps failing.

1. Go to Settings > Stream.
2. Open the Server dropdown.
3. Pick a named regional server instead of Auto. Choose one geographically near you, but not necessarily the nearest, since the nearest is the one Auto was already failing on.
4. Click Apply and try again.

If it connects immediately on a manually chosen server, your regional node was the problem and you can switch back to Auto in a day or two.

Step 3: Custom RTMP and the URL/Key Split

If your Service is set to Custom rather than a named platform, there is a specific mistake worth checking before anything else.

The platform gives you two values: a server URL beginning rtmp:// or rtmps://, and a separate stream key. These go in two different fields. Pasting the full URL with the key appended into the Server box, and leaving Stream Key empty, produces exactly this error. So does the reverse.

Split them correctly, and make sure the server URL has no trailing slash beyond what the platform provided.

Step 4: Fix Network Routing

If your machine has more than one active network path, a Wi-Fi adapter enabled while Ethernet is plugged in, a VPN, or a virtual adapter installed by a container or VM tool, OBS can bind its outbound connection to the wrong one.

1. Go to Settings > Advanced.
2. Scroll to the Network section.
3. Set Bind to IP to Default unless you have a specific reason to pin it. A pinned IP that changed after a reboot or DHCP renewal breaks the connection with this error.
4. Tick Enable network optimizations.
5. Tick Dynamically change bitrate to manage congestion, which stops OBS dropping the connection outright when your upstream dips.

If a VPN is running, disconnect it and retry. Many VPN providers block or throttle RTMP traffic, and some route it through exit nodes the platform rejects.

Step 5: Let OBS Through the Firewall

Security software treats outbound RTMP on port 1935 as an unrecognised request and blocks it silently. This is a very common cause of the error appearing suddenly after a system update, with no configuration change on your part.

On Windows:

1. Press the Windows key, type Allow an app through Windows Firewall, and press Enter.
2. Click Change settings, which requires administrator rights.
3. Find OBS Studio in the list and tick both Private and Public.
4. If it is not listed, click Allow another app, browse to C:\Program Files\obs-studio\bin\64bit\obs64.exe, add it, and tick both boxes.
5. Click OK.

On macOS:

1. Open System Settings > Network > Firewall > Options.
2. Confirm OBS is present and set to Allow incoming connections.
3. If the firewall is off entirely, the block is coming from third-party security software instead.

Third-party antivirus suites maintain their own firewall independent of the operating system's. If you run one, whitelist obs64.exe there as well, since the built-in settings will look correct while the traffic is still being dropped.

Step 6: When Port 1935 Is Blocked Upstream

Corporate networks, university networks, hotel Wi-Fi, and some residential ISPs block port 1935 outright. Nothing you configure locally will change that.

The workaround is to use RTMPS, which runs over port 443, the same port as normal web traffic, and is therefore almost never blocked. Most major platforms publish an rtmps:// ingest address alongside the standard one. Set Service to Custom, enter the RTMPS server URL, and paste your key.

If that connects when the standard address does not, the network was blocking the port and RTMPS is your permanent answer on that connection.

Symptom Router

If You Are Not Actually Streaming

A large share of people who hit this error are not broadcasting live at all. They are recording a tutorial or a product walkthrough, opened OBS, and clicked Start Streaming instead of Start Recording. If that is you, the button one row down does what you wanted and no server is involved.

And if recording is all you ever do, an RTMP stack is a lot of machinery to maintain for a file that never leaves your disk. Cubix Capture records locally with no server, no key, and no firewall rule to maintain, on Windows and Mac, with a free Starter plan and no account required.

Keep Reading

• OBS Encoding Overloaded Error: How to Fix if the stream connects but stutters once it is live.
• OBS Dropping Frames: Why It Happens and How to Stop It for network drops during an established stream.
• OBS Keeps Crashing: How to Fix It if OBS dies rather than reporting an error.
• OBS Best Settings for Screen Recording for a configuration baseline.