Same here as with others, reboot solved the issue: I did reboot it earlier, but this second one did the trick and I can now access my library again.
Same here.
Synology DS415play server not registering as device on Plex App
Same here with Synology DS218+ and a friend of mine has also the same problem also with DS218+. It suddenly stopped working.
Same here restarting the plex server package was not “enough”, restarting the nas and plex server was online again. (Ds218+)
Same here, I rebooted the NAS (Synology) and player, and router just in case, and I still can’t connect.
Everyone,
I would like to ask if you’ll take the following steps to reestablish your Synology systems.
- Plex/web browser - Upper right corner - Sign out of your Plex account.
- Restart Plex on the Syno
- Wait the typical 30-45 seconds for it to get settled with Plex.tv
- Open an Incognito browser window
- Connect to http://LAN.IP.of.syno:32400/web
- Sign-in
- Claim again if needed but should auto reclaim.
If if fails to sign in and reestablish itself, please stop Plex and manually collect the Logs directory (from the Plex share) in a ZIP and attach here for me.
Still no progression over here. Rebooted my Synology, restarting Plex server package, also deleted Plex server package and installed it again. And deleted and installed Plex media player at my Samsung again. Nothing seems to work.
And the Plex team acts as if the problem has been solved. As far as I may believe their website. 
We simul-posted. Please read above your post.
All
Uninstalling/reinstalling the package will have no impact on the configuration/ account state because it’s stored separately in the Plex share with your metadata.
If I may respond to the comments about nobody from Plex caring,
I hope you all know I do care but am but one person and I spent most of the day yesterday rebuilding my entire system (desktop) from scratch after Fedora had a major blowout.
I spent 12+ hours trying to put Ubuntu on the machine and use partitions like I have on Redhat. It failed miserably.
VMware is gone and unknown if/when I’ll get that back. I got VirtualBox running last night.
I knew of what was happening here but in no position to help.
I’ll be working today and throughout the weekend to clear the backlog of 200+ tickets in addition to working here in the forums.
I have had somewhat of the same issue for about a week or so. I am running on a Synology 218+ and running Plex 1.18.5.2309-f5213a238. I will open https://app.plex.tv/desktop which I have been doing since the install of over 1.5 years ago and I get the explanation points for the server. I am on the same network. I restart the service in Synology and it comes back. A few hours later, it is gone again. I just was watching a show, finished the show, closed back to the main menu and it is not available. Something other than the outage the other day is an issue.
Followed these steps. Server still not registered in devices.Logs.zip (5.2 MB)
Please don’t work too much overtime 
I think some of the frustration is that there doesn’t seem to be any strong mandate on the Plex dev team to make sure the core server functionality works when there’s not internet access and/or no plex.tv services available. Every time there’s a Plex service outage (it’s not often but it happens), or an internet service outage on our end (it varies), we run into issues like these because somehow Plex Server has too many hooks and reliance on plex.tv access… The core feature of Plex is “you can play your media at home”, so this should work as long as our LAN is up. If internet or plex.tv are down, we should lose access to logical stuff like friend accounts and server sharing and all that… I feel like somehow along the way Plex’s codebase lost proper compartmentalization between what’s critical and what’s nice to have. So what I’d like to see isn’t Plex employees doing overtime – I’d like instead to see a change of dev policies in the next few months that assure us that Plex QA, build farms, testing procedures, and code reviews do include this consideration of critical vs non-critical features, in order to make sure (as much as possible) that this won’t happen again. On a purely anecdotal level, getting locked out of my Plex server happens around once a year.
2 Likes
Thanks for the logs.
I’m seeing a few things and would like to get this part resolved first:
- Which volume is PMS installed on? It seems to have lost track of the appstore.
Feb 07, 2020 13:00:11.364 [0x7f64cee1c700] DEBUG - File "/volume1/@appstore/Plex Media Server/Resources/Plug-ins-f5213a238" changed: -1 => 2020-01-23 17:47:34 (1579823254).
Feb 07, 2020 13:00:11.364 [0x7f64cee1c700] DEBUG - File "/volume1/Plex/Library/Application Support/Plex Media Server/Plug-ins" changed: -1 => 2018-12-15 17:46:37 (1544917597).
Feb 07, 2020 13:00:11.365 [0x7f64cee1c700] DEBUG - Scanning for plug-ins in "/volume1/@appstore/Plex Media Server/Resources/Plug-ins-f5213a238"
Feb 07, 2020 13:00:11.411 [0x7f64cee1c700] DEBUG - Scanning for plug-ins in "/volume1/Plex/Library/Application Support/Plex Media Server/Plug-ins"
- Codec download failure -
Feb 07, 2020 13:00:42.248 [0x7f64dcd04700] DEBUG - HTTP simulating 408 after curl timeout
Feb 07, 2020 13:00:42.248 [0x7f64dcd04700] ERROR - Codecs: Failed to download XML for codec 'mpeg4_decoder'
Feb 07, 2020 13:00:42.248 [0x7f64dcd04700] WARN - Codecs: Failed to download mpeg4 decoder; bailing out
- Still unable to contact plex.tv
Feb 07, 2020 13:01:22.337 [0x7f64cdc88700] WARN - Sync: Couldn't get sync lists without subscription.
Feb 07, 2020 13:01:22.338 [0x7f64cdc88700] DEBUG - HTTP requesting GET https://plex.tv/api/v2/features?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx
Feb 07, 2020 13:01:23.205 [0x7f64cf10a700] ERROR - Error issuing curl_easy_perform(handle): 28
Feb 07, 2020 13:01:23.205 [0x7f64cf10a700] DEBUG - HTTP simulating 408 after curl timeout
Feb 07, 2020 13:01:23.206 [0x7f64cf10a700] ERROR - Error parsing content.
Feb 07, 2020 13:01:23.206 [0x7f64cf10a700] ERROR - Error parsing XML: Error parsing file.
Further down, I see general connectivity issue:
192.168.1.199:32400&httpsEnabled=1&httpsRequired=0&dnsRebindingProtection=1&natLoopbackSupported=0&X-Plex-Token=xxxxxxxxxxxxxxxxxxxx
Feb 07, 2020 13:03:48.113 [0x7f64dca16700] ERROR - getaddrinfo(192-168-1-199.abcdefghijklmnopqrstuvwxyz012345.plex.direct) failed: -3
Feb 07, 2020 13:03:48.113 [0x7f64dca16700] DEBUG - Network: 192-168-1-199.abcdefghijklmnopqrstuvwxyz012345.plex.direct failed to resolve to 192.168.1.199 but instead yielded ""
Feb 07, 2020 13:03:48.113 [0x7f64dca16700] DEBUG - PublicAddressManager: Obtaining public address and mapping port.
Feb 07, 2020 13:03:48.113 [0x7f6498279700] DEBUG - PublicAddressManager: Obtaining public IP.
Feb 07, 2020 13:03:48.113 [0x7f64dca16700] DEBUG - EventSource: Successfully connected to 184.105.148.113.
Feb 07, 2020 13:03:48.113 [0x7f64dca16700] DEBUG - EventSource: Failure in IdleTimeout (0 - Success).
Feb 07, 2020 13:03:48.113 [0x7f64dca16700] DEBUG - MyPlex: We appear to have lost Internet connectivity, resetting device URL cache.
Feb 07, 2020 13:03:48.113 [0x7f64dca16700] ERROR - EventSource: Retrying in 15 seconds.
Feb 07, 2020 13:03:48.113 [0x7f6498279700] DEBUG - HTTP requesting GET http://plex.tv/pms/:/ip
Feb 07, 2020 13:03:56.514 [0x7f649a2b3700] ERROR - Error issuing curl_easy_perform(handle): 28
Feb 07, 2020 13:03:56.514 [0x7f649a2b3700] DEBUG - HTTP simulating 408 after curl timeout
Feb 07, 2020 13:03:56.514 [0x7f649a2b3700] WARN - MyPlex: Updating device connections failed, retrying in 10 seconds.
Feb 07, 2020 13:04:00.990 [0x7f649bfff700] DEBUG - MyPlex: Updating device connections (from timer: 1)
Which geographic region are you in ?
Re : Working too much overtime…
I’ll gladly let you sit in my chair if you’re volunteering?
2 Likes
Volume 1
Located in Texas
PlexMediaServer-1.18.5.2309
This is my current version
With it now working again and knowing:
- 1.18.5.2309 = old version of Plex/web bundled client
- 1.18.6.2368 = new version of Plex/web bundled client
Is this failure immediately reproducible by upgrading to the PlexPass beta version again?
If it is, I will act immediately to get this resolved because not everyone uses the hosted app at app.plex.tv and it doesn’t get as much hard use as the bundled does.
To help me, pulling the Web client logs in both cases is of GREAT help.
It gives me exactly what I need, showing success and showing failure, which I can take directly to them without further delay investigating.
I am having a similar issue. I did a fresh install and get the web ui to open. It tries, but fails to connect. Attached are my logs.Logs.zip (100.1 KB)
