Limited Connection warning when using Plex Web app to play files on same machine

I get this warning:

when I attempt to watch a file with the Plex Web app in Firefox on the same Windows 7 pc as the file. Any idea how to fix this? PMS is up to date.

Either

disable ‘Secure Connections’ on your server (Settings - Server - Network)
(restart Plex server afterwards. You might also have to allow Plex Web do fall back to unsecure connections under Settings - Web - General)

or

  1. Edit the settings of your router to use Google’s DNS servers (8.8.8.8 + 8.8.4.4) instead of the one from your ISP.
  2. find out whether your router has a ‘DNS rebinding protection’. An exemption needs to be created for the domain *.plex.direct

https://support.plex.tv/hc/en-us/articles/204604227-Why-can-t-the-Plex-app-find-or-connect-to-my-Plex-Media-Server-

I had to disable secure connections and change the DNS servers but fortunately I didn’t have to get into DNS rebinding protection. Thanks for the quick reply.

My setup is all default, is this a bug in the Plex Media Server?

If you disabled Secure Connections, changing DNS and DNS rebinding protection is not necessary. Only if you insist on Secure Connections you need to do both DNS server and DNS rebinding protection.

No, this is not a bug but rather how secure connections work.
https://support.plex.tv/hc/en-us/articles/206225077-How-to-Use-Secure-Server-Connections

Neither disabling secure connections or changing the DNS servers resolved the problem alone but they worked in combination. Should that not be the case?

I have a rudimentary understanding of secure connections (after checking out your link). Why would that affect media on the same device?

@phillo12345 said:
Neither disabling secure connections or changing the DNS servers resolved the problem alone but they worked in combination. Should that not be the case?

No, normally not. (Provided you did the server restart after switching off secure connections.)

I have a rudimentary understanding of secure connections (after checking out your link). Why would that affect media on the same device?

Because server and client are different apps and if secure connections are either set to ‘require’
or
the web app is not allowed to fall back to an unsecure connection,
it will as well try to use a secure connection. Which only works with proper name resolution of the *.plex.direct subdomain and working DNS rebinding.

@OttoKerner said:

@phillo12345 said:
Neither disabling secure connections or changing the DNS servers resolved the problem alone but they worked in combination. Should that not be the case?

No, normally not. (Provided you did the server restart after switching off secure connections.)

Yea I restarted PMS after disabling secure connections but it wasn’t until I changed the DNS servers that the problem was resolved. Out of curiosity I re-enabled secure connections but the problem came back.

Regardless the problem is fixed and I appreciate the help and information a lot.