"The server '#######' does not allow secure connections." What happened?

Plex Media Server
1

Server Version#:DSM 7.1.1-42962 Update 2
Player Version#: 1.29.1.6316-7000

Please bear with me because I don’t yet have a grasp of how this all works, so I may be just sharing generally useless info that you will have to sift through.

I recently upgraded the Syno HDDs in my pool. While doing that, I relocated all my media into a new shared folder, which Plex had access to. I added a bunch of new media (videos) to my existing collection, which appeared on Plex. I have a bunch of audio files, and Plex was scanning through it all. Unfortunately it got stuck scanning one large collection (a catalog of Bach or something) for over 24 hours, so I cancelled the scan. I had added one more movie to my server, and this movie never appeared on Plex.

Now I see that I am unable to securely connect to my server. Between the last time Plex accessed the server until I noticed it could not, I did not change any features. Any help would be greatly appreciated.

2

Plex/web can be kinda dumb.

“doesn’t allow secure connections” is its way of saying it can’t connect – which is true.

What it doesn’t tell you at that instant is " Is the server running & available ? "

  1. If Plex is running, Stop it
  2. Open Filestation
  3. Navigate to PlexMediaServer/AppData/Plex Media Server
  4. Right-click “Logs” → “Compress to Logs.zip”
  5. When that’s done, download it
  6. Attach it here and I’ll see what it’s not happy about.
3

Logs.zip (6.4 MB)

Thank you. Here you go.

4

Any news?

5

I’ve looked over this a few times and compared with other cases I’ve seen.

I can’t see what happened when PMS started (due to all the activity which rolled off the end of the logs)

What I do see is everything running through Relay (indirect) connection

It makes me ask: Do you have the Synology firewall on and is it blocking port 32400 ???

You can see where PMS is struggling to find a connection to the internet.
This should all be defined and absolute in the NAS network settings.

 09:18:10.093 [0x7f94688aa0] DEBUG - NAT: UPnP, didn't find usable IGD.
Nov 08, 2022 09:18:10.093 [0x7f94688aa0] DEBUG - PublicAddressManager: Mapping failed.
Nov 08, 2022 09:18:10.555 [0x7f94688aa0] DEBUG - MyPlex: mapping state set to 'Mapped - Not Published'.
Nov 08, 2022 09:18:10.579 [0x7f94688aa0] DEBUG - MyPlex: Last published value didn't change, we're done.
Nov 08, 2022 09:18:12.849 [0x7f90c69aa0] DEBUG - NAT: UPnP, found device <http://192.168.1.76:5000/ssdp/desc-DSM-eth0.xml> with private address <192.168.1.76>
Nov 08, 2022 09:18:12.849 [0x7f90c69aa0] DEBUG - NAT: UPnP, not an IGD: <http://192.168.1.76:5000/ssdp/desc-DSM-eth0.xml>.
Nov 08, 2022 09:18:12.850 [0x7f90c69aa0] DEBUG - NAT: UPnP, found device <http://192.168.1.76:50001/desc/device.xml> with private address <192.168.1.76>
Nov 08, 2022 09:18:12.850 [0x7f90c69aa0] DEBUG - NAT: UPnP, not an IGD: <http://192.168.1.76:50001/desc/device.xml>.
Nov 08, 2022 09:18:12.852 [0x7f90c69aa0] DEBUG - NAT: UPnP, found device <http://192.168.1.254:49152/wps_device.xml> with private address <192.168.1.76>
Nov 08, 2022 09:18:13.114 [0x7f90c69aa0] DEBUG - NAT: UPnP, not an IGD: <http://192.168.1.254:49152/wps_device.xml>.
Nov 08, 2022 09:18:13.116 [0x7f90c69aa0] DEBUG - NAT: UPnP, found device <http://192.168.1.254:49152/wps_device.xml> with private address <192.168.1.76>
Nov 08, 2022 09:18:13.116 [0x7f90c69aa0] DEBUG - NAT: UPnP, not an IGD: <http://192.168.1.254:49152/wps_device.xml>.
Nov 08, 2022 09:18:13.118 [0x7f90c69aa0] DEBUG - NAT: UPnP, found device <http://192.168.1.254:49152/wps_device.xml> with private address <192.168.1.76>
Nov 08, 2022 09:18:13.118 [0x7f90c69aa0] DEBUG - NAT: UPnP, not an IGD: <http://192.168.1.254:49152/wps_device.xml>.
Nov 08, 2022 09:18:13.119 [0x7f90c69aa0] DEBUG - NAT: UPnP, found device <http://192.168.1.254:49152/wps_device.xml> with private address <192.168.1.76>
Nov 08, 2022 09:18:13.122 [0x7f90c69aa0] DEBUG - NAT: UPnP, not an IGD: <http://192.168.1.254:49152/wps_device.xml>.
Nov 08, 2022 09:18:13.124 [0x7f90c69aa0] DEBUG - NAT: UPnP, found device <http://192.168.1.254:49152/wps_device.xml> with private address <192.168.1.76>
Nov 08, 2022 09:18:13.124 [0x7f90c69aa0] DEBUG - NAT: UPnP, not an IGD: <http://192.168.1.254:49152/wps_device.xml>.
Nov 08, 2022 09:18:13.125 [0x7f90c69aa0] DEBUG - NAT: UPnP, found device <http://192.168.1.76:50001/desc/device.xml> with private address <192.168.1.76>
Nov 08, 2022 09:18:13.125 [0x7f90c69aa0] DEBUG - NAT: UPnP, not an IGD: <http://192.168.1.76:50001/desc/device.xml>.
Nov 08, 2022 09:18:13.162 [0x7f90c69aa0] DEBUG - NAT: UPnP, found device <http://192.168.1.76:5000/ssdp/desc-DSM-eth0.xml> with private address <192.168.1.76>
Nov 08, 2022 09:18:13.174 [0x7f90c69aa0] DEBUG - NAT: UPnP, not an IGD: <http://192.168.1.76:5000/ssdp/desc-DSM-eth0.xml>.
Nov 08, 2022 09:18:13.174 [0x7f90c69aa0] DEBUG - NAT: UPnP, getPublicIP didn't find usable IGD.
Nov 08, 2022 09:18:13.424 [0x7f90c69aa0] WARN - NAT: PMP, got an error: Not Supported by gateway.
Nov 08, 2022 09:18:13.609 [0x7f90c69aa0] DEBUG - [HCl#16f5] HTTP requesting GET https://107-198-4-66.4e3f9aafe1594300b25a46f7ae495052.plex.direct:0/identity
Nov 08, 2022 09:18:13.610 [0x7f9a3fbaa0] WARN - [HttpClient/HCl#16f5] HTTP error requesting GET https://107-198-4-66.4e3f9aafe1594300b25a46f7ae495052.plex.direct:0/identity (3, URL using bad/illegal format or missing URL) ()
Nov 08, 2022 09:18:13.612 [0x7f90c69aa0] DEBUG - MyPlex: mapping state set to 'Mapped - Not Published'.
Nov 08, 2022 09:18:13.662 [0x7f90c69aa0] DEBUG - MyPlex: Last published value didn't change, we're done.
Nov 08, 2022 09:18:20.046 [0x7f9d3a9aa0] DEBUG - [EventSourceClient/pubsub/184.105.148.117:443] EventSource: Got event [data] '<Message host="184.105.148.81" port="443" command="startRelay"/>'
Nov 08, 2022 09:18:20.138 [0x7f9d3a9aa0] DEBUG - [EventSourceClient/pubsub/184.105.148.117:443] Relay: already have an active relay connection for this server
Nov 08, 2022 09:18:30.697 [0x7f9d5acaa0] DEBUG - [EventSourceClient/pubsub/184.105.148.117:443] EventSource: Got event [data] '<Message host="184.105.148.81" port="443" command="startRelay"/>'
6

I think you are right that Synology firewall is on, because if I try to access Plex directly through Syno the port does not work. How do I fix this?

I also see that remote access is not available outside my network. Provided it is secure, I would like it to be available. Is the issue within Synology that I need to correct?

7

In my system here, I turn it off.

My philosophy – If someone is on my LAN, it’s too late.

1 Like
8

Can you elaborate? I’m not sure if I understand.

Should I have remote access available outside of my network? And would that be ok for safety?

9

The layering (architecture) we all have:

  1. The ISP runs the main line down the street

  2. We all get modem/routers so we can connect

  3. That modem/router does two things
    – Modem = convert from coax/telephone/whatebevr ↔ Ethernet (fiber is slightly different but largely the same)
    – Router = What separates our LAN from the internet (WAN).

  4. The important part here is what the router does.
    – Creates our local network (10.x.x.x, 192/168.x.x)
    – Has a built-in firewall to protect us from the internet

  5. When we enable Remote Access
    – PMS can talk to the router portion and tell it to open a single port to allow remote access. This works because only PMS will be listening to that port. Further, The router is configured to “forward” the port to the IP address of the server and guaranteeing nothing else gets it accidentally
    – PMS can also skip those steps, allowing us to configure everything ourselves.

  6. After all configuring is done, as part of confirming Remote Access will work, PMS asks Plex.tv to test the connection
    – You see the initial “green” flash as you enable it (testing started)
    – If it turns red, Plex.tv has replied with a NO that the port isn’t open.

CAVEAT

Some modem routers will Start green, switches to red (as if failed), and later go back to green when PMS/Plex.tv cycle around again to confirm the port is still open.

Back to you

If you want to share your media server with family / friends, you are welcome to do so. You’re not required to leave it enabled if you don’t want it.

10

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