My PMS is no longer showing in Plex settings

Server Version#: 1.29.06219-7000
Player Version#: All plex client supports

Hi, i’ve got a big issue with PMS. I’m on a Synology D220+ with DSM7, since this afternoon everything was working fine but now for a reason I can’t access anymore my server from the client side of Plex. He just vanished like this :confused:
I tried everything i found on you documentation and on the web in general, disabled the VPN on my NAS, set back originales DNS, my firewall also alrdy has plex port opened same for my router.

I’m out of solutions and this is why I’m asking for help here :slight_smile: i’m sorry if this is not the right place for it !

I’m giving you my logs, thanks you in advance for your time :slight_smile:
Logs.zip (952.4 KB)

Those logs show quite a number of errors (aside of tons of verbose messages – which you obviously cannot disable while you cannot access the server settings… just giving me a headache anyway).

  1. There seems to be some permission issues (at least for the library linked to /volume1/photo/) – probably not related to your issue
  2. Plex doesn’t seem to like the device name you’ve assigned to your server (I guess because of the Unicode character / emoticon

In addition to the items @tom80H mentions, check the NAS network connection, including the Ethernet cable, any switch ports, etc. If you have changed the MTU size, return it to the default (uncheck Set MTU value manually in DSM Control Panel → Network)

There are several hundred Network change messages in the log file.

Sep 21, 2022 23:04:00.489 [0x7f454fbebb00] DEBUG - Network change.
Sep 21, 2022 23:04:00.489 [0x7f454fbebb00] DEBUG - NetworkInterface: Notified of network changed (force=0)
Sep 21, 2022 23:04:00.489 [0x7f454fbebb00] DEBUG - Network change notification but nothing changed.
Sep 21, 2022 23:04:00.489 [0x7f454fbebb00] DEBUG - NetworkInterface: received Netlink message len=1224, type=RTM_NEWLINK, flags=0x0
Sep 21, 2022 23:04:00.489 [0x7f454fbebb00] DEBUG - NetworkInterface: Netlink information message family=0, type=1, index=10, flags=0x1002, change=0xffffffff

A runaway DHCP server or being on the edge of a WiFi can also create these messages

Thank you all for yours answers, it seems that the server start working again by his own… Don’t really understand the behavior but I guess it’s okay now !
I’m gonna look up the warning you guys told me (about the name and everything) :slight_smile:

Again, huge thanks for your time, much appreciated :wink:

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