I’ll now go back and resume attempting to repair/optimise the database, and see where that gets me. Thank again.
Yes, those router settings are correct and do NOT need to be changed.
I don’t know what hole you pulled that IP Address (217.155.223.50) out of, but it was obviously wrong.
To confirm your NAS IP Address, go to DSM Control Panel > Info Center > Network tab and then look under LAN 1 > IP Address.
The image above shows Bond 1, this is because I have two Ethernet connections and they have been Bonded together into a single connection. That is why LAN 1 and LAN 2 are not shown.
If your LAN x connection shows an invalid IP Address (169.254.x.x) then that adapter is NOT connected.
If your valid IP Address (192.168.178.x) connection is not on LAN 1, then you need to put the Ethernet cable into Port 1 on the back of the NAS. I am assuming you have at least two Ethernet ports on your NAS.
So, your ssh command should look like this now:
ssh adminuser@192.168.178.x -p 15
You need to find the value for x as shown above.
That should at least connect you to the NAS using ssh.
That’s great info, thanks. I am most of the way through your our response, but everything connected to the NAS seems to be taking ages (like 5 minutes just to display the home page of DSM) so it does seem that there is a blockage somewhere.
More later 
Here are my DSM IP Address settings. It looks like the address is fixed, on 192.168.178.35 (Static IP)
Next, I will attend to the DBRepair process…
I hope everything is working as it should now?
Your NAS IP Address looks very good, try not to change that at all.
Let me know if you manage to run DBRepair.sh or not and the results if any.
Oh, I got an error: Permission denied, please try again.
I typed ssh adminuser@192.168.178.35 -p 15 . Terminal is asking me for adminuser@192.168.178.35’s password . The “ ‘s “ after 35 is new to me; is it significant? I am definitely in the right folder in PlexMediaServer (where DBRepair lives)
I know that Terminal doesn’t echo passwords to the screen.
When you enter the password you get “permission denied”?
Make sure the user is in the administrators group on the Synology NAS. See my earlier post for more info.
You previously told us that your adminuser name was cinerama21.
So why have you used adminuser when adminuser clearly needs to be substituted for the name of your NAS Admin User?
Pay attention to what you are doing and READ what is written for you, it will save us all some time.
Thank you for pointing that out! I have corrected it to my actual username, and the script is executing (“Automatic Check,Repair,Index started.”) So that’s good, all is hopefully alright now, at last I have been able to run DBRepair (relief!).
Aghh! Is it possible to undo the last thing you were doing? Before I came back to this thread earlier, Plex had been unexpectedly working, almost as good as it had been before all my connection issue started. I probably should have said that things were ok then, but I wanted to finish what I had originally started, but I did the DBRepair process anyway, which worked fine. Now, I am getting the ‘NAS is currently unavailable error, with those yellow/orange warning signs on all my libraries.
Many thanks for your continued patience…
-
Is Plex Media Server running?
-
From a PC on the same network as the NAS, point a browser at http://192.168.178.35:32400/identity.
You should see one line of XML with claimed=“0” (unclaimed) or claimed=“1” (claimed).
If unclaimed, you need to claim the server. -
From a PC on the same network as the NAS, point a browser at http://192.168.178.35:32400/web (you may need to use https). Login and click on the wrench icon (settings). Can you reach the server settings?
I am glad you were finally able to run DBRepair. Now that is done, you should not be having any issues with Plex itself.
Reboot your modem/router and everything connected to it, including any wireless devices.
Please follow the instructions given by @FordGuy61 and let him know what you found etc.
Since your current issue seems to be focused on your network, try turning off one device that is constantly connected to your network and monitor things for a few days at least.
If nothing bad happens, then turn that device back on and turn off another device that is constantly connected to your network.
Keep doing that until you can narrow down a possible cause for your ~frequent network issues.
Of course the problem could be with your internet connection or the router itself, but hopefully the culprit will reveal itself while you are testing.
Hi, thanks for this. I tried with both of the URLs that FordGuy61 specified, but they both generated an error, ‘Can’t connect to the server’. However, removing what is after the IP address of the NAS worked as expected (i.e. just the http://192.168.178.35), displaying the log-in screen of DSM. The error was the same trying to use https and one a variety of devices and browsers.
Next, I am going to implement trumpy81 suggestions with a view to sorting out my network issues. Why do you think that Plex “came back to life” a few days ago (before I broke it again 
If the URL’s that @FordGuy61 provided, did not work, it probably means that Plex Media Server is NOT running on your NAS.
You need to check in DSM Package Center > Installed > Plex and make sure it is running before you use those URL’s.
I am thinking that something (a device) in your network is intermittently causing all manner of problems on your network.
If you can narrow down which device that is, then you can take steps to eliminate that device from your network and hopefully solve your Plex issues in the process.
It’s a long shot, but worth looking into at least.
Shazam! That seems to have worked; I restarted every device on my network, checked in DSM Package Center that the server was working (it wasn’t) and lo and behold things appear to have returned. Even though I have no memory of doing it, the server getting turned off (possibly) must have happened after the last time I had things running smoothly, and before I did DBRepair.
I will still run DBRepair, now that I know even more what to watch for. I’ll keep an eye on how Plex is running. Once again, many, many thanks for all your help.
Before you run the DBRepair automatic option (Menu item 2), you must stop the server (Menu item 1) and after the automatic option runs, then you must restart the server (Menu item 7).
You probably forgot to do the latter.
In any case, I am glad things seem to be working for you once again, but do keep an eye on your network and if you spot anything that seems out of the ordinary, please let us know.
Happy Plexing!
Hello, I have got myself into a slight pickle inside Terminal with DBRepair, even though I’ve run it before, using your previous instructions. My most recent output from Terminal says:
“ bash-3.2# chmod +x DBRepair.sh
bash-3.2# ./DBRepair.sh
grep: /proc/1/cgroup: No such file or directory
grep: /proc/1/cgroup: No such file or directory
grep: /proc/1/cgroup: No such file or directory
grep: /proc/1/cgroup: No such file or directory
Error: Unknown host. Current supported hosts are: QNAP, Syno, Netgear, Mac, ASUSTOR, WD (OS5), Linux wkstn/svr, SNAP, FreeBSD 14+
Current supported container images: Plexinc, LinuxServer, HotIO, & BINHEX
Manual host configuration is available in most use cases.
Are you trying to run the tool from outside the container environment? Manual mode is available. Please see documentation. “
The line about the container environment has foxed me. Many thanks.
Not sure why DBRepair is not running correctly.
FYI, chmod sets file permissions. You do not need to use it every time. Only when first downloading the file.
Let’s try downloading a new copy of DBRepair and see if that helps.
- SSH to the NAS and navigate to the directory with DBRepair.
- Issue the
sudo bashcommand to become root. - Download a new copy of DBRepair:
You can copy/paste these commands. In Terminal on a Mac, if Command-V does not work, try a right mouse click to paste.
# Rename existing DBRepair.sh
mv DBRepair.sh DBRepair.sh.old
# Download latest version
wget -O DBRepair.sh https://github.com/ChuckPa/PlexDBRepair/releases/latest/download/DBRepair.sh
# Make it executable
chmod +x DBRepair.sh
# Run it
./DBRepair.sh
This is how it looks on my Synology running DSM 7.2.2:
DBRepair download
bash-4.4#
bash-4.4# mv DBRepair.sh DBRepair.sh.old
bash-4.4#
bash-4.4# wget -O DBRepair.sh https://github.com/ChuckPa/PlexDBRepair/releases/latest/download/DBRepair.sh
--2025-12-10 12:49:44-- https://github.com/ChuckPa/PlexDBRepair/releases/latest/download/DBRepair.sh
Resolving github.com... 140.82.114.3
Connecting to github.com|140.82.114.3|:443... connected.
<< a lot of lines deleted >>
Saving to: 'DBRepair.sh'
DBRepair.sh 100%[==========================================================>] 79.79K --.-KB/s in 0.002s
2025-12-10 12:49:45 (41.1 MB/s) - 'DBRepair.sh' saved [81708/81708]
bash-4.4#
bash-4.4# chmod +x DBRepair.sh
bash-4.4#
bash-4.4# ./DBRepair.sh
Database Repair Utility for Plex Media Server (Synology (DSM 7))
Version v1.13.02
Select
1 - 'stop' - Stop PMS.
2 - 'automatic' - Check, Repair/Optimize, and Reindex Database in one step.
3 - 'check' - Perform integrity check of database.
4 - 'vacuum' - Remove empty space from database without optimizing.
5 - 'repair' - Repair/Optimize databases.
6 - 'reindex' - Rebuild database indexes.
7 - 'start' - Start PMS
8 - 'import' - Import watch history from another database independent of Plex. (risky).
9 - 'replace' - Replace current databases with newest usable backup copy (interactive).
10 - 'show' - Show logfile.
11 - 'status' - Report status of PMS (run-state and databases).
12 - 'undo' - Undo last successful command.
21 - 'prune' - Remove old image files from PhotoTranscoder cache & all temp files left by PMS.
23 - 'deflate' - Deflate a bloated PMS main database.
42 - 'ignore' - Ignore duplicate/constraint errors.
88 - 'update' - Check for updates.
98 - 'quit' - Quit immediately. Keep all temporary files.
99 - 'exit' - Exit with cleanup options.
Enter command # -or- command name (4 char min) :
I can see the machine is using DSM 7.3.2-0
When are you are at the SSH command line, type this command and you should replicate my results.
bash-4.4# cat /proc/1/cgroup
9:devices:/
8:cpuacct:/
7:blkio:/
6:freezer:/
5:cpu:/
4:memory:/
3:cpuset:/
2:name=synomonitor:/
1:name=systemd:/
bash-4.4#
The biggest difference I immediately see is the bash command prompt.
You have: bash-3.2
I have: bash-4.4
DSM 7.3.2 uses bash ver 4.4
Is this a virtual DSM ?
