Open zmike808 opened 5 years ago
hello will it work with apps?
I would also like to know - being able to configure this would make a big difference for me as I have limited bandwidth for Plex.
@zmike808 if you have some more information on those evil headers I'd be interested in seeing it
I would also like to know - being able to configure this would make a big difference for me as I have limited bandwidth for Plex.
@zmike808 if you have some more information on those evil headers I'd be interested in seeing it
@dippynark take a look here: https://github.com/zmike808/Plex-Blackmagic just uploaded my cloudflare worker script that handles the headers I mentioned.
Heads up to anyone still using this. forceAutoAdjustQuality has been countered by some really dark black magic. It 100% no longer works on plex.tv, which is really themost magical part. I went back to server version 1.13.8.5388 a month or 2 ago and I can confirm it will work on your direct domain such as plex.whyplexgottabelikethat.tears. But, like I said, that defeats the original purpose of this magical hidden setting, since it allowed friends you shared with to not have to herp derp at 2mbps default for their enitre lives. I have identified what is countering this magic however, I haven't had the time to deep dive into an attempted fix. It has to do with new headers being sent from plex.tv web clients. So, if anyone is interested in trying to fix it hit me up and I'd be willing to show you the evil headers in question. I have a general idea of how this may be fixable, but it would require having osme sort of middlelayer between plex.tv and the connection to the server maybe. I tried some basic things with nginx which yielded no results.
TL;DR: Once again plex pulls a plex and dicks dedicated plex users for absolutely no reason. But for not my brethren, all hope has not been lost (yet)