Server Version#: 1.14.1.5487
Player Version#: 3.77.4
Running on Windows Server 2016
Plex.tv refuses to connect clients to my server. This worked fine until recent releases of Plex, and nothing changed on my network.
As you can see, Plex insists that my server isn’t accessible from my WAN IP, but you can also see that that’ exactly how I’m accessing it (connecting via WAN IP from work):
Port 32400 is manually forwarded to my server, which is using a static IP. Clearly it works, since I can access the server remotely, just not though Plex.tv.
Remote Access keeps disabling itself. When I re-enable it, it goes green for a second, then goes back to red, and no one can connect directly to my server anymore.
Restart your server.
Verify the accessibility of your server with canyouseeme.org
If they say ‘accessible’, just ignore the ‘Not Accessible’ warning within Plex for a few hours. Don’t do anything to these settings.
It will go green eventually.
I have restarted, and verified at canyourseeme.org - I don’t care if its red or green, I care that it actually doesn’t work when you access app.plex.tv, since that’s what users do…
After several reboots, it seems to be working. That was also the case yesterday, but it was broken again this morning, so I don’t expect it to stay “available” for long. Again, nothing has changed or is changing on my end, so why is this happening?
I am keenly watching this, as I also am having this issue. I can connect using my iPad/iPhone remotely, but I cannot remotely access my server from a PS4 or smartTV. I’ve also tried going back to previous builds, no luck, I’m wondering if something larger is going on here?
I have the SAME issue…
In addition, while playing PLEX, it stops streaming, and then next thing I know- my internet connection in the router gets CUT… I have to reboot the Modem-a router again…
I have stopped using PLEX for sometime because of this issue…
Please HELP us fix this…
Thank you for the logs and for enabling debug logging
There is a timing problem whereby the server may not end up as showing as enabled for remote access at the plex.tv end. I have seen the issue resolving itself by doing browser screen refresh (with F5) when on the Remote Access Server setting page - assuming the server has Remote Access enabled.
The debug logging was only enabled for the last 2 log files - so i don’t have much of the history of what was happening.
There is some evidence of this timing issue arising at 15:20 on the 19th after you disabled and re-enabled remote access.
After the restart there is evidence of an attempt being made to do a connectivity test at 15:21:10 on the 19th December. Was the port forward for wan port 32400 always there in the router for 192.168.0.100 ?
The log suggests an attempt was made by the plex.tv / pubsub servers to send request GET /identity to your wan ip and port 32400 but it did not get through
The port has been open for a long time, and hasn’t been altered recently. Up until recent builds of Plex I never had this kind of issue.
I don’t see anything getting caught in the firewall either.
The thing is, when I see it failing (and only offering people indirect connections), I can access Plex via my WAN-IP:port from outside my LAN, so I know it’s open. I used a third party web port checker too, which verified this.
It is possible that there are sometimes delays in the server responding to clients and so they instigate a Plex Relay connection when one is not needed.
Would like you to monitor the xml you get back from this request when the issues arise https://plex.tv/api/resources?includeHttps=1&includeRelay=1&X-Plex-Token=xxxxxxxxxxxxxxxxx
You would need to find the server token and put it in the browser request replacing the xxxxxxxxxxxxxx with the token string
Have a look at this support article for how to find a token https://support.plex.tv/articles/204059436-finding-an-authentication-token-x-plex-token/
So when you have the problem again - see from this xml what routes show for your server - each entry will have a number of connection routes. You should see the WAN IP and the public port. You can try these yourself by just adding /web at the end of the uri string
If they are there and work, it means the plex client apps may have had a timeout and switched to trying relay. If the routes are not there for WAN IP, then that could be the timing condition i mentioned which may resolve itself by re-enabling remote access and then doing browser refresh
The xml has security tokens so if you need to pass it to me, save to text file and zip and send by private message and for the logs you can continue to post here
As from yesterday my friends cannot see my main server. I can see on my network and notifications are all green
This server is on a Qnap NAS with 1.14.1.5488.
My other server a Synology NAS is being seen by the same friends and has same plex version.
