Server Version#: 1.43.0.10492
Player Version#: I have Plex set up on my WD EX2 Ultra (NAS)
The remote access has been working perfecty fine. Then for no reason (no config changes, updates of any kind), it stopped and I cannot get it back. When I lost remote acess in the past, restarting the router seemed to do the trick, but not now.
What else can I do?
I have port forwarding set up in Plex and on the router (it has been like this for years).
I tried changing the port.
I have updated the Plex server.
I have reinstalled the Plex server.
I have restarted Plex and the router several times.
I have already read through Troubleshooting Remote Access | Plex Support
I have checked the port on CanYouSeeMe.org (I assume I have to enter the public IP and port that I have set up forwarding for.) Keeps telling me connection timed out.
I have been having exactly the same issue, and done almost exactly what you have done. Haven’t had any issues until two weeks ago.
This morning I shut down my entire network, turned off all Sonos speakers, rebooted the router. Wrote down all of the settings, ports beforehand. Rebooted and it’s up and running. The only visible difference is that a new public port has been assigned, which is consistent with the router. May have cleared out stuff in the background.
Will be keeping a check on it to see if it either keeps working or fails again!
If canyouseeme.org cannot see/access the specified public port from your manual forward, your next step should be to connect with your ISP. They might be blocking ports / certain communications or put you in a CGNAT.
Have you been able to verify the public IP recognized by canyouseeme.org matches the WAN IP of your router and public IP recognized within the Plex remote access settings?
I have always done that. I’m not directly relying on UPNP. But that hasn’t prevented remote access from going down. What is not clear to me why a system that has worked faultlessly for two years went down two weeks ago without me altering any of the set up.
I re-established full remote set up yesterday, which then went down yesterday evening, then after a full reboot I now have accessibility again. But my set up hasn’t changed at all.
I’ve also just double checked on canyouseeme.org and everything is fine.
I have a similar issue with 1.43.0.10492. Remote access is lost, I connect to the server, enable “Manually specify public port” using default 32400 and get the access restored. I have a script running every night that restarts plex; next day remote access is again lost.
LE: DSM 7.2.1
LE2: Interesting, I manually stopped plex from package center and start it back, no problem.
wondoring why this script breaks it
“#!/bin/bash
echo Checking if plex is running…
echo
/usr/syno/bin/synopkg stop “PlexMediaServer”
sleep 60
/usr/syno/bin/synopkg start “PlexMediaServer”
exit 1
fi"
If you’re using a port forward, that’s the public port used by your router — and if you configure that in Plex, it won’t switch to use a different port.
As for „why is it no longer working after it was working just fine for years“ → not all changes to your remote access setup are visible to you… many times, ISPs change things in their backend that can impact your setup.
Based on your description, it sounds more like an issue with your network configuration, e.g. changing IP addresses of the host running your PMS (DHCP).
Probably worth to have that in it’s own thread.
The symptom „remote access issues“ can have many causes and your script might be a very different case.
Thanks, I’ll monitor and post on a new thread if needed. I tried to reproduce the problem using the script after my manual restart and the checkbox for public port is no longer loosing the configuration. Strange one as it happened for the last 4 days. Will see tomorrow appologies if I hijacked the thread
My ISP uses dynamic IP addressing, so doesn’t that potentially change when the router is rebooted.
But the use of port forwarding isn’t mutually exclusive, so I have manually applied 25000 as the public port. I haven’t changed that since I originally set up the port forwarding.
So the only thing that has changed is the first element of the public address: xx.xx.xxxx.xx: 25000.
I may be doing something wrong, but that format has worked for years up until 2 weeks ago.
So, the ISP was useles. They (Virgin Plus) literally have no real tech support that know anthing more than is your internet working…. If yes, that’s all we can do. No info. No assistance. Not even able to escalate this or tell me who else I can contact. I did see someone in their forum mentioned this, but I have no idea what to do with it. Virgin appears to have switched to full Symmetric NAT. We no longer get a public IP.
It basically means the ISP is treating their backbone like a home network. Only their central infrastructure is directly accessible from the outside.
Technically, the ISP can make exceptions and provide you with a dynamic or static publicly routable IP address. Most will only offer you an option to sign-up for a static IP address and charge steeply for that.
So, I guess that means that there is nothing that can be done, since Virgin is using Bell’s fibre and Virgin’s tech suport is basically non-existant.
appologies if I hijacked the thread