RTMP_Connect1, TLS_Connect failed: -0x7080 On Facebook Live

zev323232

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

Code:
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

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

pluck

New Member
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

New Member
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

New Member
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.

Code:
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

New Member
[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).

1733218144689.png



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!
 

zev323232

New Member
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

New Member
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.
 

darksurf

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

 
Top