Forum

Post a new question

Categories:

Tags:

How can i denied access to direct link of live stream?

lsa 2016-12-06 02:12:14 UTC in Nimble Streamer
6610d42de2d7e2a69689fde8634f088a

Hi!

i've create a live stream using MPEGTS In, MPEGTS Out settings.
MPEGTS In gets UDP.

Finally a get an url: http://server_ip_address:port/server_name/channel/playlist.m3u8

I need to deny direct url to users.
For example, before Nimble, i've managed udpxy to get access to the channel from localhost:
http://127.0.0.1:8080/udp/ip_address
User open in his player a current link:
http://server_ip_address:8000/udp/ip_address and nginx make proxy_pass to http://127.0.0.1:8080/udp/ip_address

Can i do something like this using Nimble?

Yury Udovichenko 2016-12-06 03:43:20 UTC
8926135388643c4be9ec685a7033dc32

Hi,

As you noticed, Nimble generated full URLs that can be used in any way you need for your streaming use cases. If you need to change URLs by proxy or other means - that's fine, but Nimble is not able to do that.

Alex Pokotilo 2016-12-06 04:40:39 UTC
B0af1cee7eb1e40dd284d9982b3aef70

Hi,
I don't get the question.
http://server_ip_address:port/server_name/channel/playlist.m3u8 is not derect access to your source. with nginx you setup http proxy from origin and output is mpegts. if you need mpegts output from nimble your link will look like http://server_ip_address:port/server_name/channel/mpeg.2ts

if you want to setup origin->edge configuration when one nimble get source and anther receive source from the origin you can do that as well.
You can setup nimble to use source from udp proxy too.
What exactly you want to setup ?

lsa 2016-12-06 04:56:25 UTC
88447aea7b017ab991217252e7b8f9cc

I'm sorry, the problem is solved.

My task was to block access from url http://server_ip_address:nimble_port/server_name/channel/playlist.m3u8 to all users, instead that url they get another, wich listens by nginx.

I did not understood, that Nimble listen all interfaces on my server, including localhost (lo).
So i can REJECT access to http://server_ip_address:nimble_port in IPTABLES and use NGINX to proxy url that i give to users to http://127.0.0.1:nimble_port/server_name/channel/playlist.m3u8.

But i have another problem now!

I'm using HLS protocol for output and the sound of my channels is stutters all time. Can i do something with it?

Or i need to start a new topic?

Yury Udovichenko 2016-12-06 05:06:55 UTC
8926135388643c4be9ec685a7033dc32

Regarding specific issues please send your question to our helpdesk via https://wmspanel.com/help

Thank you.

Alex Pokotilo 2016-12-06 05:11:45 UTC
B0af1cee7eb1e40dd284d9982b3aef70

you can setup Nimble to listen on any ip you want. It listen all by default but you can change that.
please file new support ticket via https://wmspanel.com/help and provide Nimble url to hear sound problems and source stream from udp proxy to make sure it's not your source issue. Please setup everything without proxies first and once sound issue gone do whatever your need even though I don't get why you need proxy.

Post a reply