Plex playback fails on Chrome/Chromium Edge

Plex Players Desktop Players
1

Server Version#: 1.18.4.2171
Player Version#: Chrome 80.0.3987.87 / Chromium Edge 80.0.361.48

I’m having some weird issues with Chrome.

I have a remote server available on my local network, call it 192.168.1.2

  • If I navigate directly to the server via Firefox (https://192.168.1.2:32400), playback is fine
  • If I navigate directly to the server via the Plex Android app, playback is fine
  • If I navigate directly to the server via Chrome/Chromium Edge (version above), playback reports “There was an unexpected error during playback”, and I get the following in the browser console:

chunk-2-e162212ebcf8fdffcb8f-plex-4.12.3-3f7851c.js:123 Error: Loading chunk 8 failed.
(error: https://192.168.1.2:32400/web/js/chunk-8-37d8f348b582502ba27b-plex-4.12.3-3f7851c.js)
at HTMLScriptElement.u (index.html:44)
po @ chunk-2-e162212ebcf8fdffcb8f-plex-4.12.3-3f7851c.js:123
chunk-2-e162212ebcf8fdffcb8f-plex-4.12.3-3f7851c.js:140 Error: Loading chunk 8 failed.(error: https://192.168.1.2:32400/web/js/chunk-8-37d8f348b582502ba27b-plex-4.12.3-3f7851c.js) at HTMLScriptElement.u (https://192.168.1.2:32400/web/index.html:44:1219)

Now, here’s where it gets weirder: if I run and access a local server (http://127.0.0.1:32400 - no TLS), and then stream content from my server at 192.168.1.2, there are no issues from Chrome or any other browser.

The only thing I can think of is TLS - the Plex CA is not trusted by my browser, and it throws a warning when I access the site (which I accept). Does anyone else have any suggestions?

The remote server is running the plexinc/pms-docker image with podman and systemd, if that helps. Given playback works on at least some devices this doesn’t seem to be the issue.

Thanks

2

Same issue here. Chrome has gotten very picky about TLS certs and hitting my box via the internal FQDN in Chrome results in an inability to do any playback. If I use another browser or plex.tv/web, it works fine. It would be nice if you could add Subject Alternative Names to the Plex-issued certs to avoid these problems.

3

Glad to know it’s not just me :slight_smile:

I’m just going to roll my own certs with all the v3 extensions that Chrome requires now (SAN, etc). I’ll update this ticket if it resolves things with Chrome.

Thanks again.

1 Like
4

The other workaround (which is lame) is to go HTTP instead of HTTPS. Not idea, but it’s easier for the lazy than having to get proper certs issued and installed.

6

That’s awesome, thanks for sharing :slight_smile: I didn’t realise https://plex.tv/web/app was an option…

7

I am dealing with this idiocy too. The last update really caused a couple of stability problems on my end. The Transcoder was locking up so hard I could not kill it manually in win 10 (Corp edition). I had to reset the server every day for 3 days, sometimes twice a day. I think the x86 build is bunked right now, and this makes it rather…Frustrating. Hope this gets sorted soonish. I love plex but man it can be super frustrating at times.

8

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.