Playback Error No compatible streams are currently available.

[therealtobo 0]

Hi everyone,

Yesterday I realized that remote playback wasn't working anymore. I've been fiddling around with this today and have some more information regarding this. I don't know exactly when this started as I very rarely use remote playback. So, connecting to the server remotely is fine, login works etc. But when I try to start a movie I get the following error message:

Playback Error
No compatible streams are currently available. Please try again later or contact your system administrator for details. 

After some testing i realized that playback works if I go towards the internal address 192.168.x.y but not when using emby.mydomain.com. I haven't changed anything in nginx lately and I haven't fiddled with any server settings in Emby either. I've tried upgrading to 4.6.7.0 without any change in behavior. 

Ubuntu: 20.04.3

Emby: 4.6.7.0

I've attached a log from when clicking play until the error message appears.

 

Playback Errodebug log.txtr

No compatible streams are currently available. Please try again later or contact your system administrator for details.

[Luke 42079]

Hi there @therealtobo can you please attach the complete emby server log? Thanks.

[therealtobo 0]

Hi @Luke, sure thing, I'll upload tomorrow!

Thanks!

[therealtobo 0]

@Luke I took care of it straight away instead. The following file is the complete file and i restarted the server before testing to keep it smaller. This is the sequence tested:

1. Started server.

2. Tried playback using remote FQDN, did not work.

3. Tried playback of the same movie using local 192.168 adress, worked.

embyserver.txt

Edited December 13, 2021 by therealtobo

[therealtobo 0]

Some more notes:

1. For the failed playbacks i get no ffmpeg log
2. Using the android app on my phone I can replicate this. Running on the same wlan, playback works. Running on cell network, playback gets the same error message.

 

[therealtobo 0]

@LukeI wonder if something has changed in the backend (letsencrypt, nginx, similar), I started fiddling with the nginx-conf anyways since that seemed to be the logical option and I found someone who talked about getting the same error because of nginx conf even though it was a long time ago. I'll try to add line after line to the configuration and see what is causing this but for now it might actually be solved. By tracking down a "faulty line" I'm also hoping to understand what has actually happened.

[therealtobo 0]

It was this pesky little line below that wasn't in the original guide (since I haven't edited it since starting to use emby). I think it all works now but need to do more testing. Has something changed recently in nginx/emby which made that line necessary and I missed it?

 proxy_buffering off;

Found the line in this updated nginx example: 

 

[Luke 42079]

Thanks for the feedback.