I recently got a Synology NAS(1019+) everything has been operating fine until today. I went to update the PMS(there was an update available) and now myself and remote users are only getting indirect connections and remote access keeps going from accessible outside my home network to not accessible. Nothing has changed on my network I’ve got port forwarding etc set properly My server is connected via a LAN cable. Any help would be greatly appreciated.
Server Version#: 1.21.2.3918
Player Version#: 1.26.0.1531-92029e9e
it does do that but then instantly goes back to red of not being available additionally everything not locally is playing as indirect no matter the user. The NAS was running fine up until the update to the server. This whole move has been a nightmare and frankly Im regretting it. Any help would be sincerely appreciated as Im super frustrated and ready to give up and just go back to the mac mini.
There are only a few things with Synology which can impact Remote Access.
The modem/router and either a good UPNP manager in that device (many are junk)
Manual port forwarding to the LAN IP address which is not static. (I have seen where the DHCP server refreshes the NAS IP every 10 minutes. This makes PMS reset both the LAN and Remote Access . Best results here is a static IP address on the Syno.
Incorrect use of multiple ethernet adapters, which will cause it to float between the two adapters, will drive it crazy.
What can you tell me of the LAN config & topology
?
Im using a Ubiquiti USG which I’ve been using this entire time(when my server was a mac mini and I never had a single issue) I have the port forwarded in my unifi settings and even made the static address of the synology the same as the mac mini(after disconnecting it of course). Im only using LAN1 on the synology. MY ISP modem is in bridged mode(again nothing has changed on my network other than replacing a mac mini with the Synology as a server)
Modem>Ubq Router(USG)>Ubq Switch>Synology Nas there’s no vlans and everything is in the same 10.10.10.x subnet. Additionally I followed your instructions and downgraded to the 1.21 PMS and Im still having the exact same issues. Remote access goes in and out(not just the check mark in the left hand tab) and im still getting indirect connections.
a remote user is currently able to access my server despite the remote access issue but it’s still an indirect connection, not sure if that’s progress but if I can fix the indirect connection part I can die a happy man. Thanks.
This isn’t PMS itself. This is entirely a networking issue.
If you’re losing remote access itself then that points to:
(the checklist for any situation)
WAN IP changing
LAN IP changing
Synology Firewall rule(s) not keeping up – if active
Forwarding rule not tracking.
All that Plex does to test , confirm, then verify (hourly) you have remote access is:
Send a message to Plex.tv giving it your WAN IP and PMS external port number.
Plex.tv (any one of the hosts in the cloud) will attempt to connect to the server.
When it does connect, they exchange the ‘verification’ message.
PMS then sets current state Green (OK) if it receives that message in time and Red (FAIL) if not.
Would it be possible for you to conduct the following test?
Verify you have DEBUG logging enabled and VERBOSE logging disabled.
Restart PMS and allow it to sit completely idle for 3 minutes (long enough to guarantee the startup and handshake with Plex.tv Remote Acess reachability test.
Download those logs ZIP and attach
To the point of Indirect, That means there is NO inbound connection.
Do you also have Indirect for the players on your LAN ?
If so, then it is the Synology Firewall or the USG . I’m inclined to think Syno first.
