Any possibility to send stream without registering it first

[xoraingroup]

Is there any possibility to allow rtmp streams without registering them first via api or UI?

We can add blocking triggers to authenticate the streams by our backend. I checked everything and there does not seem to be any option.

Also one another question, I couldn't find how to enable rtmps along with rtmp.

Many thanks :)

[Rokamun]

Hey there, The wildcard functionality is probably what you're looking for. It allows you to set up a single stream and create additional streams using the same setup on the fly. A good explanation of this is found here: https://news.mistserver.org/news/90/How+to+build+a+Twitch-alike+service+with+MistServer#How_to_support_infinite_streams_without_configuring_them_all (Don't worry, we're working on making the website easier to use as well ;) ) RTMPS isn't available input wise right now, though we do plan to include it soon as it's been requested more. If you need something for users to authenticate we'd recommend using the PUSH_REWRITE trigger. It uses the same idea as the RTMP_PUSH_REWRITE trigger as explained in the Twitch alike service article, but is slightly newer so it'll work for SRT streams as well. An example of that trigger is given here: https://news.mistserver.org/news/114/Simple+token+support+for+live+streams RTMPS output is already available, the only thing you'd need to do is try and push out to an RTMPS address. With kind regards, Balder Viëtor Head of Testing MistServer

…

On Thu, Sep 28, 2023 at 3:32 PM xoraingroup ***@***.***> wrote: Is there any possibility to allow rtmp streams without registering them first via api or UI? We can add blocking triggers to authenticate the streams by our backend. I checked everything and there does not seem to be any option. Also one another question, I couldn't find how to enable rtmps along with rtmp. Many thanks :) — Reply to this email directly, view it on GitHub <#181>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAN2RJE2KV2374ECIDQWO73X4V36BANCNFSM6AAAAAA5K7IFQ4> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[xoraingroup]

Hi Balder,

Thank you very much, it has cleared alot of things. Few questions though,

I was trying trigger for one of our test backend server using https.

Does it support https triggers?

Is the method type POST for trigger? and what is the content type that it posts to remote server.

Also when is the expected time for rtmps to be incorporated?

Thank you :)

[Rokamun]

Hey there, HTTPS triggers are supported and they are indeed POST. MistServer does a post to the given address and expects the reply back in the body. I don't believe we set a content type, but if we do it'll be text/plain. The body itself shouldn't contain a white line & if it's a boolean only the first letter is read. If there's no body the trigger is assumed to be failed and the default response is used instead. RTMPS is something we actually want to finish up this week, so it shouldn't take long, but realistically I can see it take 2 more weeks before it's done. With kind regards, Balder Viëtor Head of Testing MistServer

…

On Thu, Sep 28, 2023 at 8:01 PM xoraingroup ***@***.***> wrote: Hi Balder, Thank you very much, it has cleared alot of things. Few questions though, I was trying trigger for one of our test backend server using https. Does it support https triggers? Is the method type POST for trigger? and what is the content type that it posts to remote server. Also when is the expected time for rtmps to be incorporated? Thank you :) — Reply to this email directly, view it on GitHub <#181 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAN2RJEO3PSLBCVILV5KF3TX4W3OLANCNFSM6AAAAAA5K7IFQ4> . You are receiving this because you commented.Message ID: ***@***.***>

[xoraingroup]

Ok thank you very much. Lets keep this issue open till https is available. Also documentation would be needed related to at webhooks (triggers) etc.

Thank you once again