Anything changed with certificate and/or Brave browser?

Hi.
I noticed that I cannot access Plex installed on my NAS from my Android app, neither does it play back anything when connecting from Brave browser. The certificate from Letsencrypt is somewhat strange (has a strange/non-existing domain like “plex.direct”) - did something change?
In Firefox I had also to accept the security issue, but then at least I was able to stream again my videos…

Thanks for any help!
F.

Plex Media Server version & platform?

Plex Android app version & platform?

Available via Authorized Devices.

Plex.direct is a very legitimate domain. It is necessary if you want secure connections to work. Here are the technical details: How to Use Secure Server Connections | Plex Support

The “security issue” only occurs when you use the local version of the web app. Which is not loaded via https.
Work around that by using the hosted version from https://app.plex.tv

By using Brave browser, you need to keep in mind that you are using a browser which has been kneecapped. It’s like intentionally blinding yourself, but blaming your optician that you cannot see correctly.

I’m running my Plex Media Server off of a Synology DS218+ with the latest DSM version DSM 6.2.4-25556 Update 2
The Plex Media Server version is 1.18.5.2309-f5213a238
The Plex Android app version is 8.23.1.28053

The issue is affecting my Android app both from inside my home network, as well as from outside. I’m using a Let’s Encrypt certificate on my Fortigate firewall to secure the https connections to my Synology NAS, both for management, as well as for Plex access.
The issue started happening out of nowhere.

Any help would be appreciated.
Thanks!

OK, I tried with Firefox inside my home network.
I entered the URL https://myfqdn-nas.synology.me:32400/web
Firefox is complaining about invalid certificate, because HSTS is in place: the certificate is valid for *.some-weird-string.plex.direct

Could it be that a Synology NAS firmware upgrade started enforcing HSTS and now I’m getting issues? This is actually strange, because I upgraded the NAS 19 days ago and the issue appeared only last week…

PMS 1.18 is over a year old. It has problems with the current Plex Android apps.

Update to a current PMS release.

The version supplied by Synology is out of date. Download the current version from plex.tv and perform a manual update.

1 Like

This will never work, because you are requesting an encrypted connection (https) with a domain name which doesn’t have a cryptographic certificate attached to it.

To access your Plex server always use either https://app.plex.tv
or in the local network
http://ip_of_your_nas:32400/web

Or get a proper (i.e. publicly trusted, not self-signed) certificate for your custom domain name.

Of course my FQDN is not “myfqdn-nas.synology.me” - I don’t want to share my FQDN here in this forum, but I can guarantee that I do have a valid SSL certificate (Let’s Encrypt).
Of course with the IP and without SSL, it works - so @FordGuy61 is right pointing at the incompatibility between PMS 1.18 and the actual Android app.

So I manually upgraded to the latest 1.24.3.5033-6000 and in fact now my Android app works again!
So one thing is fixed.
Now, when I try accessing the URL on port :32400/web (via http), it redirects me to https and then fails because of HSTS.
Any solution to this?

Glad your Android apps are working again.

I’ll defer to others on the other issue. My comment was strictly in regard to the Android problem, and I use app.plex.tv, not a personal domain name, when accessing my server via Plex Web.

Well, now that I think about it: when I’m abroad on another computer, I just use plex.tv and log in there and I can reach my PMS…
I think it’s a non-issue the one related to the URL:32400/web URI… but maybe somebody knows how to fix that as well…
Thanks so far!

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