Hi - I am having the same issue. It worked fine on Friday, as usual. But then yesterday I began noticing that remote access would not work. I had made no changes in my router setup, or any other setup.
I have the port manually forwarded to 32400. I checked canyouseeme and it showed the correct ip, but the port timed out. I added a log, if that helps. Any assistance would be appreciated. Plex Media Server.1.log (10.0 MB)
This would have been retried 3 hours later - would like to see if the error is repeating itself.
This WD Cloud device still has an old PMS version - when did the problem start ? Could you get all the log files - zipped
WD plan to update the version of PMS sometime later this year. I do not know at this point if the issue is due to this being a very old version that WD have.
Thanks. It literally worked fine this past Friday and Saturday playing music, then did not work yesterday. I have attached the full zip of the log file. Plex Media Server Logs_2021-07-06_13-15-39.zip (5.3 MB)
Appears to be a sold fault - each retry gets same erorr. May be certicate was renewed and that was when the issue started. Will discuss with the development team
I am currently suffering the same issue. Ports are correctly open on the firewall, remote access is enabled in Plex etc. I have performed a full reinstall to a new server out of frustration, however the issue persists.
Previous attempts at fixing (as per a post on Reddit) involved disowning the server and reclaiming it, however this only worked for a few seconds before failing again.
Remote access is currently unusable (except through relay). Are we to assume that perhaps an issue with the certificate maintenance has emerged? Happy to provide logs if necessary.
One issue we have had in the past with certificates is when the Plex Media Server device system clock is ahead of itself in time. Could you check that the system time on this WD Cloud device is correct
Thanks. I have the WD MyCloud Home. I do not see any way to check the date/time on this device. I have looked all through settings and the user manual.
Hi everyone, Plex was working fine and then on Friday 7/2/21 I notice no devices were able to connect to the Plex server. I then also notice I was not able to connect to it via Plex.tv. I have not made any changes at all for it not to work. Now the only way any devices can access the sever is by going to advance in every device and then selecting always allow unsecured connections. Please help.
I have confirmed that your port forward is ok by actually reaching your server and getting challenged for login - when using http
Will need to replicate the request that plex.tv sends to the server for connectivity test and then try and send one and see if it gets rejected. I am only working one day a week and i will have to leave it till next Tuesday - you could try disabling secure connections in server settings (network) and see if that gets your remote access working if you like to try it and next Tuesday with it re-enabled I can do some testing
Thanks. It looks like disabling the secure connection worked for the time being. I appreciate your help. Can we look at it again next week when you get back to see if we can get it working correctly?
Thanks!
yes - send me a private message next Tuesday after you re-enable secure connections (as per default: Preferred) and suggest restarting the server after that and sending me logs
Bizarre - Iāve spent the last couple of days battling this, saw your post, tried it and youāre right, it works. I have an ATT BGW320 router and a WD My Cloud Home connected to it, Iāve done a fixed allocation on the IP for the MCH and added two port forwarding rules for Port 32400, one for TCP and one for UDP. I also turned off IPv6 for good measure. Initially in the Plex desktop, the Remote access turned green, with a jaunty green check iconā¦then, a few hours later I noticed it had a red exclamation mark on itā¦whenever I retried it would go green for a few seconds and then revert back to red, which was a massive tease. I then tried rebooting the MCH, restarting the router, deleting and reinstalling the port forward rules, restarting the Plex, and all combinations in between to no avail. Finally, after reading your post I turned off wifi on my phone and tried accessing Plex⦠and it worked, even though the plex desktop still says its unavailable. So Iām at a loss. Iāve spent days chasing a green check, only to discover it appears to be working anyway.
To check remote access status, your Plex Media Server checks in on a regular basis with a plex.tv host. Sometimes the check-in fails (time-out, net congestion, etc) but remote access still works. When this happens your server will show remote access as not working when it is really still available. Plex made some changes to Plex Media Server and their backend hosts last year (May/June) to improve the process, but the situation can still occur.
You can check if remote access is working outside of the Plex Remote Access status page:
canyouseeme.org
From a system on the same network as your server, go to canyouseeme.org.
Replace the default port with your Plex remote access port & click Check Port.
Success means it can reach your server.
Uptime Robot
Uptime Robot will check remote access every five minutes and send an e-mail if it cannot reach your server. The web interface also has a nice dashboard showing percent uptime, listing when connectivity was lost & regained, etc. The basic free account works fine for monitoring a Plex server. Your Plex server must be using manual port forwarding. With automatic, your remote access port will change when you restart your server, etc, which would break monitoring by Uptime Robot.
This is great information, thank you.
I am confused by one aspect though, which may be a pointer to the issue:
When I run canyouseeme.org, the IP address it shows is different to the Broadband IPv4 Address shown in the AT&T BGW320 Fiber router, which it states is āThe public IP address of your device, whether dynamically or statically assigned.ā
In the Plex app, the remote access rule is using the BGW320 IPv4 address and pointing to the fixed allocated IP address of the MCH. Private [Fixed Allocated IP for the MCH] : 32400 Public [BGW IPv4 address] : 32400
canyouseeme,org has an error when I enter port 32400, but I can successfully access using http://[BGW320 IPv4 address]:32400/Web
Iām not sure if this helps, hinders or is irrelevent, but I mention because Iāve seen in a number of threads the assertion that the IP address shown in canyouseeme should be the same as the router and in my case it is not. I wonder if this is unique to the BGW320? This is the unit ATT installed to activate my gigabit fiber service.
PS: I only added the UDP port forward because Iād read that entering both was required. Iāll remove that now. If truth be told this is all dark arts to me Iām just working blind here, trying stuff out from what Iām reading to see if it works.
The public IP address provided by the AT&T router should match the public IP address shown on your Plex Media Server remote access settings page, and that should match the address shown in canyouseeme.org.
Are you running a VPN client on the system you used with canyouseeme.org? Were you using a mobile device not connected to your LAN? Either would change the devices public IP address.
Normally Iād say shutdown your server, reboot the router, then restart the server.
However, if things are working, I tend to say, āIf it aināt broke, donāt fix it.ā
One thing to check:
From a remote device (phone on mobile network, etc), stream a movie/show/etc from your Plex server
.
Monitor playback using Plex Dashboard ā Now Playing. Expand the view to show the details of the stream.
Is the stream local, remote, or indirect?
If indirect, then the remote device is connecting via Plex Relay (tunneled through servers at plex.tv), not standard remote access.