Media Server only available when in insecure mode

Server Version#: 1.20.1.3252
Player Version#: 4.34.4

This is the problem.
When i try to access the server via https://app.plex.tv/desktop, Plex tells me that it is unable to connect to my server securely. All i get is the exclamation marks where my server list on left side of the page should be. Once I click on the button to connect insecurely to the server, it then displays the server. So i can watch what i like on my desktop windows 10, however remote access is not available via port forwarding.

  • I have turned off the router for a minute and turned it back on, done this several times
  • Turned off and on the computer
  • Checked that the Ip address is the correct one for remote access
  • Deleted the Plex server inside my routers Nat Virtual server setup then re-added it
  • Turned off then turned back on upnp
  • Confirmed that the port forwarding number im using is open
  • Deleted cache and cookies on my browser
  • Tried Plex on two different browsers with same result
  • gone to cmd and flushed the dns and reset TCP/IP
    Realized that when resetting TCP/IP in cmd, it came back with resetting, failed.
    So i went into regedit and did some stuff that was meant to fix it, however did not work, for some reason, cmd will not allow me to reset the TCP/IP

Update, went back into regedit to change something to allow all access which resolved the tcp/ip reset, but still made no difference to my plex issue

  • Exited out of Plex server and turned it back on
  • Checked and confirmed Plex is allowed on the firewall, also turned off firewall to see if that would make a difference.

Despite all of this, and doing it all several times over, no luck.

Any other steps i can take to try and resolve this?

Is the behaviour the same with Chrome and Edge web browsers?
Or does Chrome work and Edge is not?

If both don’t work, while being on the same local network as your server, you might be the victim of the notorious “DNS rebinding protection”. https://support.plex.tv/articles/206225077-how-to-use-secure-server-connections#toc-4

One has nothing to do with the other. If you disable secure connection in your browser, it doesn’t affect other clients which are trying to connect remotely.
Your server is available remotely, but judging from the port number, it uses an automatically created port forwarding. Did you forget to set the checkbox in Plex? https://support.plex.tv/articles/200931138-troubleshooting-remote-access/

“DNS Rebinding Protection” as in i wasnt attacked by a DNS rebind but rather my isp or router did something that caused this situation with my Plex App?

The latter. This is usually a good thing. But due to the way Plex is handling encryption ( by assigning your server an own FQDN on the plex.direct domain) this protection is mis-firing.
Hence the need to define an exception.

ok so sadly, my IP support tells me theres nothing they can do as its outside of their scope of training?
My router which was provided by the IP has been purchased by another company, i sent them a help desk ticket to assist with defining an exception, so im guessing they will reply back, hopefully.

Is there anything else i can do or try in the meantime to potentially resolve this?

If the router doesn’t provide those preferences, you can only do these things:

  • get a different router
  • get a 3rd-party, alternative firmware for the existing router (of course you can only do that if the router is your own property). There are open source projects named DD-WRT, Open-WRT, or Tomato.

I also have this issue and I guess there are two ways around it:

  1. Use the Plex for windows application which doesn’t have this problem.
  2. Use the local IP address and port of the server to connect to it, for example I use:
    http://192.168.1.220:32400/web/index.html

I get a “Not secure” warning in the address bar at the top but as this is local traffic on a secure network I’m not too worried by this.

This is my setup, but I am getting the same problem as my server is not available.

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