Serviio

I am going crazy - been trying to read and solve this problem for a long time.

My internal network is 172.24.13.X - not sure if that matters as it's a private zone, but just the same (some applications don't respect the 172./12 allocation) - not sure if that even matters here.

When running ServiiGo I can play back a stream (as long as I don't seek) without any issues. (Andriod OnePlus X).

For example:
If when running ServiiGo (internal player) I start to play a movie, jump to time index 30 (minutes) the movie will play for a minute or so then "Cannot play this video" error message appears.

To confirm - the "Cannot play this video" message ONLY appears if I seek within something I am streaming.

So - by that logic you would assume my network is somehow stripping the token data right and /or the token is expiring Well how?
I run a Monowall router - LAN is */* to LAN. Besides how would a router screw up a GET / POST or session data? So, by this logic it can't be my router. Further I don't have any other issues on my LAN end (I we've got VPN tunnels, port forwards, etc. - but not on the 172 block)...

That leaves ServiiGo ? anyone else have these issues? Perhaps ServiiGo is not appending the GET data (I assume) to the requesting HTTP URL?

I am a PRO user.
I am running Serviio on Mint 17.1
I have compiled FFMpeg (many versions - even old backdated versions).
I have complied (from source) the FFmpeg version seen on the Serviio downloads page.
The problem doesn't seem to exist when using MediaBrowser (web) seeking.
No apache or other proxy is involved - 23424 simply points to LAN IP of my mediaserver.
I have used the Internal (ServiiGo Player) and BS Player - same result.
Tried flashing my phone (CM) same result. Using my Nexus Andriod Pad = same result.

Things DO work if I install BubbleUPNP on my phone both inside and outside my network (this has been my workaround thus far).

I have completely formatted my media server with a fresh install. I can reproduce on Serviio 1.5.X and 1.6.x. Both Ubuntu and Mint (yeah I know not a real big difference).

That said, when I first used Serviio - it worked flawlessly (but I can't remember what version I was on - I think 1.4.X) w/ServiiGo (but Windows)

What the heck is causing this issue? Can anyone help my sanity.

I am aware the new version of Serviio can remove the token auth checks (please correct me if I am wrong), but this is not a good idea for security reasons. Besides that's negating the problem not fixing it.


In my /tmp folder I see:


Here is the Serviio log

Maybe Will could confirm this (you could try in the ServiiGo thread).

Normally, the m3u8 file created in /tmp is further processed by Serviio on the GET request to add any other query parameters, one of them being the token. This should work (at least works for me when using MediaBrowser on iPad).

It would be good to check the detailed log a bit further up (well, try to play the file again) and there should be a GET request for the m3u8 file (probably with /MANIFEST/ in the URL). Find it and try to open the URL in a browser - post here what you get.

You can do this for
- when you start playing the file, and then
- when you seek in the file (the URL will change, just follow what is in new the log)

Initial play (no seek) in my /tmp:


Play (after seek) in my /tmp:



As you can see no difference (or sign of a URL / token).

I am using FFMpeg from Serviio download page:

If grabbing via GET:
http://1.2.3.4:23424/cds/resource/644/M ... EDIUM.m3u8?
profile=serviigo_hls&authToken=9454bda32cba4ce7a1cadf7388719df8&clientId=0fb0f56a3b564a04982fffc88796085f&start=1676

It seems to have token data.


I think the issue is now related to the internal player? As I can see proper token data.
If I use the internal player (I can seek) if I use BS Player or MX Player seeking is not a option.