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

JosueAChavez · 2019-04-02T00:29:01Z

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.

The text was updated successfully, but these errors were encountered:

jwainwright87 · 2019-04-02T20:29:12Z

I've just seen the same @JosueAChavez and started panicking. I am using nginx on a raspberry pi to push streams to facebook live and wondering how to do this after 1st May 2019.

I understand at this time that nginx does not support RTMPS however from doing some searching, it looks like you can use stunnel somehow. This looks above my level so I am reluctant to try it on my raspberry pi server.

duoporcoduo · 2019-04-03T10:57:22Z

I'm on the same issue, I use a command today:

push rtmp://live-api-s.facebook.com:80/rtmp/KEY;

push rtmp://x.rtmp.youtube.com/live2/KEY;

When replacing the address with rtmps the server does not rise.

Can someone help?

ForrestScott · 2019-04-03T14:25:17Z

I have the same issue as I also use the RTMP module to stream to FaceBook live.

jwainwright87 · 2019-04-03T15:36:12Z

I am looking at nimble streamer as an alternative, apparently that supports RTMPS

ForrestScott · 2019-04-03T19:19:07Z

Nimble appears to require a subscription? If so, that's not for me.

Lax · 2019-04-04T05:05:15Z

I have a solution to run an stunnel and publish to the rtmps:// address.

~~I will write a brief into doc in a few days~~
Here a link to the steps and key config "RTMP/RTMPS relay with stunnel"

Yes, you need to choose another port if nginx is listening on :1935

ForrestScott · 2019-04-04T10:34:08Z

Lax, I had been reading about stunnel but couldn't figure out how to configure it. Thank you so much for the tutorial!!! I'll give it a shot!

One question: Since nginx is listening on port 1935, doesn't stunnel need to be listening to a different port since they are running on the same machine?

jwainwright87 · 2019-04-04T13:09:41Z

I have a solution to run an stunnel and publish to the rtmps:// address.

I will write a brief into doc in a few days
Here a link to the steps and key config "RTMP/RTMPS relay with stunnel"

I have had a look at this article and I don't understand how it works. Does anyone have any idea?

jwainwright87 · 2019-04-04T13:10:18Z

Lax, I had been reading about stunnel but couldn't figure out how to configure it. Thank you so much for the tutorial!!! I'll give it a shot!

One question: Since nginx is listening on port 1935, doesn't stunnel need to be listening to a different port since they are running on the same machine?

I'm assuming it will be 443

ForrestScott · 2019-04-04T13:33:18Z

jwainwright87, Lax's tutorial has nginx and stunnel running on the same box so they both can't be listening to port 1935. For my testing, right or wrong, I chose port 207 (an unused AppleTalk port) for stunnel to listen on.

Initial testing shows that Lax's example works for me, however I did have to remove the "include = /etc/stunnel/conf.d" line though. It appears to me that right now FB will accept an RTMP or an RTMPS stream regardless of the SLL switch setting.

I use OBS to stream and nginx to relay to FB, YT and a private 3rd party web site. So here is how it works: obs -> nginx (port 1935) -> stunnel (port 207) -> FB. I run nginx and now stunnel on a ubuntu 18.04 server.

jwainwright87 · 2019-04-04T13:42:14Z

@ForrestScott That's ace I'll give that a go. I got a bit confused during one tutorial it was talking about setting up a certificate from the client side. Do you know it stunnel sorts all that out for you. Also, how do you sent the rtmps feed instead of the rtmp address?

Thanks in advanced

franMx · 2019-04-04T14:11:33Z

HI, I'm trying this on a windows machine. Any idea on the configuration to work properly on stunnel?
Tried:
[fb-live]
client = yes
accept = 127.0.0.1:1935
connect = live-api-s.facebook.com:443
verifyChain = no

but got:
Service [fb-live] needs authentication to prevent MITM attacks

ForrestScott · 2019-04-04T15:35:09Z

@jwainwright87 I didn't have to do anything with security certificates. I think that is what the "verifyChain = no" line is about. But I do wonder about that.

I changed my nginx push to FB to this: "push rtmp://127.0.0.1:207/rtmp/;" Again, I am using port 207 for stunnel.

@franMx I got the same message but in my case I think it can be ignored since nginx and stunnel are communicating on the same machine.

franMx · 2019-04-04T16:43:08Z

Thanks, @ForrestScott unfortunately got this one.

2019.04.04 09:46:49 LOG5[1]: Service [fb-live] accepted connection from 127.0.0.1:53922
2019.04.04 09:46:49 LOG5[1]: s_connect: connected 31.13.89.1:443
2019.04.04 09:46:49 LOG5[1]: Service [fb-live] connected remote server from 192.168.15.8:53923
2019.04.04 09:46:49 LOG5[1]: Connection closed: 3591 byte(s) sent to TLS, 3480 byte(s) sent to socket

Would you mind sharing your conf?

ForrestScott · 2019-04-04T17:04:55Z

@franMx , that looks exactly what I see in my log.

Here is my conf:

setuid = stunnel4
setgid = stunnel4
pid = /tmp/stunnel.pid
output = /var/log/stunnel4/stunnel.log
;include = /etc/stunnel/conf.d

[fb-live]
client = yes
accept = 127.0.0.1:207
connect = live-api-s.facebook.com:443
verifyChain = no

franMx · 2019-04-04T19:09:35Z

Thanks @ForrestScott, it's working now. On windows stunnel didn't modified the first part, just second block.

JosueAChavez · 2019-04-05T01:17:34Z

Thank you @Lax for the solution! I tried it and it works perfectly and with little to none performance hiccups 🙌

I wrote instructions for those who are using this on Windows. We are all not doomed after all!

Lax · 2019-04-05T01:29:46Z

Lax, I had been reading about stunnel but couldn't figure out how to configure it. Thank you so much for the tutorial!!! I'll give it a shot!

One question: Since nginx is listening on port 1935, doesn't stunnel need to be listening to a different port since they are running on the same machine?

Yes, you need to choose another port for stunnel if Nginx is already listening on :1935.
(document updated)

jwainwright87 · 2019-04-05T16:04:13Z

Having some issues when I am running the following command
systemctl restart stunnel4 && systemctl status stunnel4

This is my output...

`==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ===
Authentication is required to restart 'stunnel4.service'.
Multiple identities can be used for authentication:

,,, (pi)
root
Choose identity to authenticate as (1-2): 1
Password:
==== AUTHENTICATION COMPLETE ===
● stunnel4.service - LSB: Start or stop stunnel 4.x (TLS tunnel for network daemons)
Loaded: loaded (/etc/init.d/stunnel4; generated; vendor preset: enabled)
Active: active (exited) since Fri 2019-04-05 17:01:04 BST; 27ms ago
Docs: man:systemd-sysv-generator(8)
Process: 1168 ExecStop=/etc/init.d/stunnel4 stop (code=exited, status=0/SUCCESS)
Process: 1174 ExecStart=/etc/init.d/stunnel4 start (code=exited, status=0/SUCCESS)

Apr 05 17:01:04 NginX systemd[1]: Starting LSB: Start or stop stunnel 4.x (TLS tunnel for network daemons)...
Apr 05 17:01:04 NginX stunnel4[1174]: TLS tunnels disabled, see /etc/default/stunnel4
Apr 05 17:01:04 NginX systemd[1]: Started LSB: Start or stop stunnel 4.x (TLS tunnel for network daemons).`

I did have a issue when installing stunnel4. For some reason it would not let me create the stunnel.conf in bash, so I had to manually create the conf file using nano and input the code in there.

Any help would be much appreciated.

jwainwright87 · 2019-04-05T16:08:11Z

I am also getting this when entering the code for the config file:
sudo cat < /etc/stunnel/stunnel.conf

setuid = stunnel4
setgid = stunnel4
pid=/tmp/stunnel.pid
output = /var/log/stunnel4/stunnel.log
include = /etc/stunnel/conf.d
EOF
-bash: /etc/stunnel/stunnel.conf: Permission denied

ForrestScott · 2019-04-05T16:39:30Z

@jwainwright87 , are you running your commands as sudo? It's required but not mentioned in Lax's guide.

jwainwright87 · 2019-04-05T16:52:20Z

@ForrestScott Yes, sorry forgot to mention that. I am also running on Debian Stretch

duoporcoduo · 2019-04-05T17:37:36Z

@Lax, you saved my day, it worked out right here, thank you!

jwainwright87 · 2019-04-05T17:37:49Z

@ForrestScott SOLVED my problem.

Issue I had was I needed to ENABLE=1 stunnel in /etc/default/stunnel4

When I ran the restart, it all worked.

Link to article that helped me https://cindyxiaoxiaoli.wordpress.com/2014/06/04/get-stunnel4-up-and-running-on-ubuntu-14-04/

lbradio · 2019-04-22T19:46:41Z

Lax, I had been reading about stunnel but couldn't figure out how to configure it. Thank you so much for the tutorial!!! I'll give it a shot!
One question: Since nginx is listening on port 1935, doesn't stunnel need to be listening to a different port since they are running on the same machine?

Yes, you need to choose another port for stunnel if Nginx is already listening on :1935.
(document updated)

Did you actually updated the document? It's still on port 1935 ;-) (and I can't get it to work)

Akeem1985 · 2019-04-22T23:18:22Z

Can someone help me I think I am missing something I was able to install stunnel on my nginx server. However I am a bit confuse of the next steps. Can someone help

h1rule · 2019-05-15T07:57:30Z

I still get

[!] /etc/stunnel/stunnel.conf:5: "verifyChain = no": Specified option name is not valid here

nhalstead · 2019-05-18T00:31:56Z

Just a note as well, Facebook is closing the usage of RTMP and only allowing RTMPs starting November 1st 2019. Facebook has reset static/persistent stream keys and in addition the stream defaults for the user to use is RTMPs, you just need to uncheck the box that is "Use a secure connection (SSL)".

(This is related to Facebook Pages, Streaming to User Accounts, "Share on your timeline", I believe are forced)

nhalstead · 2019-07-31T17:50:14Z

@Yesha052 If you would look at the URL that you have posted, that is a Stream Key to Facebook's RTMP (with SSL) for Streaming TO Facebook.

This feed is ONE WAY. So feeding this into ExoPlayer will not work. Check for a different link in the the OG API. Chances are, Facebook will not give you a direct link to get the video feed FROM Facebook servers, you'll probability get a link to the post or something such as that.

In addition this Issue that you are having is NOT related to this issue, Either create a new Issue and work out of that or if you already have one work from that ticket.

kkrishnan90 · 2019-10-06T16:43:51Z

Is there anyway to pass the Facebook streaming key as a dynamic parameter in push directive ? I have been banging my head for the past 2 days to do it. Any help is much appreciated ! Thanks in advance !

ssllqq · 2019-11-15T07:25:45Z

I still get

[!] /etc/stunnel/stunnel.conf:5: "verifyChain = no": Specified option name is not valid here

I just removed verifyChain = no and it started working, by default it no

threehappypenguins · 2020-02-12T16:04:39Z

I tried Lax's instructions, and also tried ForrestScott's changes in the stunnel.conf file, and I still can't get my live stream to show up in Facebook. When I type in nano /var/log/stunnel4/stunnel.log the log is blank.

When I type in systemctl restart stunnel4 && systemctl status stunnel4 I get:

● stunnel4.service - LSB: Start or stop stunnel 4.x (TLS tunnel for network daemons)
   Loaded: loaded (/etc/init.d/stunnel4; generated; vendor preset: enabled)
   Active: active (exited) since Wed 2020-02-12 12:00:44 AST; 21ms ago
     Docs: man:systemd-sysv-generator(8)
  Process: 22516 ExecStop=/etc/init.d/stunnel4 stop (code=exited, status=0/SUCCESS)
  Process: 22521 ExecStart=/etc/init.d/stunnel4 start (code=exited, status=0/SUCCESS)
      CPU: 21ms

Feb 12 12:00:44 CRPC-HC2 systemd[1]: Starting LSB: Start or stop stunnel 4.x (TLS tunnel for network daemons)...
Feb 12 12:00:44 CRPC-HC2 systemd[1]: Started LSB: Start or stop stunnel 4.x (TLS tunnel for network daemons).

Is this normal? How do I even go about figuring out where its going wrong when the log is blank too?

threehappypenguins · 2020-02-12T16:35:17Z

I'm starting to think that maybe this is a port forwarding issue for me. So when I created my nginx server, I did so on my Odroid HC2. Because I need access to port 80 on it, in the nginx.conf file, I changed the listen address from 80 to 8725 (made up number). So then in port forward, I have external port 1935 forwarded to internal port 8725 (for my Odroid's internal IP address).

So then I thought that I should forward internal port 19350 (for stunnel) to 8725 as well. But I still can't receive the Facebook stream. Thoughts?

threehappypenguins · 2020-02-12T19:09:08Z

I had to give up on my Odroid. I ended up signing up for Amazon AWS EC2 and installed nginx and stunnel on Ubuntu. I used ForrestScott's setup for stunnel.conf but with port 19350 instead:

setuid = stunnel4
setgid = stunnel4
pid = /tmp/stunnel.pid
output = /var/log/stunnel4/stunnel.log
;include = /etc/stunnel/conf.d

[fb-live]
client = yes
accept = 127.0.0.1:19350
connect = live-api-s.facebook.com:443
verifyChain = no

Apparently, what is supposed to show when I restart stunnel with systemctl restart stunnel4 && systemctl status stunnel4
is

● stunnel4.service - LSB: Start or stop stunnel 4.x (TLS tunnel for network daemons)
   Loaded: loaded (/etc/init.d/stunnel4; generated)
   Active: active (running) since Wed 2020-02-12 18:56:54 UTC; 7ms ago
     Docs: man:systemd-sysv-generator(8)
  Process: 31140 ExecStop=/etc/init.d/stunnel4 stop (code=exited, status=0/SUCCESS)
  Process: 31389 ExecStart=/etc/init.d/stunnel4 start (code=exited, status=0/SUCCESS)
    Tasks: 1 (limit: 1152)
   CGroup: /system.slice/stunnel4.service
           └─31414 /usr/bin/stunnel4 /etc/stunnel/stunnel.conf

Feb 12 18:56:54 ip-172-31-4-177 stunnel[31413]: LOG5[ui]: Running  with OpenSSL 1.1.1  11 Sep 2018
Feb 12 18:56:54 ip-172-31-4-177 stunnel[31413]: LOG5[ui]: Update OpenSSL shared libraries or rebuild stunn
Feb 12 18:56:54 ip-172-31-4-177 stunnel[31413]: LOG5[ui]: Threading:PTHREAD Sockets:POLL,IPv6,SYSTEMD TLS:
Feb 12 18:56:54 ip-172-31-4-177 stunnel[31413]: LOG5[ui]: Reading configuration from file /etc/stunnel/stu
Feb 12 18:56:54 ip-172-31-4-177 stunnel[31413]: LOG5[ui]: UTF-8 byte order mark not detected
Feb 12 18:56:54 ip-172-31-4-177 stunnel[31413]: LOG5[ui]: FIPS mode disabled
Feb 12 18:56:54 ip-172-31-4-177 stunnel[31413]: LOG4[ui]: Service [fb-live] needs authentication to preven
Feb 12 18:56:54 ip-172-31-4-177 stunnel[31413]: LOG5[ui]: Configuration successful
Feb 12 18:56:54 ip-172-31-4-177 stunnel4[31389]: Starting TLS tunnels: /etc/stunnel/stunnel.conf: started
Feb 12 18:56:54 ip-172-31-4-177 systemd[1]: Started LSB: Start or stop stunnel 4.x (TLS tunnel for network

Lastly, I can see errors with stunnel by typing in systemctl status stunnel4.service or journalctl -ex and press ctrl + c to exit out of it (I am using PuTTY in Windows).

KenSharp · 2020-03-03T09:06:44Z

I really don't know why this bug report is full of so much prattle.

stunnel works fine.

siniztr · 2020-03-18T18:05:43Z

OK so I have the RTMP server running, and can do live streams to a website. I have set up the stunnel4 as done in the instructions and am not getting any error, however Facebook is not seeing an incoming stream, and checking netstat does not show a connection outbound to facebook. I do see the stream listening but not too sure if the RTMP server is connecting to the tunnel.

GordonMatthewson · 2020-04-04T21:18:49Z

got this working, thank you!!!

mathiasseyfert · 2020-04-19T20:36:14Z

I still get
[!] /etc/stunnel/stunnel.conf:5: "verifyChain = no": Specified option name is not valid here

I just removed verifyChain = no and it started working, by default it no

thank you,

that solved my errors in the setup made with these instructions:
https://obsproject.com/forum/threads/facebook-to-deprecate-rtmp-from-live-api-on-5-1-2019.84978/

on Ubuntu 16.04.6:

sudo apt install stunnel4

Edit file stunnel.conf

sudo nano /etc/stunnel/stunnel.conf

setuid = stunnel4
setgid = stunnel4
pid=/tmp/stunnel.pid
output = /var/log/stunnel4/stunnel.log
include = /etc/stunnel/conf.d

Change in stunnel4 ENABLED=0 to ENABLED=1

sudo nano /etc/default/stunnel4

ENABLED=1

Make dir

sudo mkdir /etc/stunnel/conf.d

Edit /create file

sudo nano /etc/stunnel/conf.d/fb.conf

[fb-live]
client = yes
accept = 127.0.0.1:19350
connect = live-api-s.facebook.com:443

restart

sudo systemctl restart stunnel4 && systemctl status stunnel4

Edit file /usr/local/nginx/conf/nginx.conf

from
push rtmp://<the_server_you_want_to_push>/<yout_stream_key>;
to
push rtmp://127.0.0.1:19350/rtmp/<yout_stream_key>;

by the way: this solution (stunnel) is using way less cpu than forwarding via FFMPEG...

shelomito12 · 2020-05-21T00:54:34Z

Hey guys, quick question:

Has anyone tried using 2 different Facebook streams on nginx and stunnel?

I'm a little bit more curious about how the stunnel config would be since both streams would use the same destination domain live-api-s.facebook.com:443

So the following would work?:

[fb-live1]
client = yes
accept = 127.0.0.1:19350
connect = live-api-s.facebook.com:443
verifyChain = no

[fb-live2]
client = yes
accept = 127.0.0.1:19360
connect = live-api-s.facebook.com:443
verifyChain = no

TheRealMattLear · 2020-05-21T00:56:15Z

It is not necessary because the hostname and port do not change, only the stream name changes. You only need a single point in stunnel.

shelomito12 · 2020-05-21T05:44:01Z

It is not necessary because the hostname and port do not change, only the stream name changes. You only need a single point in stunnel.

Thanks! it worked

shelomito12 · 2020-05-22T02:17:30Z

Hey guys sorry for posting this issue here but today, there was a tragedy during streaming.

A friend (DJ) connected to my nginx server via Virtual Dj and reported the following errors:

The facebook stream was only live for 20 minutes, and the audio was terrible (breaking out at all times)
The youtube stream was only live for less than 3 minutes and half of it muted (no audio after a minute or so.
The ffmpeg command only sent audio to one of my radio stations intead of the 2 of them.

Below is my Nginx config:

# RTMP configuration
rtmp {
    server {
        listen 1935; # Listen on standard RTMP port
        chunk_size 4000;
        play_restart on;

        application live {
            live on;
            allow publish 127.0.0.1;
            allow publish all;
            allow play all;
            # Turn on HLS
            hls on;
            hls_path /nginx/hls/;
            hls_fragment 3;
            hls_playlist_length 60;
            # disable consuming the stream from nginx as rtmp
            #deny play all;
            push rtmp://live.restream.io/live/KEY;
            push rtmp://127.0.0.1:1936/rtmp/FBKEY1;
			push rtmp://127.0.0.1:1936/rtmp/FBKEY2;
            exec /home/ubuntu/encoder/bin/ffmpeg -i rtmp://127.0.0.1:1935/$app/$name -vn -c:a mp3 -ac 2 -b:a 64k -ar 44100 -f tee -map 0 [f=mp3:onfail=ignore]icecast://source:hackme@liquidsoap:8080/live|[f=mp3:onfail=ignore]icecast://source:test456@radio.zeno.fm:8000/stream";
        }
    }
}

I want to know whether the issue was on my friends side (maybe a bad internet connection), or an issue on the Nginx server side (see below)

I saw the following lines in the nginx error log:

2020/05/21 20:29:01 [error] 13859#0: *74 hls: force fragment split: -154.310 sec, , client: 186.10.216.130, server: 0.0.0.0:1935
2020/05/21 20:29:03 [error] 13859#0: *74 hls: force fragment split: 162.543 sec, , client: 186.10.216.130, server: 0.0.0.0:1935
2020/05/21 20:29:10 [error] 13859#0: *74 hls: force fragment split: -155.344 sec, , client: 186.10.216.130, server: 0.0.0.0:1935

LoganSound · 2020-05-25T15:58:01Z

I would guess since the problem largely affected audio that your DJ friend was copyright struck.

istvanmate · 2020-05-26T20:00:44Z

OK so I have the RTMP server running, and can do live streams to a website. I have set up the stunnel4 as done in the instructions and am not getting any error, however Facebook is not seeing an incoming stream, and checking netstat does not show a connection outbound to facebook. I do see the stream listening but not too sure if the RTMP server is connecting to the tunnel.

Same here. Happened at least 3 times in the last 3 months, soo quite annoying... stream was pushed to YouTube without any problem, so nginx worked fine, stunnel showed connection from nginx, but Facebook did not get ANY data. I suspect stunnel not connecting correctly to FB, but cannot prove it yet...

ForrestScott · 2020-05-27T17:40:15Z

I may have the same problem. Once in a great while, as in perhaps once every 3 months or so, my FB feed won't start but YT is fine. We start streaming 10 min early before the event so we catch this situation and fix it by restarting the stream.

istvanmate · 2020-05-27T21:20:47Z

I may have the same problem. Once in a great while, as in perhaps once every 3 months or so, my FB feed won't start but YT is fine. We start streaming 10 min early before the event so we catch this situation and fix it by restarting the stream.

@ForrestScott you restart the stream only or the tools too?

ForrestScott · 2020-05-27T22:36:54Z

We just restart the stream from within OBS.

SteveMitto · 2020-05-30T09:08:11Z

How can i fix this error

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

vnfreezone · 2020-06-09T11:37:16Z

How can i fix this error

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

Having the same error :(

ChristofferSthlm · 2020-11-24T14:00:35Z

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 (EAI_NONAME)

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

egbertn · 2020-12-27T11:07:51Z

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 · 2021-03-07T01:09:13Z

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

DanielFrankDK · 2023-11-20T10:48:34Z

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 · 2023-11-20T11:04:14Z

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

JosueAChavez closed this as completed Apr 5, 2019

Akeem1985 mentioned this issue Apr 27, 2019

RTMPS Issue Facebook May 1 Help #1408

Open

vikyvilla mentioned this issue Nov 18, 2019

Is there anyway to pass the Facebook streaming key as a dynamic parameter in push directive ? I have been banging my head for the past 2 days to do it. Any help is much appreciated ! Thanks in advance ! #1459

Closed

michaeltoohig mentioned this issue Apr 29, 2020

Dynamic Facebook Streamkey Supported? #1514

Open

harryjubb mentioned this issue Jun 19, 2020

Move to RTMPS (secure RTMP) for streaming harryjubb/bee_iot#12

Closed

mannyamorim mentioned this issue Mar 14, 2022

Add RTMPS relay support sergey-dryabzhinsky/nginx-rtmp-module#344

Open

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

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

Comments

JosueAChavez commented Apr 2, 2019

jwainwright87 commented Apr 2, 2019

duoporcoduo commented Apr 3, 2019

ForrestScott commented Apr 3, 2019

jwainwright87 commented Apr 3, 2019

ForrestScott commented Apr 3, 2019

Lax commented Apr 4, 2019 • edited Loading

ForrestScott commented Apr 4, 2019 • edited Loading

jwainwright87 commented Apr 4, 2019

jwainwright87 commented Apr 4, 2019

ForrestScott commented Apr 4, 2019

jwainwright87 commented Apr 4, 2019

franMx commented Apr 4, 2019

ForrestScott commented Apr 4, 2019 • edited Loading

franMx commented Apr 4, 2019

ForrestScott commented Apr 4, 2019 • edited Loading

franMx commented Apr 4, 2019 • edited Loading

JosueAChavez commented Apr 5, 2019

Lax commented Apr 5, 2019 • edited Loading

jwainwright87 commented Apr 5, 2019

jwainwright87 commented Apr 5, 2019

ForrestScott commented Apr 5, 2019

jwainwright87 commented Apr 5, 2019 • edited Loading

duoporcoduo commented Apr 5, 2019

jwainwright87 commented Apr 5, 2019

lbradio commented Apr 22, 2019

Akeem1985 commented Apr 22, 2019 • edited Loading

h1rule commented May 15, 2019 • edited Loading

nhalstead commented May 18, 2019 • edited Loading

nhalstead commented Jul 31, 2019

kkrishnan90 commented Oct 6, 2019 • edited Loading

ssllqq commented Nov 15, 2019

threehappypenguins commented Feb 12, 2020 • edited Loading

threehappypenguins commented Feb 12, 2020

threehappypenguins commented Feb 12, 2020 • edited Loading

KenSharp commented Mar 3, 2020

siniztr commented Mar 18, 2020

GordonMatthewson commented Apr 4, 2020

mathiasseyfert commented Apr 19, 2020 • edited Loading

on Ubuntu 16.04.6:

Edit file stunnel.conf

Change in stunnel4 ENABLED=0 to ENABLED=1

Make dir

Edit /create file

restart

Edit file /usr/local/nginx/conf/nginx.conf

from push rtmp://<the_server_you_want_to_push>/<yout_stream_key>; to push rtmp://127.0.0.1:19350/rtmp/<yout_stream_key>;

shelomito12 commented May 21, 2020

TheRealMattLear commented May 21, 2020

shelomito12 commented May 21, 2020

shelomito12 commented May 22, 2020

LoganSound commented May 25, 2020

istvanmate commented May 26, 2020

ForrestScott commented May 27, 2020

istvanmate commented May 27, 2020

ForrestScott commented May 27, 2020

SteveMitto commented May 30, 2020

vnfreezone commented Jun 9, 2020

ChristofferSthlm commented Nov 24, 2020

egbertn commented Dec 27, 2020 • edited Loading

jack-fdrv commented Mar 7, 2021

DanielFrankDK commented Nov 20, 2023

egbertn commented Nov 20, 2023

Lax commented Apr 4, 2019 •

edited

Loading

ForrestScott commented Apr 4, 2019 •

edited

Loading

ForrestScott commented Apr 4, 2019 •

edited

Loading

ForrestScott commented Apr 4, 2019 •

edited

Loading

franMx commented Apr 4, 2019 •

edited

Loading

Lax commented Apr 5, 2019 •

edited

Loading

jwainwright87 commented Apr 5, 2019 •

edited

Loading

Akeem1985 commented Apr 22, 2019 •

edited

Loading

h1rule commented May 15, 2019 •

edited

Loading

nhalstead commented May 18, 2019 •

edited

Loading

kkrishnan90 commented Oct 6, 2019 •

edited

Loading

threehappypenguins commented Feb 12, 2020 •

edited

Loading

threehappypenguins commented Feb 12, 2020 •

edited

Loading

mathiasseyfert commented Apr 19, 2020 •

edited

Loading

from
push rtmp://<the_server_you_want_to_push>/<yout_stream_key>;
to
push rtmp://127.0.0.1:19350/rtmp/<yout_stream_key>;

egbertn commented Dec 27, 2020 •

edited

Loading