Jump to content

Bitrate exceeds DirectPlay limit error- (Since Android App version 3.1.59)


embyben

Recommended Posts

I am a long time Emby Server user. Love it!  Last night I moved my Emby Server in to a DMZ zone on my firewall.

When I have one rule allowing my LAN to connect to the EMBY in the DMZ over TCP port 8920 which is the HTTPS port,

Web browsers on the LAN can browse the library and play media.

iPAD app on the LAN can browse the library and play media.

But the Android app will not play movies. I get the message "no compatiable streams are currently available"

My firewall needs my TCP 8094 HTTP (not HTTPS) port to also be opened, and then the Android app plays.

Is this meant to be like this?

 

Edited by embyben
Link to comment
Share on other sites

2 hours ago, Luke said:

Hi there, does the remote address displayed on your server dashboard use the https address?

Yes. I confirm.

Running on HTTP port 8096, and HTTPS port 8920.

In-Home (LAN) access: http://1...

Remote (WAN) access: https://6...

Link to comment
Share on other sites

Hi @Luke

It looks as though my issue is just coincidental. I moved my server in to a DMZ zone just as there was an update to the Android app.

My Android app will play low definition movies fine. But high definition movies are not playing.

My embyserver.txt log is attached.

embyserver.txt

Link to comment
Share on other sites

I can confirm 1080p movies will not play on my Android app latest version 3.1.73 but work fine on a previous version 3.1.23

When the app attempts to play a HD movie - The screen rotates from portrait to landscape with the "spinning circle loading icon", then the screen rotates back to portrait, and back to landscape, and back to portrait and back to landscape and then stops.

Screenshot_20210122-070228.thumb.png.8ea19343d25a9dfea938f0d595e83dc9.png

Low def movies play fine. I access emby server over HTTPS. This error is reproduced locally and remotely. I am using a Google Pixel 3XL Android version 11.

I have cleared the logs and reproduced this issue.

There seems to be an issue here

2021-01-22 07:02:26.245 Info App: Bitrate exceeds DirectPlay limit: media bitrate: 10366897, max bitrate: 4000000
2021-01-22 07:02:26.245 Info App: Bitrate exceeds DirectStream limit: media bitrate: 10366897, max bitrate: 4000000

The emby server log

embyserver(.73).txt

The android app log (3.1.73) (IP addresses removed) REMOVED MY ANDROID LOG FOR PRIVACY

 

I will continue using version 3.1.23 for now.

My emby server was on a freenas jail on the same subnet. I have recently moved embyserver in to a DMZ zone and rebuilt my server. Embyserver now runs on OpenMediaVault(Debian) in a docker container.

Edited by embyben
Link to comment
Share on other sites

I have investigated further  and confirmed the issue is with the emby app since version 3.1.59

I have reproduced the error and provided details and (fresh) logs in this post..

You can delete this thread.

Edited by embyben
Link to comment
Share on other sites

Confirmed issue is also in

  • version 3.1.71
  • version 3.1.69
  • version 3.1.64
  • version 3.1.59

1080p movies play fine on version 3.1.23

Edited by embyben
Link to comment
Share on other sites

Hi, have you looked at your logs?

You have a ton of errors in them you need to address.

java.security.cert.CertPathValidatorException: Trust anchor for certification path not found.

Fri Jan 22 07:02:24 GMT+08:00 2021 Error sending request to http://172.17.0.3:8096/emby/system/info/public?format=json: failed to connect to /172.17.0.3 (port 8096) from /192.168.188.66 (port 39950) after 10000ms

etc

You need to validate your cert is valid/not expired and still working properly.
Test this in a web browser

Does Emby show a remote address in the Dashboard view using the secured port?

Let us know what you find.

Link to comment
Share on other sites

23 hours ago, cayars said:

Hi, have you looked at your logs?

You have a ton of errors in them you need to address.

java.security.cert.CertPathValidatorException: Trust anchor for certification path not found.

Fri Jan 22 07:02:24 GMT+08:00 2021 Error sending request to http://172.17.0.3:8096/emby/system/info/public?format=json: failed to connect to /172.17.0.3 (port 8096) from /192.168.188.66 (port 39950) after 10000ms

etc

You need to validate your cert is valid/not expired and still working properly.
Test this in a web browser

Does Emby show a remote address in the Dashboard view using the secured port?

Let us know what you find.

172.17.0.3 is an IP address that docker uses when I used to use a bridge network and I have specified a new docker network which is 10.10.10.130.

Running on HTTP port 8096, and HTTPS port 8920.

In-Home (LAN) access: http://10.10.10.130

My docker run file is

docker network create -d macvlan -o parent=eno1 \
  --subnet 10.10.10.0/24 \
  --gateway 10.10.10.1 \
  mynet

docker run -d \
    --name emby \
    --device /dev/dri:/dev/dri \
    --network mynet \
    --ip 10.10.10.130 \
    -p 8096:8096 \
    -p 8920:8920 \
    -e UID=1000 \
    -e GID=100 \
    -v /srv/dev-disk-by-uuid-832de4f2-73ac-400a-b84b-f1abfa3e27ac/config/emby:/config \
    -v /srv/8dfcfa9c-f641-412b-843f-606afffd9344/media:/media \
    --restart unless-stopped \
    emby/embyserver:latest

 

Link to comment
Share on other sites

I'd review your docker or networking setup.
Emby should never see this"bridged address" if things are working correctly.
Have you tried using a normal NAT address?

I can't be of help in this as I don't run Docker but prefer to run Emby natively,

Link to comment
Share on other sites

@Luke@cayars
I have reinstalled latest Android app 3.1.73.

Connected to my embysever over HTTP on LAN. 1080p movies play.

I turned off my wifi to switch to cellular and connected over HTTPS. The original error reoccurs.

My android log is attached (with IP and domain names removed).

4deab63d-0497-4e98-9153-848639a03a6a.log

 

Edited by embyben
Link to comment
Share on other sites

I can connect remotely via the Android app on version 3.1.23 and play ALL media fine.

However, when i use Android app version 3.1.73 I can't play all media. Not even my music files will play.

In this log I have

  1. cleared my log files on my android phone
  2.  opened the emby app over cellular
  3.  connected to my server fine
  4.  opened a low definition movie which seems to be working fine.
  5.  movie plays
  6.  closed the movie
  7.  attempt to play a song in the Music library.
  8.  nothing plays after a long wait.

I've also removed my IP and Domain name from the log.

51d7206a-8f33-43da-b9e8-7e7dcd487506.log

i can see in the log file that there are attempts to connect over the non-SSL port/url

Fri Jan 29 07:50:44 GMT+08:00 2021 Error sending request to http://10.10.10.130:8096/emby/system/info/public?format=json: failed to connect to /10.10.10.130 (port 8096) from /10.250.44.204 (port 43172) after 10000ms

I'm not sure why it would do this over a remote connection.

 

My current SSL setup is with Cloudflare. I'll attempt the LetsEncrypt method this weekend to see if there is any difference.

Link to comment
Share on other sites

You can't connect via SSL to IP 10.10.10.130  in anything resembling a normal setup.

SSL requires a domain name and that will almost always point to a public IP address.  The 10.x range are private IPs

So this appears to be used IN LAN.  In that case don't log into your domain (without loop back in your router) and instead use the LOCAL IP address shown in the web console.

 

Link to comment
Share on other sites

2 hours ago, embyben said:

I can connect remotely via the Android app on version 3.1.23 and play ALL media fine.

However, when i use Android app version 3.1.73 I can't play all media. Not even my music files will play.

In this log I have

  1. cleared my log files on my android phone
  2.  opened the emby app over cellular
  3.  connected to my server fine
  4.  opened a low definition movie which seems to be working fine.
  5.  movie plays
  6.  closed the movie
  7.  attempt to play a song in the Music library.
  8.  nothing plays after a long wait.

I've also removed my IP and Domain name from the log.

51d7206a-8f33-43da-b9e8-7e7dcd487506.log 32.84 kB · 0 downloads

i can see in the log file that there are attempts to connect over the non-SSL port/url

Fri Jan 29 07:50:44 GMT+08:00 2021 Error sending request to http://10.10.10.130:8096/emby/system/info/public?format=json: failed to connect to /10.10.10.130 (port 8096) from /10.250.44.204 (port 43172) after 10000ms

I'm not sure why it would do this over a remote connection.

 

My current SSL setup is with Cloudflare. I'll attempt the LetsEncrypt method this weekend to see if there is any difference.

Just so we are clear, you can play on the older version because we were embedding a different video player, and we had it configured to blindly ignore all ssl problems. The player we're embedding now is a little more strict where it wants you to do things a little more by the book. We'll look into what flexibility we may have with that, but both of you are right in what you are saying. Yes you were able to play in the older version, but cayars is also right that what you are trying to do is far out of the norm.

  • Like 1
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...