RTMP_Connect1, TLS_Connect failed: -0x7080 On Facebook Live

[zev323232]

Hello! I'm currently having an issue connecting to facebook live. Here is the log:

info: [rtmp stream: 'simple_stream'] Connecting to RTMP URL rtmps://rtmp-api.facebook.com:443/rtmp/...
info: RTMP_Connect1, TLS_Connect failed: -0x7080
info: [rtmp stream: 'simple_stream'] Connection to rtmps://rtmp-api.facebook.com:443/rtmp/ failed: -2

Obs: obs-studio 30.2.3-1
Arch: 6.11.9-arch1-1

 

[pluck]

Same here :

Obs: obs-studio 30.2.3-1
Arch: 6.6.60-1-lts

I will loose my job on this one. I just cannot figure it out.

 

[pluck]

Might a log report be of any help :

12:24:50.341: [rtmp stream: 'simple_stream'] Connecting to RTMP URL rtmps://live-api-s.facebook.com:443/rtmp/...
12:24:50.450: RTMP_Connect1, TLS_Connect failed: -0x7080

12:24:50.451: [rtmp stream: 'simple_stream'] Connection to rtmps://live-api-s.facebook.com:443/rtmp/ failed: -2

12:24:50.451: ==== Streaming Stop ================================================

Same output with :

rtmps://rtmp-api.facebook.com:443/rtmp/

I also deleted :

~/.config/obs-studio

to no avail.

 

[pluck]

Just finished compiling osb-studio-git. Still the same error.
I tried :

openssl s_client -connect rtmp-api.facebook.com:443 -showcerts
openssl s_client -connect rtmp-api.facebook.com:443 -tls1_2
openssl s_client -connect rtmp-api.facebook.com:443 -CApath /etc/ssl/certs/

and all seems ok. (Tried also with FB url : live-api-s.facebook.com:443 with the exact same results).

 

[tackleza]

Hello, I'm facing the same issue.

I'm running OBS 30.2.3 right now, installed via "obs-studio-git." I'm using Manjaro, and I still have no idea why this is not working.
Everything is up-to-date right now.

info: [rtmp stream: 'adv_stream'] Dynamic bitrate disabled. The encoder does not support on-the-fly bitrate reconfiguration.
info: [rtmp stream: 'adv_stream'] Connecting to RTMP URL rtmps://edgetee-upload-bkk.xx.fbcdn.net:443/rtmp/...
info: RTMP_Connect1, TLS_Connect failed: -0x7080
info: [rtmp stream: 'adv_stream'] Connection to rtmps://edgetee-upload-bkk.xx.fbcdn.net:443/rtmp/ failed: -2

Hope someone finds the solution. Is anyone in this forum able to live stream to Facebook? Is it a Facebook server problem, an OBS problem, or maybe my computer?

Thank you

 

[tackleza]

[Sorry, I can't edit the above message, so I have to post a new message here.]

I've tested on the Youtube platform with this preset "Youtube - RTMPS," and it's working. I'm not sure if it is RTMPS or not. But the custom URL, like "rtmps://a.rtmp.youtube.com/live2" or "rtmps://a.rtmp.youtube.com:443/live2," is not working for me (pic below).

The output is:The output is: So I think the problem is on the protocol rtmps://, which is on the project "MbedTLS," not on OBS itself.
Here is another user facing the same problem (https://forum.manjaro.org/t/obs-and-mbedtls-disaster/170668/5).

So maybe we have to wait? or maybe rollback to an older version and compile it by ourselves
I have to go now; I appreciate it if someone can find a solution!

 

[MMLTech]

this may be helpful, however it looks more like a rtmps:// protocol issue in the latest builds https://obscountdown.com/article/117-beginners-guide-to-fix-obs-studio-rtmp-tls-connection-errors

 

[zev323232]

So maybe we have to wait? or maybe rollback to an older version and compile it by ourselves
I have to go now; I appreciate it if someone can find a solution!

I have already tried to compile multiple older version of obs with no luck.

I've tested on the Youtube platform with this preset "Youtube - RTMPS," and it's working. I'm not sure if it is RTMPS or not. But the custom URL, like "rtmps://a.rtmp.youtube.com/live2" or "rtmps://a.rtmp.youtube.com:443/live2," is not working for me (pic below).

Yep this is the same behavior for me.

 

[darksurf]

I'm also having this issue. I've had to avoid upgrading OBS for MONTHS because we cannot seem to figure out the breakage between MbedTLS and OBS. I'm still using OBS 30.1.2 and MbedTLS 3.6.0 because its the only way I can stream to facebook from this production machine. I'd love to use the flatpak version, but sadly the theres no good way to install the required plugins for NDI and multi-stream in the flatpak version.

 

[pluck]

Same with obs-studio 31.0.0-1

 

[darksurf]

I've created a bug to MbedTLS to see if they know whats going on here.

Issues · Mbed-TLS/mbedtls

An open source, portable, easy to use, readable and flexible TLS library, and reference implementation of the PSA Cryptography API. Releases are on a varying cadence, typically around 3 - 6 months ...

github.com

 

[MathMage]

I am too getting the same error. For now the flatpak version seems to work fine

 

[darksurf]

MbedTLS team has found it has something to do with TLS fragmentation. They fixed this in TLS 1.2 some time ago, but now they're working to fix this in TLS1.3 .

 

[darksurf]

TLS Handshake record layer fragmentation not working · Issue #1840 · Mbed-TLS/mbedtls

I have a server setup that sends handshake with ssl->in_hslen set to above 22700-ish, which is above the accepted limit of 16384. Is there any plan to support this (or a workaround without changing...

github.com

if you're interested in the progress of the solution.

 

[tackleza]

That's really good news that the problem is being fixed, and the patch is on the way (TLS 1.3).

 

[sadmath]

A month later and it's still not working :(

 

[nitanspoiler]

Same problem in Manjaro (and arch based distros), Debian, LMDE. Only works the FB streaming in Ubuntu 24.04 (the problem is, i need distroav plugin, and don't work) and Flatpak versión

 

[aiisforever]

Same problem with debian, my analysis thus far. I am stuck as well.
info: [rtmp stream: 'simple_stream'] Connecting to RTMP URL rtmps://rtmp-api.facebook.com:443/rtmp/...
info: [rtmp stream: 'simple_stream'] Binding to IPv4
info: RTMP_Connect1, TLS_Connect failed: -0x7080
info: [rtmp stream: 'simple_stream'] Connection to rtmps://rtmp-api.facebook.com:443/rtmp/ failed: -2

Context Recap​

• Problem: OBS fails with TLS_Connect failed: -0x7080 when streaming to rtmps://rtmp-api.facebook.com:443/rtmp/.
• Progress: You built a new librtmp from source, but ldd shows OBS links to /lib/x86_64-linux-gnu/librtmp.so.1 (old version 2.4+20151223).
• Certificates: Your openssl s_client -connect live-api-s.facebook.com:443 succeeded with Verify return code: 0 (ok), so Kali’s system certificate store trusts Facebook’s certs.

Your note about “Operating System certificates” from past threads aligns with a common TLS issue—OBS/librtmp might not be using the system’s certificate store correctly, or the old librtmp lacks modern TLS support (e.g., TLS 1.3, updated CA bundles).

---

Why Certificates Might Matter​

• Historical Issues: Older threads (e.g., OBS GitHub, Kali forums) over 4-5 years often cite TLS failures due to:
  • Outdated librtmp not supporting newer TLS versions or ciphers.
  • OBS not loading system CA certificates properly on Linux.
• Your Case: Since openssl works but OBS fails, it’s likely librtmp’s TLS handshake (not the system’s) is the bottleneck, possibly due to certificate validation or cipher mismatch.

---

Step-by-Step Fix​

Step 1: Force New librtmp (Redo with Confirmation)​

Your LD_PRELOAD didn’t override the old librtmp. Let’s replace it directly:

1. Backup Old librtmp:
   bash
   

 

[nitanspoiler]

The problem still in the new versión of OBS

 

[darksurf]

The problem still in the new versión of OBS

The issue isn't OBS, the issue is MBedTLS. Many different linux Distros got off of OpenSSL and moved to MBedTLS which worked OK until the recent upgrade to stable 3.6 in 2024 and the enabling of TLS 1.3. Now the Linux distros claim they support TLS 1.3 and the service tries to negotiate a handshake using TLS 1.3, but are fragmenting the handshake and MBedTLS 3.6.2 does NOT support fragmented handshakes for TLS 1.3.

Using the older version of MBedTLS, TLS 1.3 wasn't supported and was falling back to 1.2 and worked fine without issues. Now that it claims support even though it doesn't have full support, it fails the handshake and fails to connect. Its like telling someone you speak fluent english, but they can't get past the greeting stage so the conversation never starts.

TLS Handshake record layer fragmentation not working · Issue #1840 · Mbed-TLS/mbedtls

I have a server setup that sends handshake with ssl->in_hslen set to above 22700-ish, which is above the accepted limit of 16384. Is there any plan to support this (or a workaround without changing...

github.com

They're trying to get this fixed in 3.6.3. I'm frustrated waiting for them to fix this mess.


UPDATE! 3.6.3 is released and includes the fix!!

Release Mbed TLS 3.6.3 · Mbed-TLS/mbedtls

Description This release of Mbed TLS provides the fix for a tls compatibility issue of handling fragmented handshake messages. This release includes fixes for security issues. Mbed TLS 3.6 is a lon...

github.com