jamiephonic / rtmps-hls-server Goto Github PK

Best regards.

I set up the service in docker, currently the server I added the https to have the HLS signal with valid SSL certificate, everything works fine until I enable :

exec_push /usr/local/bin/ffmpeg -i rtmp://localhost:1935/$app/$name -async 1 -vsync -1
-c:v libx264 -c:a aac -b:v 256k -b:a 64k -vf "scale=480:trunc(ow/a/2)*2" -tune zerolatency -preset superfast -crf 23 -f flv rtmp://localhost:1935/show/$name_low
-c:v libx264 -c:a aac -b:v 768k -b:a 128k -vf "scale=720:trunc(ow/a/2)*2" -tune zerolatency -preset superfast -crf 23 -f flv rtmp://localhost:1935/show/$name_mid
-c:v libx264 -c:a aac -b:v 1024k -b:a 128k -vf "scale=960:trunc(ow/a/2)*2" -tune zerolatency -preset superfast -crf 23 -f flv rtmp://localhost:1935/show/$name_high
-c:v libx264 -c:a aac -b:v 1920k -b:a 128k -vf "scale=1280:trunc(ow/a/2)*2" -tune zerolatency -preset superfast -crf 23 -f flv rtmp://localhost:1935/show/$name_hd720
-c copy -f flv rtmp://localhost:1935/show/$name_src;

I send 4 signals and only in 1 I get the audio and video from the signal, in the others I only get the audio, I thought that maybe it was server, so with this test signal:

rtmp://stream.mediaserver.com.co:8083/live/buenisimatv

when trying to broadcast from my local pc each signal, I realize that the rtmp link sometimes connects well and sometimes stays idle as in a timeout style, I pass my current configuration file, which did not add the options but only left the part of the bandwidth, but I would like everything to work from the s
nginx.txt
erver or if done from outside the connection to the rtmp is agile and without timeout

Hello,

Initially when I had tried the container. It just crashed when I'd start it.

I was trying to use the minimal config. If I commented out the following nginx works as expected.

#listen [::]:1935;

Is it something I'm doing wrong or forgetting? Or something that was left in the minimal config by accident?

Thanks.

Hi there,

I have deployed this on a kubernetes cluster.

I have a working SSL wildcard certificate on the cluster.

I have deployed this service on a subdomain and I am receiving an SSL error for this subdomain. http only is working

curl -iv subdomain.domain.io

url -iv --tlsv1.2 https://subdomain.domain.io             35 ↵
*   Trying xxx.xx.xxx.xx:443...
* Connected to subdomain.domain.io (xxx.xx.xxx.xx) port 443 (#0)
* ALPN: offers h2
* ALPN: offers http/1.1
*  CAfile: /etc/ssl/cert.pem
*  CApath: none
* (304) (OUT), TLS handshake, Client hello (1):
* error:1404B42E:SSL routines:ST_CONNECT:tlsv1 alert protocol version
* Closing connection 0
curl: (35) error:1404B42E:SSL routines:ST_CONNECT:tlsv1 alert protocol version

Could this be a conflict with the SSL that is provided out of the box?

Have you set this up before?

Hi, how can I map the nginx html directory to the host assets path?

I only see configs, players, ssl in the assets path on my host machine.

Hello
If someone is sending a stream to the server
How can it be stopped from the server?
For example, we only know that the stream key is "test12345"