PMS not opening from Synology NAS: network connection unexpectedly broken

Plex Media Server NAS & Devices
,
1

Server Version#: 4.98.2
Player Version#:

Hello,
I am using a Mac with a DS918+ Synology NAS. Up till now everything worked fine, but after the update of SMB service, I no longer can open PMS on my NAS. PMS can be opened from the Plex website though.
I get the message “Safari cannot open page (my Quick connect link from Synology) because the network connection was unexpectedly lost.”
Streaming onto Plex clients works fine.
After reinstalling DSM7 again, the problem still remains.

Any ideas where to look?

thanks for helping me :pray:

2

Stop Plex

Using FileStation

  1. Open PlexMediaServer
  2. navigate in until you see “Logs”
  3. RIght-click “Logs” → “Compress to Logs.zip”
  4. Download the ZIP file
  5. Attach here
3

Ok, Logs are in attachment.
Logs.zip (1.7 MB)

4

@Tommmy

is PMS running when you grabbed the logs ?

They were cut off at the bottom?

5

I am not running PMS as far as I know, I reattached the logs. The Synology DSM is at the startup screen, so no PMS is open (since I can not open it anyway).
Logs.zip (1.7 MB)

6

Package Center → Plex → “Running” ???

Your logs changed so even if ‘closed’ , it does look like it’s running.

7

how can I ‘close’ PMS then within DSM?

8

See the “Open” ? Next to it is an arrow. Click it, it opens → Stop

Screenshot from 2023-01-14 09-38-00
Screenshot from 2023-01-14 09-38-00771×355 27.7 KB

9

got it. Here you are :palm_up_hand:
Logs.zip (1.7 MB)

10

First thing I see.

You have both network adapters plugged in and on the same network.
This will confuse PMS ( actually confuses the secure connections )

Do you have a switch capable of bonded service (using 2 adapters as if one) ?

If not, then choose which adapter (IP address) you don’t want to use and unplug it.
After doing that, restart the Syno.

Jan 14, 2023 09:09:10.350 [0x7f4859b570d0] DEBUG - Detected primary interface: 192.168.0.218
Jan 14, 2023 09:09:10.350 [0x7f4859b570d0] DEBUG - Network interfaces:
Jan 14, 2023 09:09:10.350 [0x7f4859b570d0] DEBUG -  * 1 lo (127.0.0.1) (00-00-00-00-00-00) (loopback: 1)
Jan 14, 2023 09:09:10.350 [0x7f4859b570d0] DEBUG -  * 3 eth0 (192.168.0.218) (00-11-32-8A-1A-E5) (loopback: 0)
Jan 14, 2023 09:09:10.350 [0x7f4859b570d0] DEBUG -  * 4 eth1 (192.168.0.119) (00-11-32-8A-1A-E6) (loopback: 0)
Jan 14, 2023 09:09:10.350 [0x7f4859b570d0] DEBUG -  * 1 lo (::1) (00-00-00-00-00-00) (loopback: 1)
Jan 14, 2023 09:09:10.350 [0x7f4859b570d0] DEBUG -  * 3 eth0 (2a02:1811:b134:d500:211:32ff:fe8a:1ae5) (00-11-32-8A-1A-E5) (loopback: 0)
Jan 14, 2023 09:09:10.350 [0x7f4859b570d0] DEBUG -  * 4 eth1 (2a02:1811:b134:d500:211:32ff:fe8a:1ae6) (00-11-32-8A-1A-E6) (loopback: 0)
Jan 14, 2023 09:09:10.350 [0x7f4859b570d0] DEBUG - Creating NetworkServices singleton.
Jan 14, 2023 09:09:10.350 [0x7f4859b570d0] DEBUG - NetworkServices: Initializing...
11

this is correct; I have 2 UTP cables connected to the NAS in bond mode, Ipv4 is in manual mode. First I will try to unplug 1 cable and restart. I use the bond mode since it has improved speeds.

12

hi Chuck, I unplugged 1 cable and restarted the NAS. But, still no PMS and the same original message. For your convenience, I attached the Logs as well.
Logs.zip (1.7 MB)

13

Looking at the logs now, I see you found bond0 . That’s the better option if you can do it.

After recreating bond0.

  1. restart DSM
  2. Uninstall PMS (use the KEEP option)
  3. Reinstall the same PMS version SPK again --EXCEPT
    – Use the “New or Lost” (Claim Token option)
    – Get the claim token via the link
    – PASTE it into the window
    – Click NEXT NEXT DONE
  4. Confirm it reports your username as the Claimed by:

Now things will work.

14

Thanks a lot Chuck!! You REALLY helped me here. Thumbs upp :+1: :+1: :+1:

15

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