Playback error no compatible stream found error

[Kaizac 0]

I've gotten this error a lot when playing from my browser, and the strange thing is that Plex does play these same files. So I just downloaded my logs (Embyserver log and playback log). And while browsing through the logs I found this snippet:

 

 

2018-11-26 16:34:14.860 Info App: Profile: Unknown Profile, No direct play profiles found for Path: /unionfs/Gdrive/Films/Captain America The First Avenger (2011)/Captain America The First Avenger (2011).mkv

 

Which is weird, since the .mkv isn't in the sub folder but directly in Films/Captain America. So it's looking one layer too deep, which doesn't exist.

 

I've attached the full logs. Hopefully someone has a clue on what I need to change.

Edited November 27, 2018 by Kaizac

[Luke 42079]

Hi, the log is filled with permissions errors:

	System.UnauthorizedAccessException: Access to the path '/unionfs/Gdrive/Series/One Piece/One Piece - 1x49 -.nfo' is denied. ---> System.IO.IOException: Permission denied

Maybe that is related?

[Kaizac 0]

Hi, the log is filled with permissions errors:

	System.UnauthorizedAccessException: Access to the path '/unionfs/Gdrive/Series/One Piece/One Piece - 1x49 -.nfo' is denied. ---> System.IO.IOException: Permission denied

Maybe that is related?

Thanks for responding. I don't think this is it, since it's only for this specific item which doesn't exist anymore. I've tested with another docker (Im on Unraid) and it also gives the same problems. It seems I can play items from my browser from my direct docker internal IP. But when I go to my external domain to access Emby it doesn't work anymore and it throws up the error.

 

Strangely through the app it does work..... I'm really lost here. I really want to jump in on Emby and get the premier but this is just breaking a big part I want to use it for. Would other logs help solving this issue? Should I try some other settings?

[Luke 42079]

Right but that is just one example. There are many more all throughout the log.

[Luke 42079]

Since this is a new install, can you try the beta version and see how that compares? Thanks.

[Kaizac 0]

Since this is a new install, can you try the beta version and see how that compares? Thanks.

Just installed the beta version and tried it. Internal IP works again, but external domain doesn't. Maybe I have some lets encrypt/nginx settings wrong? Which is still weird since the app works flawless on the external domain from outside my network.

[Luke 42079]

I would make sure that nginx isn't stripping off any http request headers, or modifying the responses.

[Kaizac 0]

I would make sure that nginx isn't stripping off any http request headers, or modifying the responses.

 

Thanks for the tip, this seems to have solved it. I tried to harden my NGINX config too much for Emby which probably caused the problems. So far I've been able to stream from my browser through my domain. And now I'm a happy Premier user. Thanks again for the support.

 

For people reading this with the same problem. This is my NGINX/Lets Encrypt config for Emby. Might not be the best, but it works and should be quite secure.

server {
    listen 80;
    server_name emby.*;
    return 301 https://$server_name$request_uri;
    }

server {
    listen 443 ssl;

    server_name emby.*;

    send_timeout 100m; #Some players don't reopen a socket and playback stops totally instead of resuming after an extended pause (e.g. Chrome)

    #Faster resolving, improves stapling time. Timeout and nameservers may need to be adjusted for your location Google's have been used here.
    resolver 8.8.4.4 8.8.8.8 valid=300s;
    resolver_timeout 10s;

    #Use letsencrypt.org to get a free and trusted ssl certificate
    ssl_certificate /config/keys/letsencrypt/fullchain.pem;
    ssl_certificate_key /config/keys/letsencrypt/privkey.pem;

    ssl_protocols TLSv1.1 TLSv1.2;
    ssl_prefer_server_ciphers on;
    #Intentionally not hardened for security for player support and encryption video streams has a lot of overhead with something like AES-256-GCM-SHA384.
    ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:ECDHE-RSA-DES-CBC3-SHA:ECDHE-ECDSA-DES-CBC3-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA';
    
    #Why this is important: https://blog.cloudflare.com/ocsp-stapling-how-cloudflare-just-made-ssl-30/
    ssl_stapling on;
    ssl_stapling_verify on;
    #For letsencrypt.org you can get your chain like this: https://esham.io/2016/01/ocsp-stapling
    ssl_trusted_certificate /config/keys/letsencrypt/chain.pem;

    #Reuse ssl sessions, avoids unnecessary handshakes
    #Turning this on will increase performance, but at the cost of security. Read below before making a choice.
    #https://github.com/mozilla/server-side-tls/issues/135
    #https://wiki.mozilla.org/Security/Server_Side_TLS#TLS_tickets_.28RFC_5077.29
    #ssl_session_tickets on;
    ssl_session_tickets off;

    #Use: openssl dhparam -out dhparam.pem 2048 - 4096 is better but for overhead reasons 2048 is enough for Emby.
    ssl_dhparam /config/nginx/dhparams.pem;
    ssl_ecdh_curve secp384r1;

    #Emby has A LOT of javascript, xml and html. This helps a lot, but if it causes playback issues with devices turn it off. (Haven't encountered any yet)
    gzip on;
    gzip_vary on;
    gzip_min_length 1000;
    gzip_proxied any;
    gzip_types text/plain text/css text/xml application/xml text/javascript application/x-javascript image/svg+xml;
    gzip_disable "MSIE [1-6]\.";

    #Nginx default client_max_body_size is 1MB, which breaks Camera Upload feature from the phones.
    #Increasing the limit fixes the issue. Anyhow, if 4K videos are expected to be uploaded, the size might need to be increased even more
    client_max_body_size 0;

    #Forward real ip and host to Emby
    proxy_set_header Host $host;

    add_header X-Robots-Tag none;
    add_header Strict-Transport-Security 'max-age=31536000; includeSubDomains; preload';
    add_header X-XSS-Protection "1; mode=block";
    add_header X-Frame-Options SAMEORIGIN;
    add_header X-Content-Type-Options nosniff;
    
    location / {
#        auth_basic "Restricted";
#        auth_basic_user_file /config/nginx/.htpasswd;
        include /config/nginx/proxy.conf;
        proxy_pass http://10.0.0.60:8096;
        proxy_redirect off;
        proxy_buffering off;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    }
}

[Luke 42079]

Thanks for the feedback and the nginx config !