It’s strange that he can get to my content no issue if he uses https://my.wan.ip:32400 but not if he goes thru plex.tv. Seems consistent with the “no remote access” issue. But don’t understand why that just started happening out of the blue.
Not to cross the streams too much, but have you implemented the restrictions you were discussing in this thread?
It could be relevant to remote access issues. (It would likely manifest how you describe, where your server can be reached remotely via its IP:PORT but not via apps which rely on published connection information.)
No I disabled all those restrictions. But, they were working fine for the last few days. Even with the firewall wide open out and in I could still not get my PMS to connect for remote access.
I am getting this now checking user access on app.plex.tv
When I try to access my server from app.plex.tv there are ZERO hits on the firewall inbound. It’s as if Plex has no idea my server (IP) exists. It’s not even trying to connect from what I can tell.
Try navigating here:
You can find your Plex token using the information in this article:
https://support.plex.tv/articles/204059436-finding-an-authentication-token-x-plex-token/#toc-0
When you visit the above URL, it should render an XML document showing all of your devices, including your server. It will include connection information for each. Find your server and see if it shows what you’d expect (your WAN IP for one of the connections).
Did you replace “your_plex_token” in the URL with your private token? That error is what you’d see if you just clicked on the link.
no, sorry, just caught that… where do I see my private token ??
I linked a document in that post which describes how to find your token…
Yeah, sorry…
The issue is I cannot see any of my content from thw web app. I can only access it locally. I can get to the LOCAL web app. I will try that.
The UUID from LOCAL plex web (127.0.0.1:32400) did not work. Same “invalid token” error as above.
So, from your local network, you’re unable to log into https://app.plex.tv?
I’m wondering… given the odd behavior when I (attempted to) reclaim the server earlier… if something broke.
I fully expected the reg cleanup to require me to reclaim the server, but it never did.
I really have no explanation for any of this odd behavior. It seems like Plex does not know where to find my server any longer, so nobody remote can contact it. That is supported by ZERO firewall hits while it’s trying to connect remotely.
Since you can access your server by IP address, go ahead and do so. Head to:
Settings → [Select Server Name] → General
If the server is claimed, it should show it at the top of the page, and by whom. If it is claimed, and under the correct account, a DNS issue might be at play.
Plex apps (and the web app at app.plex.tv) need to be able to resolve the server’s *.plex.direct FQDNs via DNS.
On the system you’re testing on via the browser try setting its DNS servers to a public provider like 1.1.1.1/1.0.0.1 (temporarily, to test). This has no DNS rebinding protection and so should be able to resolve your local plex.direct names to IPs.
Then see if https://app.plex.tv behaves as it should. There’s no point in trying to fix remote access at this point; you need to be able to access the server via https://app.plex.tv first.
It shows claimed by me.
Not sure I’m following the DNS logic. Is there a particular DNS name I could test to ensure *.plex.direct resolves (I think that is the question) ?? I cannot easily change DNS settings on this network.
Interesting, now I am seeing this on the general page. Update check has never not worked..
Yes, that’s the thrust of it. You can construct an FQDN to test using these steps:
- Open regedit on your server and navigate to the following key:
- HKEY_CURRENT_USER/Software/Plex, Inc./Plex Media Server
- Note the CertificateUUID.
- Construct the plex.direct FQDN of your PMS:
- Dash separated octets of your servers local IP address (e.g. 192-168-1-100)
- The certificate UUID noted above (e.g. abcdefg1234567890)
- the plex.direct host domain.
So, your final FQDN will looks something like:
192-168-1-100.abcdefg1234567890.plex.direct
Try resolving that on your network (nslookup, ping, whatever). If it resolves, great. If not, you’ll need to figure out why.
Resolves no problem. Comes back with my WAN IP.
