Plex cant see media files on Synology NAS

Server Version#: 1.19.4.2935-79e214ead
Player Version#: 4.35.1
Synology NAS Model: DS1019+ Version: 6.2.3-25426-0
Plex: Version 4.35.1 1.19.4.2935-79e214ead (from authorized devices page)
NetGear Orbi AX3000 Router and satellites

Recent changes include an upgrade to synology and to plex versions within the last few days. I also have had issues lately with Synology Admin account, and even in restarting or shutting down the synology box. I suspect I have a permissions issue, but I’m in over my head.

Also made some changes trying to move to static IP address for the NAS. About 3 months ago i replaced my modem and router, which while not causing immediate problems did cause issues related to previous configuration items like making plex available outside the home. I attempted to secure static addresses for the NAS and the Roku, and to chsnge the pool of DHCP addresses. Later I undid these changes trying to get things working again.
In trying to reset my Synology Admin earlier in the week I pushed the reset only for the button to break off inside…not a great week :frowning:

The current facts:
synology assistant shows my NAS, and its ip address and DHCP status.

I can link to the media folders on the NAS, from my windows laptop and add and rename files as i wish, so i know they are there, just that in Plex and in Synology - I cant see them, or dont have permissions to them.

I can login to synology NAS

-First oddity is that the box on the lower right for “system Health” shows the server name, but the IP address and uptime are blank. The resource monitor looks fine.
-Second oddity is that clicking on “Shared Folder” within Synology - results in a lengthy “Processing Please wait” message followed by a blank page
-third oddity is that clicking on “User” , takes a long time to load. 4 Users appear the last being my login.
Results (not sure if this is important or not):
admin Disabled
guest Disabled
plex Normal
My ID Normal

I can log into plex from Roku, iOS, and windows browser. I get prompted for my pin code, and it opens up but with no local contect available (Movies, Music, Photos, playlist).
The message I see in the “Settings” is :Unable to connect to Yavin4 securely.
If I click on “Allow Insecure Connections”, I just get the message back, “The server Yavin4 does not allow secure connections”. When I pressed allow insecure connections, I received the message, “Yavin4 is currently unavailable”.

All Plex apps (Windows, Roku & iOS) function but dont show my content. Local users are prompted for PINS, and enter application. When clicking on movies I receive the message “Unable to connect to “Yavin4” securely”.

I turned debug on and received the following:

Summary

{
“type”: “log:message”,
“level”: 4,
“message”: “[Commands] Executing testServerConnection”,
“time”: “2020-06-14T11:01:55.387Z”
},
{
“type”: “log:message”,
“level”: 4,
“message”: “[Connections] Retrying connection tests for Yavin4 in 28 seconds”,
“time”: “2020-06-14T11:01:55.387Z”
},
{
“type”: “log:message”,
“level”: 4,
“message”: “[Connections] Retrying server events connection for Yavin4 in 28 seconds”,
“time”: “2020-06-14T11:01:55.387Z”
},
{
“type”: “log:message”,
“level”: 4,
“message”: “[Connections] Testing connection for Yavin4 at https://192-168-1-2.03d07443aeb34bd8bf6cd08446f2f5eb.plex.direct:32400/media/providers”,
“time”: “2020-06-14T11:01:55.451Z”
},
{
“type”: “log:message”,
“level”: 4,
“message”: “[Connections] Testing connection for Yavin4 at https://73-145-236-179.03d07443aeb34bd8bf6cd08446f2f5eb.plex.direct:23299/media/providers”,
“time”: “2020-06-14T11:01:55.459Z”
},
{
“type”: “log:message”,
“level”: 4,
“message”: “[Connections] Testing connection for Yavin4 at https://172-105-21-56.03d07443aeb34bd8bf6cd08446f2f5eb.plex.direct:8443/media/providers”,
“time”: “2020-06-14T11:01:55.466Z”
},
{
“type”: “log:message”,
“level”: 1,
“message”: “[Connections] Yavin4 is unavailable at https://73-145-236-179.03d07443aeb34bd8bf6cd08446f2f5eb.plex.direct:23299/media/providers (Status 0)”,
“time”: “2020-06-14T11:02:03.819Z”
},
{
“type”: “log:message”,
“level”: 1,
“message”: “[Connections] Prevented fallback to insecure connection for Yavin4”,
“time”: “2020-06-14T11:02:03.824Z”
},
{
“type”: “ajax”,
“url”: “https://73-145-236-179.03d07443aeb34bd8bf6cd08446f2f5eb.plex.direct:23299/media/providers?X-Plex-Product=Plex%20Web&X-Plex-Version=4.35.1&X-Plex-Client-Identifier=hktvuutwkp9p626fa7xj5hjq&X-Plex-Platform=Firefox&X-Plex-Platform-Version=77.0&X-Plex-Sync-Version=2&X-Plex-Features=external-media%2Cindirect-media&X-Plex-Model=hosted&X-Plex-Device=Windows&X-Plex-Device-Name=Firefox&X-Plex-Device-Screen-Resolution=1920x938%2C1920x1080&X-Plex-Token=TOKEN-vLzaC9zgwjY&X-Plex-Language=en”,
“status”: 0,
“headers”: {
“Accept-Language”: “en”,
“Accept”: “application/json”
},
“statusText”: “error”,
“time”: “2020-06-14T11:02:03.825Z”
},
{
“type”: “log:message”,
“level”: 1,
“message”: “[Connections] Yavin4 is unavailable at https://192-168-1-2.03d07443aeb34bd8bf6cd08446f2f5eb.plex.direct:32400/media/providers (Status 0)”,
“time”: “2020-06-14T11:02:06.007Z”
},
{
“type”: “log:message”,
“level”: 1,
“message”: “[Connections] Prevented fallback to insecure connection for Yavin4”,
“time”: “2020-06-14T11:02:06.010Z”
},
{
“type”: “ajax”,
“url”: “https://192-168-1-2.03d07443aeb34bd8bf6cd08446f2f5eb.plex.direct:32400/media/providers?X-Plex-Product=Plex%20Web&X-Plex-Version=4.35.1&X-Plex-Client-Identifier=hktvuutwkp9p626fa7xj5hjq&X-Plex-Platform=Firefox&X-Plex-Platform-Version=77.0&X-Plex-Sync-Version=2&X-Plex-Features=external-media%2Cindirect-media&X-Plex-Model=hosted&X-Plex-Device=Windows&X-Plex-Device-Name=Firefox&X-Plex-Device-Screen-Resolution=1920x938%2C1920x1080&X-Plex-Token=TOKEN-vLzaC9zgwjY&X-Plex-Language=en”,
“status”: 0,
“headers”: {
“Accept-Language”: “en”,
“Accept”: “application/json”
},
“statusText”: “timeout”,
“time”: “2020-06-14T11:02:06.011Z”
},
{
“type”: “log:message”,
“level”: 1,
“message”: “[Connections] Yavin4 is unavailable at https://172-105-21-56.03d07443aeb34bd8bf6cd08446f2f5eb.plex.direct:8443/media/providers (Status 0)”,
“time”: “2020-06-14T11:02:06.014Z”
},
{
“type”: “log:message”,
“level”: 1,
“message”: “[Connections] All connections to Yavin4 failed”,
“time”: “2020-06-14T11:02:06.015Z”
},
{
“type”: “log:message”,
“level”: 4,
“message”: “[Servers] Found all servers = plex.tv”,
“time”: “2020-06-14T11:02:06.017Z”
},
{
“type”: “ajax”,
“url”: “https://172-105-21-56.03d07443aeb34bd8bf6cd08446f2f5eb.plex.direct:8443/media/providers?X-Plex-Product=Plex%20Web&X-Plex-Version=4.35.1&X-Plex-Client-Identifier=hktvuutwkp9p626fa7xj5hjq&X-Plex-Platform=Firefox&X-Plex-Platform-Version=77.0&X-Plex-Sync-Version=2&X-Plex-Features=external-media%2Cindirect-media&X-Plex-Model=hosted&X-Plex-Device=Windows&X-Plex-Device-Name=Firefox&X-Plex-Device-Screen-Resolution=1920x938%2C1920x1080&X-Plex-Token=TOKEN-vLzaC9zgwjY&X-Plex-Language=en”,
“status”: 0,
“headers”: {
“Accept-Language”: “en”,
“Accept”: “application/json”
},
“statusText”: “timeout”,
“time”: “2020-06-14T11:02:06.020Z”
},
{

Not sure if its relevant but when this occurred - I had created a folder for prerolls (by just creating a folder by right-clicking - not creating a share), in the extras i was typing the address of this folder when - everything stopped working. This could just be another issue - as I have had problems the last several days as noted above.

I have done as you suggested. Do you think reinstalling DSM is the only way forward? Will I need to buy a new Synology device to do that given the broken switch?

Thanks for your suggestion! Synology shipped me a new device under warranty. It will arrive this AM. Any suggestions for moving forward that will help on the Plex side (Keep the same device name & IP Address)?

Ok nas is running again and I installed Plex, and it looked good until I noticed a newer version and applied that update. Plex says the server is unreachable. Before that it said something about an unsecured nonencrypted connection and I said ok. Always. Currently on version 4.36.1 on Synology nas 1019+.

I can see the Plex shared folder and from file station can see all the files are intact. When I go the package center the Plex media server button says run. When I click on it. It says loading… and the the button shows as open.

thought all was good and then received a checksum error…

Checksum mismatch on file [/volume1/Plex/Library/Application Support/Plex Media Server/Plug-in Support/Databases/com.plexapp.plugins.library.db].

I do have NAS rated drives. i ran the quick smart tests and they all came out healthy. looks like last night many more check sum errors, and auto reboots. This morning the status light is green but all the drive lights are flashing and synology assistant doesnt see the NAS. If i reboot (again), how does one uninstall the plex application? I had used the new edge browser for the download. I’ll use Firefox the next time.

ok - after a lot of work - I got my NAS working again and the volume rebuilt. replaced one drive, reinstalled DSM. All drives show healthy after running extended scan on each of them (Seagate Red Wolf NAS 8TB).

Everything looking like it had returned to normal, I noticed Plex was not showing as an installed app, even though the library was still there. I attempted a manual install of the intel 64 bit version.

From the log it looks like it installed and then triggered a checksum error again.

Reading your notes above, I then stopped and

  1. uninstalled the app,
  2. Deleted the plex user.
  3. I want to make sure I understand what your asking. Delete the shared folder with all of the libraries and media content? or just the library directory?

BTW: I am using Firefox browser.

You were right - glad you caught that. When I started the NAS and installed Plex it was all new to me. I’m not sure how they got the way they did - but the media files were in the Plex Shared folder. Ive created a separate share and moved the media files over, before deleting the Plex share.

So I have installed Plex, but it doesnt see my existing content. Can you point me to the next steps to link my content in the media folder (movies, music, pictures etc.) to Plex

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