Prevented fallback to insecure connection for

Plex Media Server Remote Access
1

Server Version#: 1.43.2.10687
Player Version#: app.plex.tv & Samsung TV
<If providing server logs please do NOT turn on verbose logging, only debug logging should be enabled>

Appearantly even though Remote Access says Green, and I can access the web portal remotely securely, but connections from apps doesn’t seem to be secure.

image
image371×298 9.88 KB

It doesn’t seem to be 429 error, as my Plex provided certificate renewed yesterday and is showing as valid. Don’t have any custom certificates installed.
Server is set to preferred, but I don’t think app.plex.tv allows fallback to insecure.

Certificate:
*.ee17.plex.direct**
**
Log:
[Connections] is unavailable at https://IP.ee17.plex.direct:32400/media/providers
[Connections] Prevented fallback to insecure connection for ",

Certificate is valid.
Issued On Wednesday, July 8, 2026 at 1:37:13 AM

Expires On Tuesday, October 6, 2026 at 1:37:12 AM

So what can I do to create a valid secure chain again?

2

Hmmm, the way i was simulating a remotrle connection on my guest wifi might have been throwing some stuff off. Have to test with a real remote conenction tommorrow.

3

app.plex.tv is showing as secure in the dashboard when being truly remote.
So guess I’ll have to troubelshoot client side why the Samsung TV isn’t connecting and keeps going to Relay.

4

Quite a few of these tips may actually apply to your situation: Client says it won't play from "remote server", although the server is local

5

It had something to do with the Samsung App settings due to a version upgrade.

Remote Quality was set to Unlimited, which after some tinkering dissapeared and the option Original came available in the menu.

Still very slow to load, slower then before the app update, but at least it’s connecting without transcoding again.