I’ve had to roll back to 1.17.1841 again just to make my Plex server usable. I can’t imagine running a processor at 100% for 3 days straight can be very good for the hardware… sigh… I am shocked that this issue has been going on this long with so many people, and there has been no resolution. I can assume that the leading factor in this issue is that we all have big music libraries. Maybe one of us should start another new thread to have us 100% processor / server unreachable users detail our setups and library sizes to see if this helps the Plex team? That or can anyone recomend a good server app for music alone, and I’ll just use Plex for video media.
2 Likes
I was thinking the same thing about splitting off my music library onto a separate sharing service. I’ll do some research into this. Just seems an awful shame that we’re being forced to do this, Plex has been so useful for many years for all my media.
Just really wish there was ANY response from a member of the Plex team to this issue? To the best of my knowledge, these support forums are supposed to be the official channel for registering support requests, but so far no response? Weird.
Especially when it seems a heck of a lot of us are in the same boat
Just in case of help… I ran into a similar issue… after many tries and some investigation… I ended up repairing the database using the Plex support procedure… surprisingly it fixed most unstability, my guesses are between two possible issues there… I have been living during a lot of time with metadata corruption on the db, and version 1.18 does not like it… or v1.18 changes something that require a repair of the database, maybe new tables introduced or whatever.
After that I realized that my Android TV sticks (Amazon Fire TV 4K) were sooooo unstable… I uninstalled the Amazon App store version and sideloaded the latest beta I have been able to find on Plex website, and all my problems have been solved.
1 Like
Hi @cr.gomezm, thanks for the suggestion.
Is this the procedure you’re referring to?
I’d think it strange that all the ‘normal’ database cleanup and automated database tasks that run successfully in v1.17 don’t catch a problem, but hey… what do I know? At this point I’ll try anything! 
Yes @philmbiz that is the procedure, at some point I felt like having the same issue that @Swervie states but cannot confirm, automated tasks crashed the server, then I suspected that any of my clients make some query to the server that make it crash… I usually do not expect so much from standard procedures but this time Plex KB has been so useful.
On my case, repaired database size was around 15 MB less than the original, so it made sense.
Anyway I also had problems with a faulty hard drive that constantly crashed my array forcing it to be rebuilt with the associated performance cost, so I think that my problems came from there more like from the update. 
1 Like
Trying it now.
The ‘check for corruption’ stage didn’t indicate any errors, but I’m going through with the ‘repair’ phase anyway.
I’ll let you know the results when done.
How did u manage to roll it back at 1.17 version?
I think that the stage that really fixed it for me was the final steps, to be more precise, rebuilding from the sql file, also the first steps showed everything was fine.
1 Like
@Advanite, the ‘older’ versions such as v.1.17.x are saved in an 'updates folder.
What if i uninstall plex from windows and have no access to previous updates?
HOLY $%&#!!! The database rebuild seems to have worked!
After doing the complete database “run a repair” procedure (even though no problems were indicated), I’ve updated to v.1.18.4.2171 and it’s RUNNING!
Now… I don’t want to get cocky… I’ll let it run for at least a few days before I declare victory… but this is by far the most success I’ve had.
@cr.gomezm, I owe you a beer! Not sure why one of the actual Plex support people couldn’t have suggested this? Whatever… thank you very much!!!
3 Likes
Just for clarity, here’s what I just did for my Windows system to get past the “server unreachable” problem and it seems to be running ok now!
-
My system would only run PMS v.1.17. Any upgrade to v.1.18.x caused the dreaded “server unreachable” error on the web interface and high CPU usage.
-
I followed these database repair instructions and grabbed the sqlite3 tools
-
My database did not indicate it had any corruption, the integrity check passed without errors.
-
Regardless, I did the complete run a repair procedure. The newly built database was smaller than the original one, so clearly it’s trimmed some unnecessary data from the DB.
-
I launched PMS and verified that Plex started ok with v.1.17
-
I grabbed a fresh copy of v.1.18.4.2171 and ran the PMS upgrade
-
PMS started fine… no more “server unreachable” errors!
4 Likes
hurray!!!, glad to have helped you, I think this is my first 2020 charity work haha 
Well, this is definitely something related to the content that users had on their servers, I think that Plex staff are never going to be able to reproduce the issue because they know exactly what Plex expect to find so they clean everything just before adding it to the library, we as users, like to drop everything into those damn folders without even care. Anyway I agree that someone from Plex staff should have realized that instead of requesting log uploads they can request a library file/log/checkpoint from the users to test.
Anyway, keep an eye opened, I have seen some other people saying something about adding music, I also have music into the library, but I must admit that many years ago I learned the hard way that you first need to fix metadata before adding to library, let’s say using Mp3Tag for example.
2 Likes
Yes, I’m very conscientious about keeping clean tags on ALL my music. Nothing gets put on my system without me scrutinizing and tagging with MP3tag.
That’s why this was so frustrating… I couldn’t see problems with data or db anywhere!
I’ll keep monitoring… maybe the problem will come back in a few days once the system has chewed on my media files for a while, but right now I’m more optimistic than I’ve been in weeks!
1 Like
I have tried the DB rebuild in the past when 1.18 first came out. I am approaching this with caution since the last time I upgraded to 1.18.2171 my Plex ran great for 2 days before going offline and remaining offline till I reverted back to 1.17.1841. Please keep us updated on this. If it holds for several days I’ll try the db repair again and then perform a fresh download upgrade.
1 Like
@Swervie… Agreed, time will tell.
But I’m cautiously optimistic as this is the first time I’ve had any success with the upgrade without removing ALL my music libraries first.
In the hours since the db rebuild, I’ve added new music, initiated a complete library scan, played from browser, iOS, AppleTV, locally and remotely. CPU has stayed reasonable, no glitches, so far so good!
So stay tuned, if it pukes out again I’ll be sure to update the forum (after I cry and open a beer).
2 Likes
Even with the 1.17 version still can’t reach the goddamn server!! idk what to do right now! i’m getting crazy!
Interesting that that worked for you. I already attempted that DB repair process early on in 1.18.x release cycle, but made no difference to the outcome. Just for kicks I tried it again right now, and result is still server unreachable with 100% CPU usage…
CPU usage eventually lowers if you leave it, but as soon as another attempt is made to access the Plex server web interface, CPU spikes again.
1 Like
These are the exact same issues on my server.
1 Like
Just a status update, so far my server continues to function smoothly after the DB rebuild/repair, going on 24 hours now. Fingers crossed it continues.
Very sorry to hear that the DB repair didn’t work for you @Swervie and @sundaydiver.
I was really hoping this was the solution we’d all been looking for.
1 Like
