Protection for incoming streams

Gabriel 2017-10-11 04:55:28 UTC in Nimble Streamer


I test nimble streamer.

I need accept only incoming stream from created applications, as wowza does.

Actually any publishers can push any streams to my server through the specified port.

Try to follow this guide, but still anyone can send signal to my server:


Gabriel 2017-10-11 05:01:27 UTC 

Sorry, anyone is a error word (I use google traslate).

All people can send signal to my server when nimble is running, I need solve this.

Alex Pokotilo 2017-10-11 05:42:37 UTC 

Please check
if you need to setup publish password please fill Push Login/Push password in "Global" settings so nobody without password can push.
In addition you can setup per Application login/password.

Gabriel 2017-10-11 05:51:51 UTC 

sure, but we are a streaming provider. If we use the push password, it would be the same for all clients. Upon termination of a client, the client could continue to log in with the global password. What I need, is to only accept the incoming stream of the applications that I activate. And when you delete an application, it can not continue to connect.

Denis Slobodskoy 2017-10-11 07:01:45 UTC 

Hello Gabriel.
You can set up publish control with signature (you will need to generate signature for client and put it in publish URL) or authorization handler (providing authentication procedure on your own server). These procedures are described in in "Using publish signature" and "Using publish authorization handler" sections.

Gabriel 2017-10-11 15:12:24 UTC 

And it is.

But the password is only for the application that I configure.

Anyone can send signal to the server, in other applications.

Maybe there is something I am not understanding well. I apologize.

What I need is that they can only send signals to the server, in the applications that I activate.

As in wowza, it only receives signal when I create the application.

Alex Pokotilo 2017-10-11 23:09:38 UTC 

1)you should specify random login and password in Nimble Streamer->Live Streams Settings->Global. This way your users will not be able to publish streams to "nonexistent" application.
2)if you can create separate application settings for all your clients just create application for every client and specify exact password. Please note that if you delete application after that this will block new publishing request but currently publishing streams will work till restart
3)if you need ability to block any stream during publishing you need to setup "Publish control" from "Control"->"Publish control" menu. You need to specify unique password for each application and specify your handler as well.

Please note that to prevent unauthorized publishing you need to specify "Nimble Streamer->Live Streams Settings->Global->Login|Password" in anyway. If you don't anyone can publish to our server using any application name. Nimble and Wowza works differently. When you setup Nimble don't use experience you had with another media server.

Gabriel 2017-10-12 00:40:53 UTC 

Thank you

Yes, but if I specify "push login" and "push password" (in live stream settings -> Global), all my clients must use same user and password to connect.

Anyone who has that user and password, will be able to connect without my authorization.

I need only accept incoming stream for autorized users (applications).


Gabriel 2017-10-12 02:33:16 UTC 

For example in Wowza is:


Gabriel 2017-10-12 02:34:28 UTC 

Solved another question (protect incoming stream)

Thank you!

Denis Slobodskoy 2017-10-12 10:48:30 UTC 

Hi Gabriel
Sorry for delay.
There is a method to limit bitrate, but it pretty complicated.
You must follow procedure decribed at "Controlling streaming process" section in

First, you will need to enable management API on you Nimble instance, as it described here: and
In a brief: add line "management_listen_interfaces =" in /etc/nimble/nimble.conf file and you can send management requests to port 8082 from same host.
Then you should create some serivice that will periodically repeat following steps:
1) Get URL for a list of opened streams. Sample response:
2) Get list of streams with ID's with . Sample response:
{"PublishControlStatus":[{"key":"1", "id":"ID_1", "ip":"","stream":"live/one"}, {"key":"2", "id":"ID_2", "ip":"","stream":"live/two"}]}
3) Match streams from rtmp_status with streams from publish_control/status and do POST list of clients you want to deny to . Sample request:

Gabriel 2017-10-12 14:31:34 UTC 

Of course, it's not simple.

There should be some easy method to set the maximum bitrate of a stream.

It's basic.

Any simpler alternative? At least to set a default value for all streams.

Alex Pokotilo 2017-10-12 22:27:12 UTC 

No, it's the only one way

Gabriel 2017-10-13 03:28:33 UTC 

Will it be available in a future update?

Alex Pokotilo 2017-10-13 03:33:54 UTC 

You can do what you need following provided method. You will get simple script with your business logic and you will probably even like you can control your publisher completely implementing any logic you want.

We don't have any plans to implement it in the way you propose. This doen't mean we will not. This doesn't mean we will though.
We got nothing to say more on the subject. If you want to have it now you already got reply.

Post a reply

Post a new question



nimbleNimble StreamerFAQHLSDVRRTMPhlsnimble streamerABRwmsauthcacheNimbleffmpegAPIapitranscoderdvrVODstreamingfailoverDASHwmspanelrtmpvodudprtsppaywallsubtitlesRTSPDispersayoutubelivelivestreamingmp4MPEG-DASHWMSAuthgeopay-per-viewdashstreamerabrWindowsencryptionUDPwhite labelconfiguser agentsmilvideoFFMPEGmulticastMPEG-TSaudioedgere-streamingCORSraspberry pichunksandroidsldpbandwidthmpeg-dashadvertizerDRMvlcrules.confadvertisingipv6FastSpringRAMwms panelthumbnailFMLEVATcrossdomainupdatehttpsmpegtsRecordingSMILplaylistpushaesakamaiserverssslSRTwowzam3u8TranscodeerrorSSLbalanceplaylist_dvrWowzachromecastconfigurationreportingsrtbugIDdownloadS3corsnimblestreamerdomainperformanceIPmpeg-tschunkraspianawspublish controlcodecmobileWMSPanelrepublishingloopVidillionHttpsnimble webcam html5UIRegistration Issuedirect link32-bit Windowstwitchanalysecache_controlitworkmelive abr support mpeg-dashrtmp abrbeirutWWDCdubaideep statshls to multicast udplogIIS Smooth StreamingcloudmediaCDNHTTPSAbrHot-linking protectionHDSvaddioMPEGTSalertsNDIViewer Statsjwplayer websitewhmcsbaselineAuthentication in HLSnginx rtmp nimbleCentOS v6.4durationAV BridgepricelimitOld logsVaddioscreencastPI3 Ubuntuview timewmspanelapiattaching domainsinterfacesDVRRecordingWMSCONFIG_HOMEmessageloadbalancingrestreamcostmetadatamod_rewriteoriginprofileAxisgbpsID3 tagsanalisyswmsauthsignhighhds streamhls hotlinkVideo Playertransocding republishingdecodergentoo install server nimbleAliastranscoding using NvidiaPublic IpPaywall Authlost trafficdocumentationofflineconcurrent-connectionsTrancoderfilelebanonlocationmanifestipMP4 not playedspaceicecast urlruleServer-sidetasks-controlhot linkingseekingchangestoppedamfmainplayoutPlayReadylimuxamazon web servicedvr streamconnectivityunique visitordvr stream twiceonAXVVGhot-linkpay per viewaliasdata slicesblockHLS vodmpeg dash7TCOanalyticsapplicationpaywalbrandingopenssltrialMP4microsoft streamerrorsrocksoftlog traffic statsExpression EncoderdebianABR DASHprogressive downloadHLS Playermultiple originsFFmpegnimblesessionidDASH Playerlive video on demandbandwithCSSserverlog nimble analysertmp playbackvideojsbitrateadaptiveAV1 codecprivate networkJWPLAYERNGINX-RTMPSnapshotsno WMSPanellive videoPullmac osx installsourcecrossdomain more then 1 domain4KwotermarksoundHLS Meta Tag editing.streamsattachmenthelp errorvimeoload balanceconcurrent connectionvod no soundbuttcdnvsomFairplayfallbackamazonControl APIlive streamTranscoderLive streamingWidevineRemote StorageWowza Agentsecuritynot foundpullmpeg2tsServer-Side-Task-ControlAS3disk migrationstereo to monoscreen captureinstall players setup ready to goDVRSettingstwitch larix broadcaster androidAppleDelete recordsicecastdrmresourceaes encryptionsubscriptionlive pull settingsABR HLS Bitratesvideo looprtmp for YouTubestarttime duration seekpointrebootdvr streamsmonitornimble streamer web server php script pageautomationNimble Streamer APIlivestreamoutrateIIS Media Servicsrtmp republishing transcodenimble.confDeep statsapi accessNimble CapacityABR DVR probleminterleavingweb playernimble streamer vod hls transmuxingloggingLive SwitcherlearnerCross Domainscreen freezecan't registercontent-dispositionnot to stealLive Broadcastinsert logoheaderactionscript 3block downloadAVCaptureMovieFileOutputNimble ServerbroadcasterUbuntu artful 17.10Transcoder MPEG DASHMPEG DASHadd_chunk failedPost processingfake extensiontranscodingFFMPEG;RTMP;I/O errorstatus:errorHotlinking ProtectionStreaming routeMPEG-Dashlarix broadcasternimble on cloudroutesprerollThumbnailsserver incorrect timepremium featureLIVELivepaymentincoming streamno soundstatsHow to do live stream with multiple audio tracknimble aliasesProgressivereloadRTMP republishrmtpno internetvp9addemandSecurelivestreamintransocderraspberryavoid refreshreportsAndroiduser_agentdvr on wmspanelS3 AWScloudfrontIOSrestartPIDHLS Streamingthumbnail dvr-thumbnailwmsAuthSignnimble streamer mpeg-ts multiple inputsLoad-BalancingcredentialslatencytranscodeRepublishingadjustDVR SettingPORTHTML5 playerdelaympeg4issuepricingtranscoder nimbleBroadcastLarixABR bitratesPacketizingbuildTeradek Decoderubuntu 18SLDPav1 codec21server iphttp servera recordVR-360Failoverstorage space availablediskNimble connectionsabr fallbackDVRStreamsrulesError when installingdissapointmentpay-per-minuteAWSSO_RCVBUFbuffering videolivestream bitrateUDP Multicastlogo in streamMPEG2 VideossaiDVR Setting limitbufferprogressivewebhookdvr to livefastspringmp2 audiocache expiryQuickTimevideo streamingrtsp push androidartifactstraffichd25publish streamAArch64storagealias route.movdistributionoutputVOD HLS streaming on public IPdomain lockRTMP Republishcontentspeedup my videoiOSqataritworkscdnvideo.js

This website or its third-party tools use cookies, which are necessary to its functioning and required to achieve the purposes illustrated in the Privacy Policy. If you want to know more or withdraw your consent to all or some of the cookies, please refer to the Privacy Policy.
By closing this banner, scrolling this page, clicking a link or continuing to browse otherwise, you agree to the use of cookies.