PMS cannot connect on HOST! It connects fine from other computers

Plex Media Server Desktops & Laptops
,
1

Server Version#: 1.20.1.3252
Player Version#: 4.34.4

I have two Linux servers running Plex. The older (that I’m going to retire) is Ubuntu 16.04. The newer is running Ubuntu 20.04.

  • Both have the same player and server versions.
  • Both have Firefox 81 installed.
  • Both have the firewall turned off.
  • Both are set to “Preferred” for secure connections

On the newer one, I CANNOT connect locally to the PLM via a web-browser, though I can connect to if from other computers (and Roku’s) on the network. It is functioning fine as a PMS everywhere but on the server itself.

I’ve tried connecting with Firefox to:

The address changes to include “/index.html#” and I get a PLEX logo (which might just be cached) but that’s as far as it gets.

I installed Chromium-browser to eliminate Firefox as the problem, with slightly different results. In Chromium when I go to any of those addresses I get:

This site can’t be reached
127.0.0.1 refused to connect. ← or whichever address I try

Try:

Checking the connection
Checking the proxy and the firewall
ERR_CONNECTION_REFUSED

… so I changed the proxy setting in Chromium, and double checked that the firewall was turned off, but it made no difference. Also, in Firefox I added the addresses I’ve tried to the exceptions for popups… just in case I was missing some sort of popup, but it made no difference.

For whatever reason, it seems that I simply cannot connect to the local server. I sort of hate to deploy this as my new server, since if anything goes wrong and I can’t connect from another machine, I’m out of luck trying to fix it.

Any help or ideas are grately appreciated!

Joe

2

Ok, partially solved. It appears that if you connect to a locally hosted PMS, you now get a redirection to Plex.tv that tells you that the server you are trying to connect to isn’t hosted by Plex and that you should only connect if you are sure this is the server you want. And there’s a button to log in.

I wasn’t getting that because I was running ‘noscript’ addon in Firefox. Once I turned off restrictions in noscript for the local IP, I got the redirect and warning, and was able to log in.

Bizarrely, I have no extensions loaded in Chromium and yet it still complains that the connection is refused. Really weird.

But, I can connect on the local machine now through Firefox, so I’m happy to move forward with the deployment.

Thanks to anyone who even read my post(s).

Joe

3

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