If you have music libraries, try removing them before upgrading and then adding back a little at a time to get past the new music match.
2 Likes
Thanks for the suggestion @pl_5309.
If you look to the first post in the thread, you’ll see I tried that (removing and reintroducing all music) and while that seemed to work for about a day or so, the problem came back… “server unavailable”.
That’s just my experience, if it worked for you that’s awesome.
One note however… by removing all your music libraries, you’ll also lose your play history as well as it’ll screw up any playlists you’ve built, so it’s was a “last resort” option for me.
1 Like
I haven’t done the db repair and install like you did. As a matter of fact I believe I stopped after it found no errors, and did not do the rest of the steps figuring it was pointless, back in October with the early versions of 1.18.x.
If you continue to maintain connectivity I will most definitely go ahead and follow the procedure you did.
I really appreciate the update seeing how we aren’t really getting anything from Plex support!
1 Like
“Plex support procedure” do you have a link to this.
I believe this is the reference:
@Swervie… Going on 2 days and still working! 
3 Likes
1 Like
OK, yesterday late afternoon I bit the bullet and decided to perform the exact same procedure as what @philmbiz did.
So far after about 20 hours, Windows updates, a couple reboots, and adding several movies, my server has also been rock solid. It actually runs better then 1.17.1841 regarding streaming and overall responsiveness in the web GUI.
I am at a loss why the database would work fine with 1.17.x but would require a complete repair / rebuild for 1.18.x.
Anyway I am again going to approach this with caution as I’ve had versions of 1.18.x remain up for a couple days before crashing and burning, but I have to say this fix does seem to have my server working and responding better then it has in a long time, so fingers crossed!
Thanks @philmbiz for the info and I will also post here with updates of how things are continuing to work on my end.
1 Like
Also wanted to add that my database went from 508mb to 443mb doing the repair and rebuild, so like what was stated above, it’s obviously doing something to the database that 1.18 seems to need.
1 Like
Ok, I have had success too (so far). I had to:
- Remove the Plex music library entirely.
- Perform DB rebuild and repair.
- Update Plex to 1.18
So it seems like the music library was the culprit for me. I will hold off adding any music back in to see how it goes first.
EDIT: and 1 hour later, it is unreachable again from the web client…But Android and kodi clients can still see and play media…? Just seems to be the Server Web client that has problems, which looks like it has a new design for 1.18?
which url are you using to access via the web client? local or hosted (https://app.plex.tv/desktop)?
Just tried both local and hosted. Only difference is that hosted first complains about not being able to create a secure connection, so I select allow insecure once, and it goes to the same unreachable error anyway.
All web client access attempts pin the plex server process at 100% CPU.
Seems similar to symptoms in this thread Http://localhost:32400/web/index.html is unavailable but PLEX works on devices
Update:
I am on day 2 now and (so far) my server is still reachable and behaving nicely.
1 Like
Just to report in, I’m on day 3 on v.1.18 after the complete database repair/rebuild and PMS is running very solid and clean. Phew!
As an extra (and off topic), I’ve gone ahead and setup the “PMS as a service”.
With the number of reboots caused by frequent Windows 10 updates, this was the next step to keep my system available 24/7. So far, so good!
@sundaydiver… Darn, sorry you’re still seeing problems. The symptoms you describe are pretty much exactly what I was seeing before doing the complete database rebuild, which seems to have fixed up my problems and I’ve been running solidly for several days now. Unfortunately you’ve reached the limits of my experience on this!
I’m on day 3 and so far so good. I think its safe to say that this issue is resolved for me. Hopefully the next update doesn’t undo it.
1 Like
Can anyone send me a link to that 1.17 download?
You might have a copy locally, see this post for more information:
I downloaded and installed 1.17 and still getting errors. I’m going to open a support ticket
I’ve pretty much given up on the 1.18 updates for now and rolled back to 1.17.0-something. This seems to have un*ucked things for the moment. We’ll see how it goes.
When I have the patience I’ll try the database repair trick.
