Remote Access DSM 7.7.2 PMS 1.41.0.8911

Plex Media Server Remote Access
1

Server Version#: 1.41.0.8911
Player Version#: ?

A week ago remote access became intermittent to PMS housed on DS1019+ (upgraded ram) with minimal resource utilization. It progressively became worse and 2 days ago stopped working all together. I had upgraded to PMS 1.41.2.9200 to see if that would clear the issue. It didn’t. I have AT&T fiber, the manual port is forwarded, and it does show remote access green, but immediately goes red.

  1. Checked double nat (none)
  2. Checked IP blacklist (none)
  3. Static IP on DS1019+ running DSM 7.7.2
  4. Port opened on AT&T router/RG tied to DS1019+ MAC
  5. TP link WiFi router in bridge mode behind it
  6. Using both ethernet ports on DS1019+ bonded
  7. Disabled the firewall all together in DSM 7.7.2 (no change)
  8. Removed all traces of PMS from Synology and reloaded 2x (rebuilding library currently).

There were no configuration changes with either my AT&T router, DSM 7.7.2, Tplink in bridge WiFi router, or PMS before attempting the above troubleshooting.

All help to resolve would be appreciated.

2

There is no need to uninstall Plex Media Server.

To what is the NAS connected, the AT&T router or the TP Link?

Which method is used to bond the Ethernet ports - Active/Standby, Dynamic Link Aggregation, etc.?

As a test, try the following:

  1. Unbond the Ethernet ports.
  2. Connect only one NAS Ethernet port directly to the AT&T router.
  3. Verify the port forwarding statement in the router is still pointing to the NAS.
  4. Enable remote access in Plex Media Server
  5. Wait 2 - 3 minutes to see if it stays enabled. It initially “goes green” while trying to activate remote access. If activation fails, it will then change to “not available.”
  6. Even if disabled, try https://canyouseeme.org. Substitute your remote access port for port 80 on the web page.

Some docs that may help:

FWIW, I’ve a DS918+ / DSM 7.2.2 Update 1 and AT&T Fiber. Remote access is working w/o any problems.

1 Like
3

Thanks @FordGuy61.

Too late on the uninstall PMS :frowning:

I’ll give the more labor intensive suggestions a try in the next few days/weekend.

  1. Bonded aggregation to the TP Link AXE300
  2. Tried https://canyouseeme.org and it failed to see me.
  3. Confirmed with the AT&T RG the configs were correct.
  4. Undid and redid them just in case
  5. Still returns to Not available outside your network

Sincere thanks for your timely and thoughtful reply. Much appreciated.

4

Appreciate your help. I’m not sure what’s going on @FordGuy61. Media is still scanning, data updating, etc. I show a greyed out server (mine), and a non-greyed out server (also mine). I can access the media both on the LAN and on the WAN, however it still shows can’t remote connect. It’d be nice to get rid of the greyed out duplicate server name/file names that are empty. Thinking will just let the scans finish, and see where I’m at after, unless you’ve seen this and have some recommendations.

5

Look in your list of Authorized Devices: https://app.plex.tv/desktop/#!/settings/devices/pms

Delete any old servers. That will remove them from your account.

Don’t delete your current server. Doing so will unclaim it. It does not hurt anything, but you’ll have to re-claim the server.

If you’ve any libraries from the old server pinned to a home page, you may need to manually unpin them.

When accessing via WAN, monitor playback via Plex Dashboard → Now Playing + Expanded View.

Is the connection Indirect?

If so, it is using Plex Relay, a fallback for when remote access is not available. The stream is tunneled through a server at Plex and is limited to 2 Mbps (1 Mbps w/o a Plex Pass).

You can disable (set to never) thumbnail generation, intro detection, etc. in Settings → Library. That will speed things up. You can re-enable them later.

If I remember correctly, the tasks will stop when they finish processing whatever file they’re analyzing. If they do not, you can always stop/re-start PMS.

Two other things to check:
a) The public IP address displayed in Settings → Remote access should be the same as displayed in canyouseeme.org.
b) In Settings → Remote Access, be sure to check the box to manually specify the public port. This must be done even if using the default 32400.

The reason for unbonding, connecting directly to the AT&T router, etc. is to simplify troubleshooting. Once the basics are working you can move the NAS back to the TP Link. Once that is working, you can re-bond the interfaces.

6

@FordGuy61 Thanks for your help. canyouseeme.org still shows matching public ip, but it times out with the open port. However, I can access everything like I used to LAN and WAN. I didn’t check any of the hardwiring between NAS, bridged WiFi router, and RG yet. Might have to wait till next week to try that.

7

When streaming remotely, what does the Plex Dashboard show?

Is the connection remote or indirect?

Plex Dashboard → Now Playing + Expanded View.

8

It was Indirect (2M) :(. I turned off the NAS. I deleted the NAT gaming port configuration. I then cleared/rescanned the devices on the RG and added back the NAT gaming port configuration. At present it’s playing remote vs indirect and canyouseeme can see me :).

I can only think there were some cobb webs in either the device list or in the nat gaming configuration section as I’m fairly comfortable with that having had a Synology NAS since 2012. Sincerely appreciate your help. I’m hoping this was the fix and that I don’t have to start going physical cat6 L1 testing. LMK what I owe you :slight_smile:

9

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.