That account appears too be a member of the admin group, as you say. I will go back over your instructions and see what happens. I have noticed an odd thing, in that if I am unable to play a movie with the Amazon Fire Plex app (which is usually the case, especially early in the day), I close it and start up the Panasonic Plex app where I can play the file fine. If I then return to the Amazon Fire version,I am now able to play the movie.
I’ve been going over my settings afresh, but I have run into an unexpected issue, responding to your message entitled ‘NAS Settings’ above. In Synology Control Panel → Network → Network Interface
I only have LAN (Connected) and PPPoE (Disconnected), I don’t have Network Address, Subnet Mask, Gateway or DNS Server.
I wanted to try and get this sorted before I do anything else. Anyway, the NAS is indeed synchronised with a public server (time.google.com)
If the NAS is synchronized to a NTP server, then the network connection is almost always OK. I ask people to do that because (a) it is a good thing for NAS operations, and (b) it is a basic check of Internet connectivity.
To display/edit the address, etc. edit the connected network interface.
Example: My Synology NAS
I’ve a simple network, only one router, no VLANs, etc. The gateway is the address of the ISP supplied router.
Should I input 192.168.178.35 into the IP address field? FordGuy61, you previously identified that IP address as mine (“192.168.178.35 per your log files”). Thanks.
I put that address into the IP field. Restarting Plex, I now have no access to any media at all (“No content available”). I wonder if you have any ideas where I can go next? Thank you.
Additionally, today I have had an ‘At Risk’ warning generated by DSM>Security Advisor (see screenshots). I have no idea what all that means TBH. Is it something to be concerned over? It’s quite alarming.
Mystifyingly, my media is now accessible again, although only on 2 devices/Smart TV’s. So the issues continue, seemingly without end.
FordGuy61, I am going to try and finally complete DBRepair this week.
If you study the image you posted carefully, you may notice at the bottom it lists the issue that caused the alert.
Go to DSM Control Panel > Terminal & SNMP and change the default SSH port number (22), to another 2 digit number E.G. 23.
And remember that when logging in via SSH you will need to add -p 23 to the end of your log in command in terminal/PuTTy.
E.G. ssh myadmin@192.168.0.22 -p 23.
In this case, -p = the port number you chose above.
Also, I would recommend that you reboot your modem/router and everything connected to it, including any wireless devices. That should clear any DNS Cache corruption that may be contributing to your issues.
Marvellous 
I changed the default SSH port number to 24 (23 was being used by something) and managed to log in (I think) - well the cursor is green now, quite a relief I must say. I’ve attached a screenshot in celebration.
Given that my original aim was to run DBRepair, do we think that it’s achievable from where I’ve got to? Thank you for all your support.
Absolutely, it’s possible.
I would save Chuck’s DBRepair script somewhere in volume1 (accessible from File Station), but NOT in the PlexMediaServer folder.
CD to it’s location and chmod -x etc. to make the script executable and then run the script as per Chuck’s instructions.
That should clean up your database and make sure it’s running as well as it can.
All my media has become invisible to Plex (“NAS is currently unavailable” - it’s not). It was fine yesterday. Nonetheless, I will try and give DBRepair a go. I have relocated the file to a different part of my NAS, as you suggested. My biggest challenge is how to CD too it’s new location (easy with a graphical interface of course…)
Do you think that DBRepair will iron out some of these problems? I would dearly love to be able to watch my stuff once again.
Sounds like you have a network issue that you may need to address. Try rebooting the modem/router and everything connected to it and then restart Plex and try opening Plex/Web using http://NAS-IP-ADDRESS:32400.
At the SSH prompt enter:
cd /address/to/the/file
E.G.
cd /volume1/Files/ (changing directory to)
chmod +x DBRepair.sh (making the file executable)
./DBRepair.sh (running the file)
Make sure you replace the file address with the actual file address on your system and do not include the text in parenthesis above.
That’s great, thanks.
So I’ve located DBRepair.sh on my NAS inside Terminal. So that’s progress. I typed CD and dragged the NAS folder from the Finder to the Terminal window, and hit return:
Mac:Volumes baward$ cd /Volumes/home/2025
Mac:2025 baward$ ls
DBRepair.sh
Goughs Transfer Of Equity receipt.pdf
Goughs Xfer EquityYour X-Press Legal Services receipt [#1084-2571].pdf
Now, to actually do something with DBRepair.sh, as described above.
Please can you explain what this command means, and how I go about using it - “chmod -x etc.” especially the -x etc. bit? I know that chmod means change the access permissions of files and directories (thanks AI) I am assuming that x refers to to the file DBRepair.sh?
+x tells chmod to set the executable bit for the file, DBRepair.sh in this case.
The command to use is:
chmod +x DBRepair.sh
You want to add the executable bit, not remove it with -x.
HTH
Thanks, it did help. I think I am getting close, but there are still some problems. I ran chmod and then the file but it generated the following, which I don’t understand:
“Mac:2025 baward$ chmod +x DBRepair.sh
Mac:2025 baward$ ./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.”
May I be of assistance?
Yes please! BTW, I managed to reconnect to my media by following your instructions at Synology FAQ - Questions, Answers, and How-To's - #28 by ChuckPa , in particular the FAQ 22 - Hard reset server credentials. Thank you.
I still want to try and run your DBRepair process, though and would appreciate the help (above)
