Forum

Post a new question

Categories:

Tags:

How to use Hot-link protection with nimble and stalker portal?

Rebel Nick 2015-05-25 03:39:14 UTC in Paywall: WMSAuth and beyond
Ee40727c4b67e2461d69bf5e675955b7

Yury Udovichenko 2015-05-25 04:33:12 UTC
8926135388643c4be9ec685a7033dc32

Hi,

Our hotlink protection requires you to sign media URLs with signature which includes a password and a few more things like IP address.
We're not falimiar with the Stalker but If you can make such signature there, then Nimble streams can definitely be protected that way via the portal.

Give us more details if there are still some concerns so we could advise.

Thank you.

Rebel Nick 2015-05-25 04:44:05 UTC
Ee40727c4b67e2461d69bf5e675955b7

This is a very common portal and is used with the very popular MAG250 box.
Stalker portal has instructions for setting up temp URLs with WoWZA:
http://wiki.infomir.eu/doku.php/en:stalker:temporary_links_for_wowza

And for NGINX secure Link:
http://wiki.infomir.eu/doku.php/en:stalker:tv_on_http_nginx_udpxy

It also works with Flussonic.

But we can't work out if we can use it with Nimble without modifying the Stalker portal source code?

Yury Udovichenko 2015-05-25 05:43:09 UTC
8926135388643c4be9ec685a7033dc32

Setting link to include signatures will most likely require additional module creation. However, you can ask people from Stalker if it's true or not.

Ioannis 2017-03-24 14:27:56 UTC
Efb1624f5d88a5d95f9e25fcab97fbe2

If i could get the some IPs from from stalker that i want to allow, could I feed them into nimble through the API?

Yury Udovichenko 2017-03-25 01:45:23 UTC
8926135388643c4be9ec685a7033dc32

Yes, please heck this page: https://wmspanel.com/api_info#sb_wms_ipranges

and then other calls from WMSAuth API to add allow rule if you haven't added it yet.

Devon 2018-03-05 01:45:37 UTC
68123b5f3cbac7efe755eb52b0d22de6

HI anyone know how to setup nimble on stalker portal ? they do have nimble as token for stream, however now sure how do i setup my nimble server to accept the stalker clients via token

Denis Slobodskoy 2018-03-05 02:20:58 UTC
C723b4e32e1909d3d1b5519f98b586fe

You should set password in WMSAuth settings: http://blog.wmspanel.com/2013/11/nimble-streamer-protect-hotlinking-domain-lock.html
and set the same password in Stalker's config.ini with NIMBLE_KEY parameter.

Devon 2018-03-05 03:58:56 UTC
68123b5f3cbac7efe755eb52b0d22de6

Thanks for the response, i did that however it is not working... do you know another setting that i need to do on my nimble ?

Denis Slobodskoy 2018-03-05 04:42:32 UTC
C723b4e32e1909d3d1b5519f98b586fe

You should set password in the bottom of WMSAuth rule page and set time tolerance, e.g. 30 seconds - it defines acceptable time divergence between Nimble and web server (stalker). Tick all protocols and leave all other fields (except rule name) blank to protect all streams.

Devon 2018-03-05 12:18:55 UTC
Af354792d3ae8daf1d9696170f19a2cd

Yes, i did all that part and i think im doing something wrong on generating the stream or the format of the output stream url on stalker.

New to nimble and learning still. If you know the format or the url pkease let me know of any tutorial about how to get the output stream will help

Denis Slobodskoy 2018-03-06 04:39:43 UTC
C723b4e32e1909d3d1b5519f98b586fe

As I understand, Stalker should generate links with signature (adds ?wmsAuthSign=...) when you configure Nimble protection.
I noticed that stream name you set in WMSAuth settings doesn't match your outgoing stream exactly - please fix it.

Post a reply