My QNAP TVS-h1288X was running great until my Ubuntu VM crashed and rebooted the NAS. Once it turned back on, I opened Plex from the QNAP app and was hit with the “This site can’t be reached page”. Rebooted the server safely, same thing. Stopped and started the app, same thing. Reinstalled the app, same thing. Replaced the db files from yesterdays backup, started the app, same thing. Not sure what else I can try. Please help as I am pulling my hair out trying to figure out what else I can try without starting from scratch. Have literally spent years building and configuring my library and feel devastated at the moment. Only other thing I haven’t tried is restoring the entire Plex folder backup as I noticed it hadn’t backed up the 3 small files in the main directory (“.LocalAdminToken”, Preferences.xml and "Setup Plex.html) in over a month, so not sure if they need to match with dates or anything before I did it.
Can provide logs, just let me know what log files to upload.
Thank you so much in advance. Any help is greatly appreciated.
Thanks ChuckPa, but I probably should have been a bit clearer when I said I “reinstalled” the app. I didnt actually uninstall it, I just installed the qpkg over the existing, like you would normally do when updating. I am aware uninstalling the qpkg breaks Plex. However, I still tried your utility and it completed, but I am still receiving the same error
A complete NAS rebuild would have to be my absolute last resort. Is there anything you could recommend before that?
Could the database be corrupt and I could use your other tool “DBRepair”?, or restoring the PlexData folder backup?
Appreciate the time you’ve taken to look over my logs as I cannot quite understand them myself.
Ok. Starting Plex from scratch again would still be less than ideal as I’ve put countless hours/days customising every poster etc with collections and everything, so hopefully that’s a second last resort.
I’ll try DBRepair now and get back to you. Thanks!
What do you mean by pending changes? None of the libraries were scanning at the time, if that’s what you mean?
And yeh, I do have quite a large library of movies and tv shows only though. No music
I do have the entire PlexData directory (roughly 300gb) backed up on a seperate external drive which runs nightly, however after all this happened, I noticed on the backups that everything has been backing up except for these 3 files in the main directory (see attached screenshot)
I’m not too worried about those 3 files. Your preferences file is easily fixed with only minor inconvenience should it get broken. (easily repaired or recreated)
Are you good at reading XML?
What I’m asking:
If you open it in the QNAP text editor app,
Do you see PlexOnlineToken="" ( a null token ) ?
As you look at each preference, are any of them duplicated ?
They are in Name="value" format.
Knowing you have a full backup is very reassuring. It gives us a lot of working room. (Please disable updating / backing up again until we resolve this )
I probably don’t quite understand everything that’s in the XML file, but I can open it and read it. There is one instance of PlexOnlineToken=, but it has a number in it. Nothing that I can see seems to be duplicated. I can share the xml file with you if it’s safe to do so?
DBRepair just finished now. It found a corrupted db, repaired and completed. Started the app again and sadly still receiving the error
And yes, I immediately stopped the automatic backups yesterday after the crash, so complete backup is from the previous day.
