I have the same issue and can access on my device and through https://app.plex.tv/ I then remembered I enabled require secure connection rather than preferred in network. Changed back to preferred and it has started working again. I’m guessing I don’t have valid certificates causing the issue.
It is actually most likely (kinda) the other way around:
- secure access can only work with a valid certificate
- a valid certificate can only be bound to a FQDN, but not to an IP address
- using a FQDN for a local server is only possible if your router (or more precisely: your local DNS resolver) is allowing Plex to assign a FQDN to a local IP.
However, some routers will block such a behaviour as a ‘DNS rebinding attack’.
Therefore, for secure connections to a local Plex server, you need 2 things to be cooperative: Your local DNS resolver and your ISPs DNS server.
If your router has a setting to block ‘DNS rebinding’ attacks, it hopefully has also a way to define exceptions. Put in an exception for the domain plex.direct.
And some DNS server provided by ISPs mess up with the .direct top-level-domain. Using an alternative DNS server can help. (e.g. use Google’s DNS service instead 8.8.8.8)
Side note: Plex is both providing the FQDN and the fitting, “pinned” certificate. You don’t need to supply your own domain, nor a certificate.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
