Re-Streaming using NGINX
Posted
#193
(In Topic #36)
Standard member
A few questions about the video
Hi!First of all, thanks for the great video! It is a great idea to handle these kind of things ourselfs if it is not all to difficult.
I do have a couple of questions, maybe some of you have an answer.
The RTMP server I am trying to publish to needs authentication. Normaly in, in streaming software this is easy to set-up, but can't find out how right now.
I tried the following: rtmp://user:pass@streamserveradress.com/streamkey this gives the following error: nginx: [emerg] invalid port in url "user:pass@streamserveradress.com/streamkey" in /usr/local/nginx/conf/nginx.conf:26
If I add in an portnumber the same error occurs. rtmp://user:pass@streamserveradress.com:1935/streamkey
Any ideas?
Thanks!
Posted
NOTS Staff
So, the error message you're getting is because a colon (:) in a URL generally indicates a port. There was a time when HTTP websites authenticated using user:pass@, but that time has long since passed, and RTMP doesn't use that formatting to my knowledge.
In order to authenticate RTMP through a URL, you'll probably have to add the username and password to the end of the URL, as query parameters. That means you'll have a question mark (?) followed by the username and password in some configuration. Exactly what configuration that is, I can't say unless I know what software you're using for the actual RTMP server (or what website you're re-streaming to that requires authentication.) For Nimble Streamer, the end of the URL is "?rtmpauth=push_login:push_password" (the colon doesn't mess anything up here because the question mark means it's a query parameter, so it can't be a port.) For Wowza, the end of the URL might be something like "?user1&pass1", but you might need to set some extra configuration files up.
What website/software are you streaming to?
Posted
Standard member
I am indeed streaming to a Wowza server. But I do not have direct control over the server.
What i've found yesterday since i've posted my question is that I need to install some modules on the wowza instance to make it possible to use a single URL.
I've reached out to my wowza provider, let's hope they can help me with that
Posted
Standard member
I loved you video, I was very helpfull
I would like to ask you if there is a way to create a stream player…
Instead of sending the video to Twitch or Facebook, send it to a personal player, so it shows it with no watermark or anything else.
And how can this be done?
Thanks!
Posted
NOTS Staff
RichyCapy said
I would like to ask you if there is a way to create a stream player…
Instead of sending the video to Twitch or Facebook, send it to a personal player, so it shows it with no watermark or anything else.
And how can this be done?
Thanks!
From “Post #285”, December 4th 2018, 10:40 AM
Hello RichyCapy, welcome to the forums.
For a non-branded/custom-branded video player, you can use a frontend like Video.js or MediaElement.js. However, setting up a media server on the backend so you don't have to depend on Twitch or Facebook is an entirely unrelated topic, and one which I haven't explored myself yet. I'll be sure to make a video when I eventually do this for myself, but until then, I don't have advice to give on this topic, aside from knowing that it takes a lot of money and bandwidth to do what you're asking.
1 guest and 0 members have just viewed this.