Playback Error, no compatible streams are currently available

[Luke 37064]

My device is galaxy S8+ and galaxy S6, both has same problem 

Thank you. 

 

Ok, thanks for the info. Please try again with the next update to the app. Thanks.

[jurgenhaas 0]

I'm having the same issue. Just installed a new servier this morning (Ubuntu 16.04) and I do use a LetsEncrypt cert as well.

 

On web browser, playing music is working just fine.

 

From the Android app, I have an interesting observation: on a Google Pixel 2 it ios working OK but on 3 different Samsung devices (S9, Tab A, Tab S3) I do get the "no compatible stream available" error message.

 

This is the app version 2.9.92 dated March 12, 2018 and I guess this is still not yet the new one, right?

[Luke 37064]

Hi, yes it's an issue specific to Samsungs over https. Please try again with the next release of the app, thanks.

[andstein85 6]

Any idea when the next release of the Android App will be? This is still an issue and I'm not about to send the login password of my media server over the internet unencrypted...

 

Using the browser or tunneling through my VPN when I'm not at home is the only workaround for now but streaming over a VPN while transcoding at the same time is much more resource intensive and not very reliable.

[Luke 37064]

We are working hard on the next release and hopefully we will have something soon. Thanks !

[darkassassin07 423]

I'm not about to send the login password of my media server over the internet unencrypted...

 

Using the browser or tunneling through my VPN when I'm not at home is the only workaround for now but streaming over a VPN while transcoding at the same time is much more resource intensive and not very reliable.

I highly recommend looking into setting up NGINX as a reverse proxy into emby. Waayyy more control over the ssl/tls (https) side of things and Im finding it to be more reliable across all my devices.

I avoided it for quite some time because it didn't seem worth the effort but Im glad I switched.

Currently running it on a raspi along side pihole (a black hole for internet ads)

https://www.ssllabs.com/ssltest/ gives me an A+ now.

 

 

@@Luke by comparison embys https port as of 30seconds ago has an F as it has the default DH parameters, and uses ssl 2/3 only (both vulnerable). This is the first time I have tested embys security, probably should have sooner.

 

Here are some parameters that are compatible with every device/browser except IE6/IE8 on Win XP tested on the above site,

Maybe it will be useful to you:

 

(NGINX config)

ssl_protocols TLSv1 TLSv1.2;

ssl_ciphers "

ECDHE-RSA-AES256-GCM-SHA384:

ECDHE-RSA-AES128-GCM-SHA256:

DHE-RSA-AES256-GCM-SHA384:

ECDHE-RSA-AES256-GCM-SHA384:

ECDHE-RSA-AES256-SHA:

DHE-RSA-AES128-SHA";

 

Personally I have TLSv1 removed from that list as well because I dont need compatibility with those devices.

Note:ssl_ciphers needs to be all one line if used in nginx

 

 

Server V3.1.4.0 Windows 7

Edited June 21, 2018 by darkassassin07

[andstein85 6]

I highly recommend looking into setting up NGINX as a reverse proxy into emby. Waayyy more control over the ssl/tls (https) side of things and Im finding it to be more reliable across all my devices.

I avoided it for quite some time because it didn't seem worth the effort but Im glad I switched.

Currently running it on a raspi along side pihole (a black hole for internet ads)

https://www.ssllabs.com/ssltest/ gives me an A+ now.

 

Thanks for the info! So you're running the nginx proxy on a raspi and emby server on a separate windows box? Are you forwarding requests from 443 on the proxy to the standard emby server https port? My ISP is a real pain in the ass about running apps on 443 open to the internet but I digress, that's obviously not a road block in getting this running.

 

I'll probably spin up a small CentOS or Ubuntu VM to test this out because I'm not really a fan of nginx on Windows

[Luke 37064]

I've seen plenty of A+ reports here as well, so I think it depends mostly on what OS you're using as well as your certificate.

[darkassassin07 423]

@@Luke Both Emby and NGINX in my tests are using the exact same cert (LE) in those tests so that's not the problem, Emby shouldn't provide horrible security just because it's running on Win 7 Pro. I could understand if I was trying to run it on vista or something like that... but I'm not.

There is no way there have been A+ scores using embys built in https:

One of the requirements there is HSTS (strict transport security) which is something you would only use if you know everything on that hostname is https only,

Emby also uses the default DH primes (1024bit) which are shared across many public servers. 

It's possible for an end user to strengthen this with some digging but there is no documentation for it and no recommendation/mention that you should even try.

 

What do you get if you test a server of your own rn?

 

 

@andetein85

Yes, NGINX is running on Raspbian on a RPI 3B, and Emby is running on a separate Win 7 machine on the same LAN.

I'm using port 443 to connect to NGINX but you can just as easily configure any port you like just as you can emby. From there NGINX proxies to embys http port (not https).

Emby has a setting under 'Advanced'  'Secure connection mode' set to 'Handled by reverse proxy'. With this Embys WAN address uses https (ie emby tells it apps to use https) but doesn't require that connection to be on the https port. Then just make sure the public https port in emby matches the one you are connecting to NGINX with, and the external domain matches the path to emby.

For example: mydomain.lol/emby if you put emby in a /emby location in NGINXs config

This gives me the 'Remote (WAN) access: https://mydomain.lol/emby:443'

Edited June 21, 2018 by darkassassin07

[Luke 37064]

Like i said, we've seen plenty of A+ results. To some degree we do utilize the components of the underlying operating system.

[darkassassin07 423]

Are you telling me that windows 7 only supports ssl 2 and ssl 3, two very outdated protocols that are both considered insecure?

 

This isn't a problem for me now that I have NGINX, but it's kinda concerning that you don't even want to consider looking into it.

[Luke 37064]

We're able to configure the allowed protocols and we're leaving it at platform default.

[darkassassin07 423]

@@Luke What do you get if you test a server of your own rn?

Really curious to see what you come up with.

 

 

Correct me if I'm wrong but it really sounds like your saying 'it is what it is, deal with it'

 

I have to say Luke if NGINX wasnt an option id be looking for an emby alternative rn. I can't believe how blasé you are about this conversation....

Emby running on a common os fully updated produces a terrible result and you just don't care.

 

We aren't exactly securing gov't secrets here but that doesn't mean you should ignore security.

 

 

I feel bad for the people that arent savvy enough to even know to look into this. I put it off for far too long myself.

 

/edit I do only have a sample size of one so when I get home im going to mess with a vm and see what happens with a brand new install

 

/edit 2 This is going to take a little while. I'll test my current server, a brand new win 7 vm and a Ubuntu vm then post the results as a new thread. Enough high jacking this one

Edited June 22, 2018 by darkassassin07

[Luke 37064]

We have a new app release that is slowly rolling out. Please try that once it comes to you. Thanks.