Local Plex access via Chrome not working

Plex Media Server Desktops & Laptops
1

Server Version#: 1.18.6.2368
Player Version#: 4.20.2

Using chrome I attempt to access my local plex server via “https://ipaddress:32400/web” and I am unable to access the site, but functionality is very broken, and I am unable to play anything. I checked the logs and receive this error. Everything works fine in Edge, and I haven’t tested FireFox. Any ideas?

> Feb 09, 2020 12:22:50.330 [7332] DEBUG - CERT: incomplete TLS handshake: sslv3 alert certificate unknown
> Feb 09, 2020 12:22:50.330 [7332] DEBUG - CERT: incomplete TLS handshake: sslv3 alert certificate unknown
> Feb 09, 2020 12:22:50.331 [7396] DEBUG - CERT: incomplete TLS handshake: sslv3 alert certificate unknown
> Feb 09, 2020 12:22:50.331 [7332] DEBUG - CERT: incomplete TLS handshake: sslv3 alert certificate unknown
> Feb 09, 2020 12:22:50.334 [7396] DEBUG - CERT: incomplete TLS handshake: sslv3 alert certificate unknown
> Feb 09, 2020 12:22:50.334 [7332] DEBUG - CERT: incomplete TLS handshake: sslv3 alert certificate unknown
> Feb 09, 2020 12:22:50.334 [7396] DEBUG - CERT: incomplete TLS handshake: sslv3 alert certificate unknown
> Feb 09, 2020 12:22:50.334 [7396] DEBUG - CERT: incomplete TLS handshake: sslv3 alert certificate unknown
> Feb 09, 2020 12:22:50.335 [7332] DEBUG - CERT: incomplete TLS handshake: sslv3 alert certificate unknown
> Feb 09, 2020 12:22:50.337 [7332] DEBUG - CERT: incomplete TLS handshake: sslv3 alert certificate unknown
2

to the top

3

That would be “http://ipaddress:32400/web” (notice the missing s)
Because there is no fitting security certificate for an IP address. So encryption won’t be working.

Try using https://app.plex.tv instead

Most likely an issue with “DNS rebinding protection”.
https://support.plex.tv/articles/206225077-how-to-use-secure-server-connections#toc-4

1 Like
4

Not sure how it can be a DNS rebinding issue? I have Netgear Orbi not pfsense or some other kind of sophisticated routing equipment?

5

DNS rebinding protection comes nowadays also in regular routers.
The worst of these don’t provide a way to define the necessary exceptions, though.

6

I’m also having this issue, everything was working fine for me until the latest 2 releases. Doesn’t work locally in Chrome, but if I try remotely it works. I don’t accept that this is a DNS issue because as both myself and the original poster aren’t using any DNS, we are simply putting the https://IPADDRESS:32400. Not to mention, the router wouldn’t play any impact because it’s direct communication with the server being on the same subnet.

Even so, I can login and see everything on the server, I just can’t play anything.
I also can use other browsers and it works fine, it seems the latest player release was broken for Chrome for local secure playback. This isn’t a DNS issue, this is a player issue. A DNS issue would be universal to the browser, and require a domain name when accessing.

7

Please read the article I posted above. It explains that even in order to use the local plex server, you’ll be using the DNS system.

8

Did this change on the last few releases? Because this looks to be more of an issue with how Chrome handles SSL…

9

Encrypted communication is now always preferred in Plex, even within the local network.
Which necessitates the use of a FQDN for your local server, which sometimes can be spoiled by firewalls/ anti virus software and router firmware interfering.

10

I understand that but shouldn’t that be the case for all Browsers not just Chrome? I apologize for being ignorant but I am just not connecting the dots.

11

I cannot tell you the details. Apparently, each browser has a slightly different behaviour, if something doesn’t work like it’s supposed to.
The error messages you have shown above could either mean that there is no valid certificate at all
or only an “intermediate” certificate, which gets used by an anti virus software or a firewall (which isn’t “pinned” to the server’s FQDN and is therefore not accepted by the Plex app).

FIrs thing would be to check that everything is set up like it’s supposed to. And that includes to make sure that your router or DNS resolver isn’t throwing a spanner in the works.

12

So this issue will just be left unfixed? It worked fine 2 releases ago, but now everyone of us will need to change browsers because of this?

14

I have the same symptoms with Chorme (Version 80.0.3987.100 (Build officiel) (64 bits)) it’s work with Chromium (79) and Firefox (72.0.2 (64 bits)).

More informations about this issue : Dashboard not work correctly (stats not work), read music seem to work but video doesn’t…

I was updated PMS to Version 1.18.6.2368 today !

Thanks for your help.

15

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