Hi Thierry.plex, I just had a look in both laptop and desktop registry’s and could’nt find any Google\Chrome entry! 
Cheers
Hi Heich, try to create one, i hadn’t this key either (this is a new key)
Hi all, Today I checked the version of Chrome and it’s now 98.0.4758.102 the problem still persists and I also noticed that when I stop playback the video continues to play. I caught a screen of the video Playing.!!!
Chrome Version 98.0.4758.102
PMS Version 1.25.6.5545
Plex Web Player Version 4.74.2
Attempted to add missing “Chrome” key to “policies” folder and then added DWORD “InsecurePrivateNetworkRequestsAllowed” and set value to 1 in the newly created “Chrome” folder.
Restarted Chrome browser and although it played through the first episode perfectly, the next episode had the “aw snap!” error again.
Good find, just not a consistent fix.
Hi Sothis, I think you forgot the “Google” folder before the “Chrome” folder. I didn’t test enough yet to be sure it works.
The equivalent key for Edge is SOFTWARE\Policies\Microsoft\Edge\InsecurePrivateNetworkRequestsAllowed
But I think Plex developpers will soon fix the problem.
[UPDATE] Added “Google” folder as top folder in “policies” folder and added the “Chrome” folder underneath it and the DWORD entries “InsecurePrivateNetworkRequestsAllowed”, “InsecurePrivateNetworkRequestsAllowedForUrls” and set value to “1”, after reboot of computer it seems to be working.
Sorry for the false hope, I havn’t had any errors since I tried this setting but I didn’t played much music either.
My problems started around the same time that chrome updated. 98.0.4758.91 (Official Build) (64-bit)
Except i’m getting Aw, Snap SIGILL. It’s intermittent, but usually doesn’t take long…
The last chrome console message was
Did not move header "accept" to query string. This can result in an unnecessary OPTIONS preflight request.
The most common error is
Ensure CORS requests include credentials only when allowed
A cross-origin resource sharing (CORS) request was blocked because it was configured to include credentials but the Access-Control-Allow-Credentials response header of the request or the associated preflight request was not set to true.
To fix this issue, ensure that resources that expect credentialed CORS requests set the Access-Control-Allow-Credentials header to true. Note that this requires the Access-Control-Allow-Origin header to not be a wildcard *.
Me too.
Happens in Chrome, Brave and Edge. - (All based upon Chromium.)
Some said changing to private/incognito would solve the issue, but not for me.
Firefox works.
Opera Works.
Hi TurboMyPC, for my peace of mind, could you try the registry setting explained here ?
Don’t forget to restart the browser after setting the key.
I tested a little more yersterday without any errors and the logs you showed seems related to a CORS problem.
Same error. Both Chrome and Edge. Firefox works just fine.
Same error on Edge/Chrome/Chromium. Windows 10 and Ubuntu. Plex Server Version 1.25.5.5492 Plex Web Version 4.75.0
Same error here. Seems to have an intermittent element to the fault as well. Some of my media will consistently play while others consistently pop this error. Tested using two *.m4v files.
Also confirmed connecting locally does not cause the issue. Related to WebRTC or U2F issue mention earlier?
Hi All, I tried the registry hack today on Google Chrome and sofar it seems to be behaving. I will keep an eye on it just incase it Sheets itself again and let you all know. 
Cheers
InsecurePrivateNetworkRequestsAllowed
Sounds like something that would be advised to keep on for security sake, but applicable to my problem. Accessing Plex over https, but content is routing local.
I will try this, but I’m concerned using this as a permanent fix. For now I’m using the Android app with no issues.
You’re absolutely right, it’s not a setting to keep, you should just set it until a fix is released by Plex, and only if needed. A better key could be InsecurePrivateNetworkRequestsAllowedForUrls to limit the security hole, but I didn’t tried it.
I added the registry key and DWORD for MS Edge and it’s working for now. Been playing music and videos for a few hours now and no crash screen saying STATUS_BREAKPOINT. I left Chrome “as is” for now so I can tell when a proper fix has been applied. Thanks for this work around……D……
1 Like
What is taking so long to fix this problem? Seriously…
I wish I knew Bro! Looks like Plex support is us. Plex seems to be quick to take our subscription money but sooooo slow at giving us what we need “SUPPORT”
Just keep pushin the same questions and eventually someone from PLEX will answer.
Cheers
