If your encoder is failing to connect to KICK, the issue usually comes down to one of a few things: an incorrect stream key, settings that do not match KICK's requirements, or something on your computer blocking the connection.
This guide walks you through each cause, starting with the most common ones.
Check your stream key first
The most common reason an encoder fails to connect is a missing or incorrect stream key.
To find or reset your stream key:
Log in to your KICK account
Visit your Streamer Dashboard
Click Channel > Stream URL and Key
Copy your stream key, or click Reset to generate a new one
If you have recently reset your stream key, you must update it in your encoder before you can go live again. KICK does not save your old key.
💡 Never share your stream key with anyone. Anyone with your stream key can broadcast directly to your channel.
Confirm your encoder settings match KICK's requirements
KICK has specific requirements your encoder must meet. If any of these are wrong, your stream will fail to connect or be rejected after starting.
Setting | Requirement |
Encoder | x264 or H.264 only |
Rate control | CBR (Constant Bitrate) only |
Maximum bitrate | 8,000 kbps |
Maximum resolution | 1920x1080 |
Maximum framerate | 60 fps |
Audio | Stereo, 48kHz maximum |
KICK does not currently support H.265 encoding, and Variable Bitrate (VBR) is not supported. If you are streaming from a Mac, set your encoder to x264 to enable CBR.
Why does KICK require CBR?
CBR keeps your stream's data rate steady. Variable bitrate changes based on what is happening on screen, which can cause sudden spikes that overwhelm KICK's servers and create a poor experience for your Viewers. CBR is the standard for livestreaming on most platforms.
Update OBS or Streamlabs to the latest version
Older versions of streaming software can stop working with KICK as we update our infrastructure. Make sure you are running the latest version:
OBS Studio: obsproject.com
Streamlabs Desktop: streamlabs.com
After updating, restart the application before trying to stream again.
Check your firewall and antivirus
Firewalls and antivirus software can sometimes block your encoder from connecting to KICK's servers. To test if this is the issue:
Temporarily disable your antivirus and try streaming again
If the stream connects, your antivirus is the cause. Add your encoder to your antivirus's allowed list, then re-enable protection
Check that your firewall is not blocking outbound traffic from your encoder
If you are on a corporate or school network, the network may be blocking the streaming ports entirely. You will need to use a different network.
Streaming from LiveU Studio?
To connect to KICK from LiveU Studio, add :443/app to the end of your stream URL.
Your final stream URL should look like this:
✅ rtmps://fa723fc1b171.global-contribute.live-video.net:443/app
Try Streamlabs Desktop's KICK integration
If OBS continues to give you trouble, Streamlabs Desktop has a built-in KICK integration that handles the connection for you:
Open Streamlabs Desktop
Go to Settings > Stream
Click Connect next to KICK
Log in through your browser to authorise permissions
Return to Streamlabs and click Go Live
💡 You will need to set your stream title manually on KICK after going live. Streamlabs is working to streamline this in the future.
Still having issues?
If your encoder still will not connect after working through these steps, contact our 24/7 Support Team at [email protected]. Please include:
Your KICK Streamer username
The encoder you are using and its version
The exact error message you are seeing (a screenshot helps)
Your operating system
Related articles
How to Stream on KICK.com
How to create a KICK Chat Dock in OBS
Why is my stream lagging or buffering on KICK?