Do failover URL app name and stream name need to be indentical?
E.g., I have stream "bbcone" on my "hlshigh" app.
if it is offline I want to pull backup stream "bbconelight" from "backup" app.
Live Pull Settings:
edge server app - hlshigh
pulls from origin app - tvhigh
the backup stream works in VLC - rtmp://188.8.131.5236/backup/bbconelight
in a test web page set to play "bbconelight" via the hlshigh app on edge server, it does not pull the backup.
When bbconelight is not found on "hlshigh" (or "tvhigh" on origin) should it then pull from "backup"?
Certainly Nimble should switch to backup stream when primary is not available, but probably source server reports offline stream incorrectly.
Does VLC show any error for primary stream when you trying to playing it while it offline?
The primary stream does not exist.
bbconelight is published to origin backup app with nothing on origin primary app - this is to test failover working.
Web page is set to play bbconelight - which is not found on primary app, so failover should happen?
But, there has never been bbconelight on the primary app.
Here is something strange:
Today I published bbconelight to primary app, then stopped it and published to backup app again.
Now the failover works on the origin server!
Edge server still does not failover when pulling from origin.
Edge server pulls correctly from primary app normally, so this works.
Edge server will also play from backup app if I set the playlist to play backup app (not via failover).
So everything works, apps, streams, live pull from origin etc.
But not when it's all together - failover not working on edge pulling from origin.
edge server 184.108.40.206
hlshigh app pull from
rtmp://220.127.116.11:1936/tvhigh - works on its own
rtmp://18.104.22.168:1936/backup - works on its own
no failover on edge. (set playlist to origin server (same app names) and failover works).
What if source server was offline? Is failover calculated on origin server and not on edge?
There should be no difference between origin and edge server. I guess it may not work properly with dynamic stream names. Try to set log mode to "verbose" and check nimble.log for messages related to livepull.
Also I would recommend to submit support ticket on https://wmspanel.com/help and provide more details.
Thank you for the reply.
I tried a live pull rule with naming the stream and not dynamic but it was the same.
I enabled verbose log, it said "no route for url 'eu2-domain.com':'/hlshigh/bbconelight/playlist.m3u8"
So I tried the test on a different edge server and it seems to be working!
So one of my edge servers must have a configuration error. Despite that I copied and pasted the config from the other working edge server just yesterday! I will set the server up like from new again...
But thanks for the replies. Will open a support ticket if I find it is still not working correctly.
and required to achieve the purposes illustrated in the
If you want to know more or withdraw your consent to all or some of the cookies, please
refer to the