I can confirm that disabling this option leads to massive slower transfer speeds.
But at least now we have narrowed down the error and we have a workaround.
What the actual f***?! This actually works!
Downstream went down from solid 950 to 200-300 MBit/s, bummer. But at least we can get scanning the library working again.
Thanks for the workaround! Looks like our problem is some sort of QoS-issue in FritzOS.
@ChuckPa Oh boy I would love to talk to this guy again with the new information… 
Again: thanks to anyone involved in troubleshooting, digging in logs, talking for hours on the phone (lol), searching the web over and over again, etc.
Glad we found a solution/workaround for now.
This is sounding like a problem which occurred in a BETA pfSense firmware version once.
Hardware acceleration of the AES encryption – didn’t. As the direct result, everything slowed down.
This is a sleigh ride for sure. 
Can also confirm that this works (FRITZ!Box 6591 with FRITZ!OS 7.13).
Did anyone contact AVM regarding this issue yet?
@bwestpha Thank you very much for your work!
Funny thing is, that in my case (Fritzbox 6660) the problem is also fixed, BUT I did NOT change the setting for hardware acceleration. It is still activated (just checked to be sure)!
Might be a coincidence, but for me the problem fixed itself, when I activated remote access in plex and opened a port in my fritzbox for plex.
Would be funny if this was related to https://forum.openwrt.org/t/flow-offloading-hw-1-not-working-on-latest-trunk/ AVM is always too lazy updating Linux components in their firmware. Wouldn’t surprise me if lots of the Linux packages in current firmware are 2-3 years old.
A small update on this case from my side.
I opened up a support case at AVM for this issue and now we had some mails going around - but we are still at the point of exchanging support data of the AVM box with enabled and disabled acceleration settings etc.
This will take some time I think :S
@ChuckPa any ideas or more insights why this happens with plex but not (for example) with emby or when directly accessing this sites? Any chance this is related to pyhton 2.7 or some other http library of python?
2 Likes
Man, I was certain I screwed up my plex or something until I found this. Thanks!
I’m really hoping there will be a solution found as it’s kind of annoying that the work around slows down everything by a factor of 4. If you are communication with AVM maybe ask if it helps if more people report the same problem (to maybe elevate the importance) of if this just clogs the system.
Thank you
Still no updates from AVM so far. Tomorrow it’s a week without any message and I will ask for the current status.
I received feedback yesterday. Since yesterday there is a new lab FW which could possibly solve the problem. I should test it. I haven’t gotten around to it yet.
unfortunately the new lab version didn’t work for me. Only when I deactivate the hardware acceleration, the metadata can be retrieved correctly. The new checkbox for Layer-2 acceleration makes no difference.
I am sure that is the reason for many complaining with problems, cause it doesnt depend on Plex Software, it is just the ISP Connection. A VPN is the method to fix it. Thanks @bwestpha!!!
I thought that the problem fixed itself after I activated remote access for Plex. But no luck.
The problem returned.
So I also had to deactivate hardware acceleration in the fritzbox settings.
Now it works again. Download speeds seam to be unaffected.
Really hoping that AVM fixes this.
Update on this matter:
I installed the latest beta firmware for the fritzbox 6660 (7.14-76932). This is not an official „labor“ version, but you can find it with google ;-).
It looks like the problem is fixed with this beta firmware.
Metadata fetching in plex works even with hardware acceleration enabled.
Did not help over here. (running beta FW 07.14-76932 BETA) - posters, actors and stuff only load when hardware accl. is switched off…
but i’m qute sure the fritz box hasn’t been a problem some PMS versions back - feels like it is a problem with the latest and maybe the version before the latest one. (where can I get older versions?
This is strange…
I don’t have any problems since I installed the beta firmware on my 6660 two days ago (keeping fingers crossed).
To my knowledge only the two new DOCSIS 3.1 Cabel Boxes 6591 and 6660 are affected by this bug. 7.14 was the first version for the 6660. So there is no older version to test.
I don’t know about the 6591.
i meant an older version of Plex Media Server as I’m quite sure this worked before on my F!B 6660 one or two versions ago. (Running Plex on a QNAP x64 NAS)
1 Like
since 2 days i had also this Problem. You are amazing 
Messaged AVM 4 weeks ago. No response yet and I don’t think they will reply at all.
