Plex server version: 1.24.1.4931
After a move I finally got around to fireing up my plex server. Only to find out i had to claim my server (it was off for 4 months). Now I can’t access it from Chrome remotely (although iPhone seems to work?) Port forwarding works (otherwise the iPhone Plex over 4G would fail)
So is there anything I am missing here ? I upgraded and started the server and this is where I am right now.
I don’t know the specific cause to it not connecting to the web app but as long as you have access to the physical server wherever you moved to, open your browser and attempt accessing your Plex Server by the following rather the Plex.tv method. If you truly do need to reclaim the server, you’ll be prompted with a opportunity to do so. This is something you can’t do over on the Plex.tv website only on the machine or device used to have Plex Server run on.
On all platforms, you can access Plex Web App on your local network. From any computer on the local network:
http://[Local Plex Media Server IP Address]:32400/web
(e.g. http://192.168.1.25:32400/web) Or locally, from the computer running the server:
http://localhost:32400/web
or
http://127.0.0.1:32400/web
Claim the server by connecting directly, from the local network, http://plex_ip_address:32400/web/.
If you’ve already claimed it, check Settings → Server_Name → Network → Secure Connections.
You want Preferred or Required.
Access via app.plex.tv requires a secure connection.
On the other hand, just as an FYI, Plex has had a few of their own problems with their own site and api, specifically yesterday Aug 20th. So as a way to troubleshoot, visit https://status.plex.tv/ for the status of Plex’s own operational/maintenance issues with their own services that your server may rely on.
Local access works… (as in the IP of the server + port). But not all local access. I kanda have a difficult local setup. So it might just be that.
@FordGuy61 I already claimed it and set SSL to preferred. But for some reason certain local networks have issues. I have to check remote Chrome… but remote iPhone works. The weird thing is that some local subnets have issues.
What are the subnets? Do they use RFC1918 addressing?
How is traffic between subnets routed?
The client is behind a firewall (no blocking rules) and need to go through another router to get to the internet. Everything inside is RFC1918. I am trying to access it using plex.tv … using its internal address on port 32400 works. plex.tv doesnt. However an iPhone that is NOT behind this firewall does work. I am starting to think the firewall has a routing / NAT issue …
Let me correct myself. Chrome on the same network as the Plex server cannot connect to app.plex.tv … (this is Chrome on a MacBook). An iPhone on the same network CAN connect to the plex server (I am guessing the phone also uses the internet way).
So whats up here… we can rule out the firewall for now.
Just checked by using a 4G hotspot: the same Chrome Macbook cannot access Plex from the internet.
Can someone from Plex step in. It looks like the reclaim of the server (why was that needed ??) screwed up my install.
C:\Users\user>nslookup 192-168-178-251.521e4907787642e4a5a3f859995ab9a0.plex.direct
Server: one.one.one.one
Address: 1.1.1.1
Non-authoritative answer:
Name: 192-168-178-251.521e4907787642e4a5a3f859995ab9a0.plex.direct
Address: 192.168.178.251
This will never work… why is it not registering my public ip ??
Try using the information in this support article to ensure your public connection information is being registered. As far as I know, clients will always try to make a local connection first and, failing that, attempt the remote connection (the one marked local="0"').
You can also view the web client’s debug logs to see where the web client is attempting to connect. By filtering on “plex.direct” you should be able to see which URLs it knows about and to which it tests connectivity.
@pshanew the debug logs do not seem to register any public ip however my server does work over a remote ip. Internally the public ip does not work anymore (app.plex.tv). So I tried to figure out what is going on but even debug logs show nothing useful.
This applies. But somehow it does (only from a phone) work on 4G. Tethered chrome on a pc or Mac does not work.
Where are you seeing the incorrect IP address? Is it at the resources link, or in the client logs?
If it’s in the client logs, try signing out of the affected clients and signing in again. That might cause the clients to update their server lists.
If it’s the resources link, can you expand on what you mean by “wrong” IP address?
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
