OBS Auto Reconnect for 24/7 Streams: Settings and Defaults

Published on | Updated

How OBS Automatically Reconnect works, from its source code: 2 second Retry Delay, 25 Maximum Retries, a 15 minute cap, and how to catch a dropped 24/7 stream.

A streamer in headphones at a desk, with a live timer in his streaming software on one monitor, a stream health dashboard on the other and a server rack behind him

Your 24/7 stream ran for days. Then the OBS status bar said "Disconnected, reconnecting in 2 second(s) (attempt 1)", and when you looked again the channel was offline. Did OBS give up, or did it never try? OBS has an Automatically Reconnect setting, it is on by default, and the source code shows exactly how long it keeps trying. This guide covers what the setting does, what to change for a stream that has to survive long outages, what it does not cover, and how to notice a drop. Everything here was checked against OBS Studio 33.0.1, released on 29 October 2026.

Quick answer: Open Settings > Advanced and find Automatically Reconnect. Enable is ticked by default, Retry Delay is 2 seconds (you can set 1 to 30) and Maximum Retries is 25 (1 to 10000). After a disconnect OBS waits the Retry Delay, makes every next wait about 1.5 times longer up to 15 minutes, and stops the stream when the last attempt fails. With the defaults that is about three hours of trying. For a 24/7 stream, raise Maximum Retries if the stream should come back by itself after a long outage, and watch for drops in the OBS log or through its WebSocket server, because reconnecting only helps a stream that was already running.

Where the Setting Is

Open Settings > Advanced and scroll to the Automatically Reconnect group. It has three controls:

SettingDefaultRangeWhat it does
EnableOnOn or offOff sets the retry count to 0, so a disconnect ends the stream
Retry Delay2 s1 to 30 sThe wait before the first reconnect attempt
Maximum Retries251 to 10000How many attempts OBS makes before it stops the stream

Simple and Advanced output mode use the same three values, and OBS reads them when the stream starts, so a change applies the next time you click Start Streaming. They are saved per profile, in the [Output] section of basic.ini as Reconnect, RetryDelay and MaxRetries. On Linux that file is in ~/.config/obs-studio/basic/profiles/<profile>/; the Flatpak build keeps it under ~/.var/app/com.obsproject.Studio/config/obs-studio/ instead, because Flatpak points XDG_CONFIG_HOME there. If you run OBS on a VPS and mostly work in a terminal, you can set the values in that file while OBS is closed.

What OBS Does After a Disconnect

The logic is in libobs, in obs-output.c:

  1. The connection to the ingest server breaks while you are live. The RTMP output writes Disconnected from and the server address to the log and reports the disconnect to libobs.
  2. libobs logs a line such as Output 'adv_stream': Reconnecting in 2.00 seconds.. (the name is simple_stream in Simple output mode) and waits the Retry Delay before it tries again. The status bar shows "Disconnected, reconnecting in 2 second(s) (attempt 1)".
  3. If that attempt fails, the next wait is the previous one times a factor between 1.5 and 1.55 (1.5 plus a small random amount): roughly 2, 3, 4.5 and 6.75 seconds, and so on.
  4. No wait is longer than 15 minutes. With a 2 second Retry Delay, the waits reach that cap around the 15th to 17th attempt.
  5. When an attempt works, the status bar shows "Reconnection successful". When the number of attempts reaches Maximum Retries, OBS stops the stream.

Added up from those rules, this is how long OBS keeps trying:

Retry DelayMaximum RetriesWaiting time before OBS stops the stream
2 s (default)25 (default)2 h 59 min to 3 h 13 min
30 s25about 4 h 40 min
2 s10000about 104 days, with 15 minutes between tries after roughly the first 30 to 45 minutes

These are waiting times. Every failed attempt adds the time the connection attempt itself takes.

Two things follow for a 24/7 stream. With the defaults, an outage longer than about three hours, such as an ingest problem or a long network fault, ends the stream, and it stays down until someone starts it again. And after a long outage the next attempt can be up to 15 minutes away, so the stream can stay offline for a while after the network is back. The 1.5 factor and the 15 minute cap are fixed in libobs; there is no setting for them.

Settings for a 24/7 Stream

Keep Enable on and Retry Delay at 2 seconds. A short first wait brings the stream back soonest after a brief network blip.

Decide what should happen after a long outage. If the stream should return on its own, raise Maximum Retries. At 10000, OBS keeps trying every 15 minutes for about 104 days. If you would rather know about it and act yourself, keep 25 and make sure an alert reaches you when the stream stops (see the last section).

Check Stream Delay if you use it. Stream Delay, in the same Advanced tab, is off by default and set to 20 seconds when you turn it on. Its option "Preserve cutoff point (increase delay) when reconnecting" is on by default: as the name says, OBS keeps the point where the stream was cut and increases the delay, so viewers fall further behind real time after each reconnect.

Consider dynamic bitrate. Under Settings > Advanced > Network, "Dynamically change bitrate to manage congestion (Beta)" lowers the bitrate when the connection cannot keep up, instead of dropping frames. OBS notes that it works for RTMP only and that the bitrate can take a few minutes to recover after a drop. That matters because, in OBS's own words, dropping too many frames can get you disconnected from the streaming server. OBS's troubleshooting guide suggests it only when you cannot fix the connection itself.

Keep the bitrate realistic. OBS's troubleshooting guide starts at 75% of your upload speed and says to stay within the platform's limit; OBS's built-in Twitch entry, for example, caps video at 6000 Kbps. If disconnects continue, the same guide suggests trying another ingest server and setting IP Family to IPv4 only under Settings > Advanced > Network, and going back to the default of IPv4 and IPv6 if that changes nothing.

What Automatically Reconnect Does Not Cover

A stream that never started. Reconnecting only begins after a running stream disconnects. If the first connection fails because the stream key is wrong or was reset, the ingest server is down, or the VPS network is not up yet when OBS starts with --startstreaming, OBS shows a "Failed to connect" message such as "Could not access the specified channel or stream key" and does not try again.

OBS itself stopping. If OBS crashes or gets killed, nothing reconnects. On the next start after an unclean shutdown, OBS 33 opens an "OBS Studio Crash Detected" window and waits until someone clicks Run in Normal Mode or Run in Safe Mode, so a script that restarts OBS with --startstreaming still needs a person to answer it. Safe Mode disables third-party plugins, scripting and WebSockets, which also turns off the WebSocket checks below.

The end of the retries. After the last attempt the stream stays stopped.

Problems that keep the connection up. A frozen source, silent audio or the wrong scene does not break the connection, so OBS has nothing to reconnect.

How to Notice a Dropped Stream

The OBS log

Each session writes a log file to ~/.config/obs-studio/logs/ (~/.var/app/com.obsproject.Studio/config/obs-studio/logs/ for the Flatpak), the folder that Help > Log Files > Show Log Files opens. On a VPS you can read it from the terminal:

grep -h -E "Disconnected from|Reconnecting in" ~/.config/obs-studio/logs/*.txt | tail -n 20

Each drop starts with a Disconnected from line and every reconnect attempt adds a Reconnecting in line, so you can see how often the connection dropped and how many tries OBS needed to get back.

The WebSocket server

OBS 28 and later include obs-websocket. Turn it on under Tools > WebSocket Server Settings: tick Enable WebSocket server, keep Enable Authentication on and note the Server Password. The default port is 4455.

  • The GetStreamStatus request returns outputActive and outputReconnecting. outputActive stays true while OBS is still retrying, so false means the stream stopped: the retries ran out or someone stopped it.
  • The StreamStateChanged event reports an outputState of OBS_WEBSOCKET_OUTPUT_RECONNECTING when the connection drops and OBS_WEBSOCKET_OUTPUT_RECONNECTED when it is back (obs-websocket 5.1.0 and later).

Keep port 4455 closed in your firewall and reach it through an SSH tunnel. Our guide to protecting your stream key on a VPS explains why the WebSocket port and password need the same care as the key.

Checks from outside OBS

OBS only knows about its own connection. To confirm that the platform actually shows your stream, and to get an alert on Discord or by email, combine the log or WebSocket check with the platform's API and a heartbeat from another machine, as our guide to monitoring a 24/7 live stream sets up step by step.

If It Still Drops

  • Short, frequent drops: lower the bitrate, try another ingest server or IPv4 only, and look in the log for the minutes before each Disconnected from line.
  • The stream stopped after hours of retrying: the outage lasted longer than your Maximum Retries cover. Raise the value, or alert on outputActive turning false.
  • The stream did not come back after a VPS reboot: connect to the desktop and look for the Crash Detected window, and make sure OBS starts streaming only after the network is up, because a failed first connection is not retried. Our cloud OBS guide sets up a remote desktop on a VPS behind an SSH tunnel.

FAQ

Is OBS auto reconnect on by default? Yes. In OBS 33.0.1 every new profile has Enable ticked, a Retry Delay of 2 seconds and 25 Maximum Retries, under Settings > Advanced > Automatically Reconnect.

How long does OBS keep trying to reconnect? With the defaults, 2 h 59 min to 3 h 13 min of waiting, plus the time of each failed attempt. The first wait is the Retry Delay, every next one is about 1.5 times longer, no wait is longer than 15 minutes, and OBS stops the stream when the number of attempts reaches Maximum Retries.

Why did OBS not reconnect when my stream failed to start? Automatically Reconnect only covers a stream that was running and then lost its connection. A failed first connection, for example because of a wrong or reset stream key, ends with an error message and no retry.

Can I make OBS retry faster after a long outage? Not with a setting. Retry Delay only sets the first wait; the growth factor and the 15 minute cap are fixed in libobs. Watching outputReconnecting through the WebSocket server at least tells you when OBS is between attempts.

Do I need a VPS for this? No, the setting works the same on any computer. A VPS means the stream no longer depends on your home connection or on your PC staying on. Our streaming VPS has OBS preinstalled and opens in your browser, so you can change these settings without setting up a remote desktop yourself.

Sources

All opened on 31 October 2026: