fast forward hangs and kills my docker containers

[brintal 0]

I'm running emby  4.7.0.19 (also tried 4.7.0.30 and  4.6.7.0) as docker on UNRAID 6.9.2.

I have a weird issue with emby hanging when fast forwarding on my chrome cast with google tv. By fast forwarding, I mean pressing the "arrow right" button and keeping it pressed. Emby will then forward the movie until I release the button and play from that position. The problem is, after releasing the fast forward button, emby hangs (=movie does not play, I can still go back to the menu) for a long time, ranging from a few seconds up to couple minutes! Same thing happens if I try to fast rewind (pressing and holding the left arrow on the remote)

Some observations:

• If I go back to the menu while it hangs and play the movie again from the last position (play from xxx) everything works and it will play immediately. So it's actually much faster to do that than to wait for emby to finish hanging.
• If I use the "chapter selection" (arrow up) to move around the movie everything works fine. no hanging.
• If I use single key presses (not pressing and holding) on the left/right arrows to move around, everything works mostly fine. If I press multiple times very fast after each other, sometimes it will hang a bit.
• The Web Client and the Android App both work fine and have no problem whatsoever. But they also do not really have this fast forward feature. But moving to any position in the movie works fine and the movie plays immediately.
• While the movie hangs (after I released the button until the movie continues playing) there is quite a high load on my server. CPU is very busy and I noticed that the docker.img file (where unraid stores its docker containers) grows and gives me alerts about it. This also sometimes results in some other docker containers dying if docker.img completely runs out of space.
• If I wait out the hang, I can then fast forward/rewind in THIS movie without further hanging as many times as I want. If I go back to the menu and reopen the movie, the first fast forward/rewind will hang again.
• On my old server with emby docker 4.7.0.19 this was working fine (same chromecast). Hence it doesn't seem to be client-related.

So I guess the question is what emby is trying to do while fast forwarding? Why does it make a difference if I select a position using chapter select or via fast forward? 
Maybe emby is trying to show some kind of animation while fast forwarding and my PC struggles with that?
Is it possible to configure emby somehow to not do anything while fast forwarding except move to the new position? I don't really need any animation.

[brintal 0]

I'm attaching some log files from my last test. Opening new movie, fast forwarding and observing the hanging. Then rewinding the same movie (without going to the menu) and observing that in that case the movie continues immediately.

Executed steps (approximated timestamps):

19:39:00    started to play movie from beginning   
19:39:10    pressing right arrow (fast forward) button
19:39:20    released button
<- movie hangs ->
19:41:07   movie continues playing

19:41:30    pressing left arrow (fast rewind)
19:41:40    released button
<- movie continues immediately->

ffmpeg-directstream-04651f7b-c2e0-472a-837c-5969130bd0f6_1.txt ffmpeg-directstream-9f840d44-553c-4e1e-b91e-ab8e4155f8b7_1.txt embyserver.txt

[brintal 0]

Ok I just discovered that it is somehow related to the reverse proxy I'm using, which makes this issue even more weird. If I go directly to my emby server without TLS via reverse proxy, everything is working fine. Fast forward works, no crazy server load, no dying containers.

I'm using Nginx Proxy Manager with a default config for emby. So probably something is missing there. Is there somewhere an example config for Ngxing Proxy Manager that I can use as reference?

[Luke 42085]

HI, I don't know about ngxing proxy manager, but I would strongly suggest checking out @pir8radio's nginx configuration:

 

[pir8radio 1312]

10 hours ago, brintal said:

Ok I just discovered that it is somehow related to the reverse proxy I'm using, which makes this issue even more weird. If I go directly to my emby server without TLS via reverse proxy, everything is working fine. Fast forward works, no crazy server load, no dying containers.

I'm using Nginx Proxy Manager with a default config for emby. So probably something is missing there. Is there somewhere an example config for Ngxing Proxy Manager that I can use as reference?

is it using subdomain or subdirectory?        emby.domain.com   or domain.com/emby      the first is the error free way to go,  you can get most things correct with the second, but you will find some things still don't work.     proxy manager is horrible too.   lol  thats just me, i hate it writing configs for me.    it spews configs into like 5 different chunks and makes it hard to follow yourself.      Like they want to force you to use their GUI, by making the configs into rocket science.. 

 

[brintal 0]

Thank you @Luke and @pir8radio.

I'm trying to figure out how to write nginx configs. Because I have no clue about nginx (coming from apache2...) I actually like Nginx Proxy Manager as most of the stuff works out of the box. Even most of emby works. Hence I would prefer to figure out which setting is missing and causing the issues described above. Does anyone of you know which nginx settins might be responsible?

Edit: I'm using subdomains. No subdirectories.

Edited March 16, 2022 by brintal

[Luke 42085]

On 3/16/2022 at 5:34 PM, brintal said:

Thank you @Luke and @pir8radio.

I'm trying to figure out how to write nginx configs. Because I have no clue about nginx (coming from apache2...) I actually like Nginx Proxy Manager as most of the stuff works out of the box. Even most of emby works. Hence I would prefer to figure out which setting is missing and causing the issues described above. Does anyone of you know which nginx settins might be responsible?

Edit: I'm using subdomains. No subdirectories.

How have you configured it so far?

[pir8radio 1312]

On 3/16/2022 at 4:34 PM, brintal said:

Thank you @Luke and @pir8radio.

I'm trying to figure out how to write nginx configs. Because I have no clue about nginx (coming from apache2...) I actually like Nginx Proxy Manager as most of the stuff works out of the box. Even most of emby works. Hence I would prefer to figure out which setting is missing and causing the issues described above. Does anyone of you know which nginx settins might be responsible?

Edit: I'm using subdomains. No subdirectories.

first guess, probably the couple range headers.