[SOLVED] Plex secure connection not possible

Server Version 1.19.3.2852:
Player Version 4.34.3:
Hello Plex Community,
Since the last Plex Server Update I have the problem that I can’t reach the server via the website “app.plex.tv” anymore. It is suddenly displayed to me as “insecure”.

Which I have already tried without success:

  • Log off Plex Server and log on again
  • Plex Server via apt install --reinstall "reinstalled
  • into my Fritzbox “plex.direkt” as allowed release for the DNS rebind protection
  • logs searched for common errors
  • Plex Server settings have not changed, so I can completely exclude this option

My plex server is only accessible locally and I want to keep it that way, but I would like to be able to continue using the “app.plex.tv” website.

I would be very happy about some help, because I can’t find the error.
Maybe one of you has an idea how to fix it.
I would like to avoid a complete reinstallation if possible, because the server is currently perfectly set up and the manual sorting of the categories took a lot of time.
My second Plex Server has not been updated yet (version 1.19.3.2843) There everything still works perfectly.

Could fix it with this:

OMG thank you so much! I was just searching Pi-Hole here hoping to find a solution!

I installed Pi-Hole on my NAS which is the same machine that my Plex server sits on. Do I just whitelist plex.direct on my Pi-Hole config page?

==============

Ok I think my situation is a bit unique in the sense that my Pi-Hole shares/has the same IP address as my Plex server because they are both apps running on the same machine-- my Netgear ReadyNAS. What I do know for sure is that:

  1. prior to installing Pi-Hole, I had correctly configured port-forwarding on my router and my Plex server is enjoying direct remote connections. It’s used on a regular basis and I never encountered any problem.

  2. after installing Pi-Hole, my Plex server became “not available outside your network,” although it is still accessible but with an “indirect” connection which is incredibly slow.

  3. I paused Pi-Hole and restarted my Plex Server, it instantly got direct connection again. So at this point I’m pretty sure it’s the Pi-Hole interfering with Plex server connection. But I’m not sure how to repair it. I’d like to have Pi-Hole and Plex running at the same time.

In my case I use pihole in use with unbound.
For unbound, just enter the config entry as described in the github issue and restart unbound once.
Afterwards everything should work.

With public DNS servers like 1.1.1.1 there should be no problems (at least I didn’t have any).
Ever checked if the DNS rebind protection (on the router) is turned on?
I think it might cause the same problem under certain circumstances.

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