I’ve had this issue now for a few days where when switching a user and that new user logs in, I get the “Looking for servers” box and it never goes away. If I refresh the page at this point, it will ask me which user I want to be and then after I chose the right one again, it will let me in just fine.
It got annoying enough that I wiped EVERYTHING on the server (library, settings, everything) and reinstalled. Cleared the browser cache. Tried different browsers. Nothing works. Under the remote access tab, it says fully accessible outside of your network.
I’m beginning to think that there may be something on the plex.tv end that may cache something and is preventing me from logging in properly.
I ended up posting this is another sub group or something because I’m not a whiz at these forums and trying to figure out the new tags and sub forums and everything else.
As a reference, here’s my other post…
To answer your questions…
This is me connecting to the server from my Chrome browser (10.0.112.11). Running Version 72.0.3626.119 (Official Build) (64-bit)
I’m not exactly sure what you mean. I’m on one network internal segment (10.0.112.11) and my PMS is on another segment (10.0.110.2). I have firewall rules setup for 32400. I think this also happens outside of my local network and I can verify this tomorrow.
Yes, the 2 users are in the same household. One user is the admin/root user and the other is a Home user that doesn’t have admin/root to PMS.
The main/admin user is my main plex account and password. My “home” user is a managed user and not an existing plex account user. So when I use the “Home” user I have to login to my plex account first and then chose the Home user…if that makes sense.
Under family adn friends, the user is listed under “Home User”.
I had the exact same issue trying to access Plex over the local network from a different subnet than what the Plex server was operating on. Exact same messages and problem as OP and nearly the same version of Plex. The issue was resolved by upgrading Plex to 1.15.2.793. Nothing else was changed to resolve the issue.
Interesting that I’m also going across subnets…but off the top of my head, even when connecting to the localhost on the installed PMS, I was still running into issues.
There was another topic started up with the same problem but it was a few folks running it on Windows. I lost touch with the topic as it didn’t seem to get a good response from anybody from plex, but I think there’s still issues with it. As little as this problem may be, it is annoying. I found that if I use the IP of the PMS instead of the DNS name that I have registered in my local DNS, things work OK. But now I have to type in an IP instead of just plex.foo.org.
I haven’t seen anything in any release notes lately that would make me think this specific issue was resolved, even though a handful of users can replicate the problem.
This issue has really brought to light the support level that customers receive with Plex. I guess I could kind of understand not wanting to help everybody because most of the time, it’s some misconfiguration on a user’s end that is causing the problem. Maybe it is for me and the handful of other users as well. But just the lack of support that we’ve received and nothing that says “try this” or “try that” and more like a “deal with it and use plex.tv” makes me a bit sour.
I agree with the sentiment to some extent, but I think it’s also important to realize that this usage is outside the scope of a supported deployment. There are simply too many possible deployment scenarios for Plex staff to support.
I do think the issue may be with your DNS setup. You mentioned you have a hostname in your local DNS? I’m not totally in the know about the architecture of the Plex web viewer, but it’s very possible that some requests are relayed to the PMS. If the browser tells the PMS to lookup plex.foo.org for some requests, but plex.foo.org is not resolvable by the PMS, then it might fail.
