No fix yet that I am aware of. Just this reg key work around for now which sounds like we have to create a potential vulnerability in our systems to get back the functionality we all had and pay for. I’m just baffled at Plex developers as to why after all this time they will not acknowledge this issue which has plagued so many users and what they are doing about it. I will have to re evaluate my decision next time my PlexPass comes up for renewal…seems to only affect connections through app.plex.tv. Direct connections to server are fine.
I get it!!
Both Microsoft and Google are enhancing security of their browsers to allow only authorized private server address connections from public web sites. I do not know why Plex has not kept pace with this to patch their servers to authorize the access. It is required for the functionality to work and the playback of files within browsers from our media servers.
We have lost this functionality for almost a month now and I know I used it quite allot. I do file editing and look up program data on the Internet and usually do all of the work in different tabs within one browser.
I really wish Plex would put a priority on this issue!!
… have a bug in their browser.
These upcoming security changes should NOT be affecting users or Plex yet.
It looks like Google is backing out some related breaking changes from the Chromium source. I don’t know when they’ll arrive in a Chrome release - maybe they’ve already landed in Canary/Developer/Beta.
https://chromium-review.googlesource.com/c/chromium/src/+/3465856
Though they kept the bug itself private. That’s interesting.
1 Like
Hello Volts…seems you were right and this was not a Plex issue….Sorry Plex!!
Both Chrome and Edge have now been updated and no more crashing playing video or audio files. All good….
2 Likes
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
