Plex Server crashing after google chrome update 98.0.4758.81(Official Build) (64 bit)

Plex Media Server
1

Server Version#: 1.25.4.5487
Player Version#: Not sure where to find this
Today I had a Google Chrome update version 98.0.4758.81 and since then whenever i try to play a video file on my Plex Server i get a blank screen with a message " Aw, Snap! Something went wrong while displaying this web page error code STATUS_BREAKPOINT
I started Plex on my Laptop and all was fine until Google Chrome Updated to the new version then the error was happenng on my Laptop aswell.
Can someone help with this ?
Cheers
Heich

11 Likes
2

Im having the same problem, also microsoft edge, but can watch the videos in Firefox thought. Its the update with 98.

3

Same problem - have all the latest updates for windows 11 and Chrome. No luck finding a solution yet.

4

Same thing here. Started a few days ago. Same version of Chrome and Plex. Usually happens a few seconds in, but some videos will play normally and some just take a little longer. Not consistent.

5

I too have this issue. Tried everything from local side, thinking it was something going on with the NAS, computer, files etc.

After many hours of testing, nothing i seemed to do helped. I will say the videos played fine on my phone and through Firefox. As a last resort, came here to see if there was something going on with the status code and yep, Chrome updated recently and that’s what’s going on.

6

I have contacted Google Chrome support about the issue but no reply or fix yet still waiting on Plex support for a reply!
I don’t know if this helps but I’m using Plex on a WD Mycloud EX2 Ultra and last night I rebooted the server, this morning it appears to be more stable, I was able to play at least 5 videos that I wasn’t able to play yesterday so i’m keeping an eye on it to see if it’s stable or a random thing.
Cheers

7

Hi all. Bad news i just tried Plex again and was only able to play 2 videos before the Aw, Snap! issue reared it’s ugly head again! So it’s a completely random thing.
Cheers

8

Hi All, Today I was editing some files in Plex Server when I got the Aw,Snap! window this time i wasn’t playing a video I was just generally editing some Video information when it happened. I hope Plex is looking into this situation 'cos it’s getting a bit frustrating having to log out and in again to use the server.
Cheers

9

Windows 10
Chrome update 98
Plex server 1.25.4.5487

Getting the same “AW, Snap!” “status_breakout” error while trying to stream music through the browser.

I cleared my cache and cookies, it helped for a few minutes. But it is back to crashing whenever I hit play on the music.

10

Same problem here. Started for me last night.

11

Also affects Chrome Version 98.0.4758.82 (Official Build) (64-bit)

12

“does not support SDES key exchange mechanisms from WebRTC”
“Lighthouse has been updated to version 9”
“U2F API decommission”

So there are big things changing, especially for backend code. I wonder which ones affect Plex web client. Lighthouse or WebRTC?

Takeaway #1 Connect to your PMS locally, instead of through app.plex.tv and it solves the problem. So it may seem this is a WebRTC or U2F issue specifically within the Plex web service provided to proxy through to our media system. I leave it up to the Plex developers to know why, but I offer this as a troubleshooting step.

Starting articles


13

There are numerous reports of this issue all over the web.

So it is clearly not an isolated incident.

This needs to be escalated for a fix immediately.

3 Likes
14

Error code: STATUS_BREAKPOINT (see images below)

Plex Media Server Version 1.25.5.5492 running on Ubuntu 20.04.3 LTS x86_64, although i suspect this is a browser / client issue. Will try on streaming devices and report back, thanks. Media file works fine in VLC.

Experiencing identical issue(s) on multiple browsers. Please advise @ChuckPa sir? Thank you for your time and expertise.

Brave browser: Version 1.35.101 Chromium: 98.0.4758.87 (Official Build) (64-bit)
image

M$ IE Edge Chromium: Version 98.0.1108.50 (Official build) (64-bit)
image

EDIT: Same above error on latest Brave under Windows 11, however, i was successful on M$ Edge Chromium Version 98.0.1108.50 (Official build) (64-bit) under the same Windows 11 machine. YMMV. Mobile Android app works fine on my phone, as well as streaming devices (Google TV, Roku).

15

Same issue on all browsers I use. I did fix it on one pc that was watching The Waltons by clearing all you browsing history but all the rest of the pc’s have the Error code: STATUS_BREAKPOINT. Man its only on some videos. I could watch The shield but not Lord of the Rings.

16

I am also experiencing this issue across multiple computers and multiple Plex Servers.

17

It’s a Chromium issue. Reverting to the previous version of whatever chromium-based browser you use should fix it.

Chromium browsers:
Chrome
Edge
Brave
Opera
etc


1 Like
18

I had the same crash problem with Chrome, Edge & Firefox.
Opera browser works perfectly though, cast is not a problem

19

These browsers all use Chromium WebKit. Its some incompatibility with what Plex WebUI uses and Chrome 98 updates. I suspect Plex needs to fix their software to conform to these changes.

Firefox loads fine.
Loading Plex WebUI directly from server, and NOT from app.plex.tv also works fine from Chromium.

2 Likes
20

Not absolutely sure yet that it’ll fix the problem (just tried the setting myself), but you could try to set a registry key for Google Chrome (the equivalent key exists for Edge) :

  • Run ‘regedit’ to open windows registry (If permission issue came then run that command with Admin command prompt)
  • Go to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome
  • Create new DWORD value with “InsecurePrivateNetworkRequestsAllowed” Name
  • Change Value to “1”
  • Restart your Browser

Sources : javascript - Chrome 98 Private Network Access problem w/ disabled web security: Request had no target IP address space, yet the resource is in address space local - Stack Overflow
Chrome Enterprise release notes - Chrome Enterprise and Education Help (Private network access preflights for subresources)

At my job we also had a problem with this Chrome version :
Chrome sends a CORS preflight request ahead of any private network requests for subresources, asking for explicit permission from the target server. This request carries a new Access-Control-Request-Private-Network: true header, and the response must carry a matching Access-Control-Allow-Private-Network: true header.

1 Like