
You are live on Kick and the OBS status bar keeps switching between "Disconnected, reconnecting in 2 second(s) (attempt 1)" and "Reconnection successful". Is it your internet, your settings or Kick? Below is what each message means, from the source code of OBS Studio 33.0.1 (the current release, out since 29 October 2026) and Kick's help center, and the fix for each.
Quick answer: OBS keeps disconnecting and reconnecting when its connection to Kick's server breaks while you are live. The usual causes: an upload or Wi-Fi connection that cannot carry your bitrate, settings outside Kick's limits (H.264 and CBR only, at most 8,000 kbps, 1920x1080, 60 fps, 48 kHz stereo audio), or a firewall, antivirus or school or office network blocking the connection. Check Session Health in your Creator Dashboard first: Unstable means Kick is not getting enough data, Misconfigured means a setting is wrong. Then search the OBS log (Help > Log Files) for Disconnected from and failed:. Lower the bitrate 1,000 kbps at a time, use a cable, and keep your upload at least twice your bitrate.
Why OBS Keeps Disconnecting and Reconnecting
The disconnect means OBS could not get its data to the server, or the connection was closed. The reconnect is Automatically Reconnect, on by default under Settings > Advanced, retrying with longer and longer waits, as our guide to OBS auto reconnect explains. That part is OBS doing its job; you need to find why the connection breaks.
Two things never start a reconnect in OBS 33.0.1: an encoder error ("An encoder error occurred while streaming.") and a failed first connection ("Failed to connect"). So a countdown means a running stream lost its connection.
Step 1: Check Kick's Side First
Kick's own lag guide starts with the KICK System Status page: if it reports an outage, you wait. If not, the cause is most likely on your end. Then, while live, watch the Session Health badge in the Session section of your Creator Dashboard:
| Session Health | What Kick says it means | What to check |
|---|---|---|
| Healthy | Online and running correctly | Nothing on Kick's side |
| Unstable | Unstable or not sending enough data; the stream is at risk of stopping | Upload, Wi-Fi, bitrate |
| Misconfigured | Live, but one or more encoder settings are not set correctly | Codec, rate control, resolution, frame rate, audio |
| Error | Stopped due to a technical problem | status.kick.com, then the OBS log |
| Offline | Not live | The OBS status bar |
Unstable during a reconnect loop points at the network, Misconfigured at your settings.
Step 2: Find the Right Lines in the OBS Log
Help > Log Files > View Current Log opens the log; Show Log Files opens the folder for searching in a text editor. A drop followed by a failed retry looks like this (timestamps left out, values in angle brackets differ per setup):
[rtmp stream: 'adv_stream'] Connecting to RTMP URL rtmps://<kick server>:443/app...
[rtmp stream: 'adv_stream'] Connection to rtmps://<kick server>:443/app (<ip>) successful
[rtmp stream: 'adv_stream'] Disconnected from rtmps://<kick server>:443/app
Output 'adv_stream': Reconnecting in 2.00 seconds..
[rtmp stream: 'adv_stream'] Connecting to RTMP URL rtmps://<kick server>:443/app...
Output 'adv_stream': Reconnecting in <3.00 to 3.10> seconds..
[rtmp stream: 'adv_stream'] Connection to rtmps://<kick server>:443/app failed: -2
OBS writes the next "Reconnecting in" line just before the line that says why the attempt failed. In Simple output mode the name is simple_stream. On Windows, an Interface: line after each Connecting line names the adapter OBS uses to reach the server; its mbps figures are link speed, not internet speed. The number after failed: is OBS's result code.
What Each Message Means: The Decision Table
| What you see | Where | What it means | What to do |
|---|---|---|---|
| "Disconnected, reconnecting in 2 second(s) (attempt 1)" | Status bar | The connection broke while live | The log before the drop, Dropped Frames (Network) |
| "Attempting to reconnect... (attempt 3)" | Status bar | OBS is making its third try; tries 1 and 2 failed | The failed: code in the log |
Disconnected from <url> | Log | Sending failed and OBS dropped the connection | Bitrate, Wi-Fi, upload |
failed: -1, "Invalid Path or Connection URL..." | Log, dialog | OBS cannot use the server URL | Paste Kick's Server URL again, with :443/app |
failed: -2, "Failed to connect to server" | Log, dialog | No connection to the server at all | The dialog's second line (next table) |
failed: -3, "Could not access the specified channel or stream key..." | Log, dialog | The server took the connection but refused the stream | Paste the current key from your dashboard |
| "Disconnected from server." | Dialog | The stream ended: reconnect is off or all retries are used | The dialog's second line |
Encoder error, disconnecting | Log | The encoder failed, not the network; no retry | Test with x264, lower the preset or resolution |
Interface has non-zero error counters | Log, Windows | The adapter counted errors or discarded packets | Cable, router, network driver |
During a loop, failed attempts only show as failed: lines. Dialogs appear when the first connection fails or OBS gives up; their second line names the network error:
| Second line | What it points to | Check |
|---|---|---|
| "The connection timed out..." | No answer from the server | Server URL, firewall, outbound TCP 443 |
| "The connection was blocked..." | Firewall or antivirus | Pause the antivirus to test, then allow OBS |
| "The connection was reset by the peer..." or "...aborted..." | In OBS's words, internet problems between you and the service | Cable, router restart, lower bitrate |
| "Hostname not found..." | DNS, or a typo in the URL | Copy the URL again |
| "Hostname found, but no data..." or "Error reaching host..." | IP Family or Bind to IP | Set both back to their defaults |
| "The RTMP server sent an invalid SSL certificate." | The certificate could not be verified | Exact dashboard URL; security software off; another network |
Kick's Checks, in Order
- Stream key. Kick names a missing or wrong key as the most common reason. It is under Channel > Stream URL and Key in your Streamer Dashboard; after a Reset, paste the new key into OBS (Settings > Stream), because "KICK does not save your old key".
- Settings inside Kick's limits. x264 or H.264 only (no H.265), CBR only (no VBR), at most 8,000 kbps, 1920x1080, 60 fps and 48 kHz stereo; on a Mac, pick x264 to get CBR. Kick says a wrong setting means the stream will "fail to connect or be rejected after starting". Kick's server address ends in
global-contribute.live-video.net, the ingest domain in Amazon IVS's documentation; Kick does not say it uses IVS, but IVS's guide says a stream over the allowed resolution or bitrate "probably will disconnect immediately". Our Kick bitrate guide has the settings per resolution. - OBS version. Older versions "can stop working with KICK as we update our infrastructure", Kick warns. Install the latest release and restart OBS.
- Firewall, antivirus and network. Turn the antivirus off for a test; if the stream connects, add OBS to its allowed list. Kick's URL is RTMPS on port 443, so outbound TCP 443 must be open. School and office networks may block streaming entirely; Kick's advice is another network.
Also set a title and category under Edit Stream Info: Kick says a stream may not start correctly without them.
Network or Encoder? Read the Stats Dock
Open Docks > Stats (or View > Stats for a separate window):
- Dropped Frames (Network): the connection could not keep up. OBS's guide: "If you drop too many frames, you may be disconnected from the streaming server."
- Skipped frames due to encoding lag: the encoder cannot keep up. Kick suggests a lighter preset, such as Superfast for x264, when your CPU sits above 90%.
- Frames missed due to rendering lag: your scenes render too slowly.
The drop rule is in rtmp-stream.c: when the video waiting in the send queue covers more than 700 ms, OBS drops the least important frames, past 900 ms the P-frames too; audio and keyframes are never dropped. At 60 fps, 700 ms is 42 frames (0.7 x 60). The network icon in the status bar measures that queue, averaged over 4 seconds: excellent when empty, good up to a third of 700 ms (about 233 ms), mediocre up to two thirds (about 467 ms), bad beyond.
Settings That Help, and Two That Do Nothing on Kick
Lower the bitrate 1,000 kbps at a time, as Kick advises. Kick wants an upload of at least twice your bitrate; OBS's guide suggests starting at 75% of your upload. Use the stricter rule: with a 10 Mbps upload, 10 / 2 = 5 Mbps, so 5,000 kbps (the 75% rule would allow 7,500). If Dropped Frames (Network) still climbs, try 4,000. Our OBS bandwidth test guide shows how to test before going live.
Use a cable. Kick calls wired ethernet "almost always more stable than Wi-Fi, especially during peak hours". On Windows the Interface: log line shows 802.11 when OBS goes out over Wi-Fi.
Dynamic bitrate, as a safety net. Settings > Advanced > Network has "Dynamically change bitrate to manage congestion (Beta)", off by default. Instead of dropping frames, OBS lowers the bitrate once 200 ms of video is queued, then raises it a tenth of your set bitrate at a time, at least 4 seconds apart. OBS's tooltip warns that it can add delay and take up to a few minutes to restore, and that it works for RTMP only (Kick's RTMPS uses the same output). Stream Delay switches it off, and it does not fix the cause.
Enable network optimizations and Enable TCP pacing do nothing on Kick. OBS's guide suggests these Windows-only boxes, but OBS 33.0.1 turns network optimizations off for any rtmps:// URL, such as Kick's, and logs "Disabling network optimizations, not compatible with RTMPS". TCP pacing only works with network optimizations on, which is why its box stays greyed out until that one is ticked.
IP Family and Bind to IP. OBS's guide suggests IPv4 Only as a test, and going back to "IPv4 and IPv6 (Default)" if nothing changes. Keep Bind to IP on Default.
When the Drops Follow Your Home Connection
If the log shows plain Disconnected from lines, Session Health says Unstable, and a lower bitrate and a cable did not help, the weak link is between your network and Kick. A VPS changes where the stream leaves from but adds no upload: your PC sending to a server first still needs that bitrate. It helps for a stream that does not need your PC (a 24/7 or prerecorded stream run by OBS on the server), and as a test: run the same scenes from a server and compare logs. Our streaming VPS has OBS preinstalled and opens in your browser, so the settings above are in the same place. To relay from home anyway, read our RTMP vs SRT comparison; for an unattended stream, add stream monitoring.
FAQ
Why does OBS keep disconnecting and reconnecting on Kick?
The connection to Kick's server breaks while you are live, and Automatically Reconnect brings it back. Usually your upload or Wi-Fi cannot carry the bitrate, a setting is outside Kick's limits, or something blocks the connection.
Is it my internet or Kick?
Check status.kick.com, then Session Health: Unstable means Kick is not receiving enough data from you, and climbing Dropped Frames (Network) points at your connection. OBS's guide adds a test: stream to another service; if the drops follow, it is not Kick.
Why does OBS disconnect right after I go live on Kick?
Usually a setting outside Kick's limits, such as VBR, H.265, over 8,000 kbps or over 1080p60. "Could not access the specified channel or stream key" means the key: paste the current one, especially after a reset.
Does OBS reconnect by itself?
Yes. With the defaults (2 second Retry Delay, 25 Maximum Retries, no wait over 15 minutes) it keeps trying for about three hours. It does not retry after an encoder error or a failed first connection.
Why does OBS stop reconnecting and show "Disconnected from server."?
Automatically Reconnect is off, or OBS used all its retries. The line under it, when there is one, names the last network error (see the second table).
Why does the same thing happen on Twitch?
The messages and log lines come from OBS, so the tables apply to Twitch too. The Twitch entry that ships with OBS 33.0.1 does differ: 13 servers to choose from and a 6,000 kbps video cap, where Kick uses one server URL and allows 8,000.
Sources
All opened on 4 November 2026:
- Kick Help Center: OBS or Streamlabs not connecting to KICK, Why is my stream lagging or buffering on KICK?, Understanding your KICK Creator Dashboard, How to stream on KICK.com, KICK System Status
- Amazon IVS: Streaming configuration, Low-Latency Streaming User Guide
- OBS Studio: 33.0.1 release, Stream Connection Troubleshooting
- OBS Studio 33.0.1 source: rtmp-stream.c, obs-outputs en-US.ini, frontend en-US.ini, obs-output.c, obs-defs.h, OBSBasic_Streaming.cpp, OBSBasicStatusBar.cpp, OBSBasic.cpp, OBSBasicSettings.cpp, OBSBasicSettings.ui, OBSBasic.ui, services.json