Stream unavalibale

[erick kurniawan]

Hi 

I faced trouble here

1.I already push teh stream but the stream status at streams unavalibale 

2.i already change port 8080 to 8000 , streams preview oflfline but i play at rtmp player it can be play 

any suggest 

[Balder Vietor]

Hello Erick,

It's a bit hard to go on what your problem might be from just this, Using the tools -> email for help option to the left in the MistServer interface should send a help ticket with the information we'd need to help you better. Still I'll try and give a few pointers that might be the problem:

Stream unavailable usually means the stream source isn't active, for a live stream that usually just means it isn't being pushed, accepted or is lost due to restrictions on your network like a firewall.

Make sure the protocols are available

If you want to use RTMP streaming make sure RTMP is active in the Protocol panel, if you want to see HTTP playback (hls/mp4/webm/flv) make sure that both HTTP and the corresponding protocol is active. If you're in doubt you can always enable all default protocols and everything should be set up. Double check if the status of the protocols is on "Active", it might take a few seconds or a page refresh for the status to change.

Check if the push is coming into MistServer

You can see if the push is reaching MistServer by attempting a push and then going to the log. The log will mention if the stream has been accepted or rejected. If you see nothing at all it's not reaching MistServer and you might need to check your push settings or firewall settings.

To see all relevant log messages please set the Debug level of your stream to 4 in the stream edit/creation panel

Log: Push rejected

If a push is rejected it's usually that the source hasn't been white listed, you should see:

 Push from ADDRESS to kaas rejected - source host not whitelisted

If this is the problem it means the stream you're pushing to has a different value for address than you've set. Go to the stream settings and edit the push address to match the address in your log message, that should solve your problem.

If the address does match the address in MistServer it means you've set a password and aren't matching the password. Check the stream url you've set in your pushing application and have it match the push settings available when you edit the stream.

Log: Stream not configured

If the following error shows up:

 Push rejected - stream NAME not configured or unavailable

It means your push isn't matching a stream name set up within MistServer. Either change the stream name within MistServer to match the name given in the log or change your pushing application to match the name within MistServer.

Log: No log messages at all

If you see no log message at all when you try to push it means your pushing application isn't actually sending any data to MistServer. This is most likely because you didn't get the address right in your pushing application. Double check the address of your server running MistServer and the address you've filled in into your pushing application. There's also a chance you've filled in the wrong port number and are sending data to the HTTP port, if you use the standard RTMP port (1935) within MistServer you can leave out the port number from the url when pushing.

If those match it's a firewall blocking the RTMP stream, check your firewall settings on the server that's running MistServer and make sure port 1935 (TCP) is available (use another port number if you've changed the RTMP port number). 

Log: Stream being accepted

For this message you need your stream to be at log level 4 or higher, you should see:

 Input for stream live started

with the tracks being detected and either accepted/rejected. If they're rejected they should tell you why. If they're accepted you should see the following:

 Stream live became active

If you see these messages it means your stream is being accepted and should've become available, if this shows up and you still cannot view the stream it's most likely a firewall. Check your firewall settings to see if the HTTP port within MistServer is being blocked (the TCP port corresponding to the number used within MistServer, defaults to 8080). 

Hope that helps, if you still run into trouble please let me know.

With kind regards,

Balder Viëtor
Head of Testing

--
You received this message because you are subscribed to the Google Groups "Mistserver.org" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mistserver+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[erick kurniawan]

Wow tx u , i tried to restart my vps and creat stream again work fine but im faced another problem

When i embed the code for my wordpress website it is no show at all

I set all to automatic 

[Balder Vietor]

Hey Erick,

Wordpress is a bit picky. To include live streams or players that aren't the one included in Wordpress you'll need to use an iframe. Those are also blocked by default, but luckily there's more Wordpress users out there.

https://wordpress.org/plugins/iframe/#description

Instead of the embed code paste the HTML ( http://ADDRESS:PORT/STREAMNAME.html ) address in there. That should work. 

With kind regards,

Balder Viëtor
Head of Testing