Hi,
Since recently, every day now: Plex does not find my server on my Synology NAS.
The NAS is connected, but no connection with Plex…
A restart of my NAS does the thing.
I guess it started with the latest Plex-update.
Is there a solution for this problem?
The rest of my family does not know how to restart the NAS and it’s no fun to have to restart it every day…
THX for the support!
Greetings
What do you mean by that?
Can you access your server using its local IP address → http://[syno ip address]:32400/web
That I can access the NAS and the files, but Plex can’t connect…
No access with the local IP address.
I tried to connect at home.
I suppose you could attempt to restart the Plex Media Server package on your Syno… though that won’t make things much easier for your family.
Did you already have a look a the server logs to see if there’s some critical errors / crashes reported?
Plex Media Server package already restarted.
Didn’t solve the problem.
Server logs give some errors…
But goes to the next after this…
Feb 16, 2022 08:26:44.753 [0x7fe1aa410b38] WARN - Waited one whole second for a busy database.
Feb 16, 2022 08:26:46.976 [0x7fe1aa410b38] WARN - Waited one whole second for a busy database.
Feb 16, 2022 08:26:49.200 [0x7fe1aa410b38] WARN - Waited one whole second for a busy database.
Feb 16, 2022 08:26:51.423 [0x7fe1aa410b38] WARN - Waited one whole second for a busy database.
Feb 16, 2022 08:26:53.648 [0x7fe1aa410b38] WARN - Waited one whole second for a busy database.
Feb 16, 2022 08:26:55.870 [0x7fe1aa410b38] WARN - Waited one whole second for a busy database.
Feb 16, 2022 08:26:58.092 [0x7fe1aa410b38] WARN - Waited one whole second for a busy database.
Feb 16, 2022 08:27:00.314 [0x7fe1aa410b38] WARN - Waited one whole second for a busy database.
Feb 16, 2022 08:27:02.536 [0x7fe1aa410b38] WARN - Waited one whole second for a busy database.
Feb 16, 2022 08:27:04.758 [0x7fe1aa410b38] WARN - Waited one whole second for a busy database.
Feb 16, 2022 08:27:06.980 [0x7fe1aa410b38] WARN - Waited one whole second for a busy database.
Feb 16, 2022 08:27:09.202 [0x7fe1aa410b38] WARN - Waited one whole second for a busy database.
Feb 16, 2022 08:27:11.424 [0x7fe1aa410b38] WARN - Waited one whole second for a busy database.
Feb 16, 2022 08:27:13.675 [0x7fe1aa410b38] WARN - Waited one whole second for a busy database.
Feb 16, 2022 08:27:15.898 [0x7fe1aa410b38] WARN - Waited one whole second for a busy database.
Feb 16, 2022 08:27:18.122 [0x7fe1aa410b38] WARN - Waited one whole second for a busy database.
Feb 16, 2022 08:27:20.346 [0x7fe1aa410b38] WARN - Waited one whole second for a busy database.
Feb 16, 2022 08:27:22.570 [0x7fe1aa410b38] WARN - Waited one whole second for a busy database.
Feb 16, 2022 08:27:24.792 [0x7fe1aa410b38] WARN - Waited one whole second for a busy database.
Feb 16, 2022 08:27:27.014 [0x7fe1aa410b38] WARN - Waited one whole second for a busy database.
Feb 16, 2022 08:27:28.220 [0x7fe1aa410b38] ERROR - Error refreshing item MovieName (sqlite3_statement_backend::loadOne: database is locked)
Feb 16, 2022 08:27:28.221 [0x7fe1aa410b38] DEBUG - Matching ‘Enemy of the State’ (ID 56576) with agent com.plexapp.agents.imdb
Plex Media Server version?
Is the Synology running DSM 6 or DSM 7?
What do you see when you try connecting directly to the server? http://server_ip_address:32400/web
Use a private/incognito window to bypass browser add-ons.
I use DSM 7 with Media Server 4.59.2.
Like I sad, it is not always that het can’t find the server. A reboot of my Synology Nas is the solution, but it is not the idle solution…
My MacBook opens the page without a problem, it’s just the server he can’t find.
The problem occurs also on my other devices: Apple TV.
So I guess the problem is not my MacBook.
I recommend reinstalling the package using the “Plex Claim Token” option.
This method handles lost servers (not found) too
Gave it a go… waiting for the result of it…
Ill keep you posted…
THX!!!
Today the same problem.
I closed the Plex app on my Synology and restarted it and the server was found again…
I guess it’s a bug in the app.
Before I had never this problem.
There’s something else going on there; we just need to find it.
Please have DEBUG server logging enabled.
If/when it does it again, grab the server logs ZIP (after you restart)
and attach it here please.
OK, will do…
There is a new server update.
I hope that will fix it…
Since the new update… no problems anymore… 
I thank for the great support! 
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
