search

arut / nginx-rtmp-module

NGINX-based Media Streaming Server
http://nginx-rtmp.blogspot.com
BSD 2-Clause "Simplified" License
13.38k stars 3.51k forks source link

RTMPS support for Facebook Live API's Upcoming Requirement #1397

Closed JosueAChavez closed 5 years ago

JosueAChavez commented 5 years ago

Facebook is planning to deprecate RTMP on May 1st.

Using the SSL option for my RTMP connection changes the Server URL from rtmp://live-api-s.facebook.com:80/rtmp/ to rtmps://live-api-s.facebook.com:443/rtmp/.

When I insert that URL paired with my streaming key in my nginx.conf file, I'm returned with an invalid port message that looks like

nginx: [emerg] invalid port in url "rtmps://live-api-s.facebook.com:443/rtmp/some_secret_key" in C:\nginx 1.7.11.3 Gryphon/conf/nginx.conf:187

I suspect that the port rtmps is unknown.

Are there any workarounds to use this module with RTMPS? This module is very efficient compared to alternatives solutions I found (ffmpeg).

I'm using nginx 1.7.11.3 Gryphon on Windows 10.

ForrestScott commented 4 years ago

We just restart the stream from within OBS.

SteveMitto commented 4 years ago

How can i fix this error

LOG4[ui]: Service [fb-live] needs authentication to prevent MITM attacks

vnfreezone commented 4 years ago

How can i fix this error

LOG4[ui]: Service [fb-live] needs authentication to prevent MITM attacks

Having the same error :(

ChristofferSthlm commented 3 years ago

I'm getting two issues when trying to set this up and work:

1) My current stunnel.conf looks like this: ;setuid = stunnel4 ;setgid = stunnel4 pid=/tmp/stunnel.pid output = /usr/local/var/log/stunnel4/stunnel.log include = /usr/local/etc/stunnel/conf.d

If I activate setuid and setgid, I'm getting error messages like this: /usr/local/etc/stunnel/stunnel.conf:1: "setuid = stunnel4": Illegal UID

2) The connection with facebook does not work. I'm getting this error message: _Error resolving "live-api-s.facebook.com": Neither nodename nor servname known (EAINONAME)

I'm doing this on a mac. Any suggestions?

egbertn commented 3 years ago

MITM

I got this message when configuring stunnel4 on Raspberry PI 4 B (arm). My conclusion now, is that 32 bit support for raspberry pi is quickly going down. stunnel4 for arm, lacks features, and recompiling the latest stunnel4 on raspi no longer possible.

To skip the lah-di dah, what I did is following the instructions for Bash on Ubuntu on Windows (WSL 2) and now it works by pointing the RTMP server to rtmp://172.28.165.42/live

jack-fdrv commented 3 years ago

I used centos, but was unable to run stunel, so i switched to Ubuntu 18 with this guid, and it works for me!

DanielFrankDK commented 10 months ago

MITM

I got this message when configuring stunnel4 on Raspberry PI 4 B (arm). My conclusion now, is that 32 bit support for raspberry pi is quickly going down. stunnel4 for arm, lacks features, and recompiling the latest stunnel4 on raspi no longer possible.

To skip the lah-di dah, what I did is following the instructions for Bash on Ubuntu on Windows (WSL 2) and now it works by pointing the RTMP server to rtmp://172.28.165.42/live

That did not explain what you did, at all.

egbertn commented 10 months ago

To skip the lah-di dah, what I did is following the instructions for Bash on Ubuntu on Windows (WSL 2) and now it works by pointing the RTMP server to rtmp://172.28.165.42/live

You should install and configure it using WSL 2, -if you have windows-.