Plex server update 1.18.0.1846-f62172e99 is borked

I’m having the same issue, update Plex on my unraid server, and now Plex says the server is “unreachable.” Just tried removing and re-installing Plex, and getting the same thing. Some mentioned “rolling back” to a previous version, does anyone know how to do that on unraid?

Thanks!

downloaded and did a “repair” … still no love.

Or downgrade to the last work version. (And get off the Beta release track to boot).

1 Like

I am running 1.18.0.1846 on Windows 2019 standard with a mix of Android, windows and web clients and haven’t experienced any major issues with this PMS version.
I have also been running Plex for many years and only had one issue with a beta version working with PmsService and crashing, other than that it’s been smooth sailing.
At first the UNO interface seemed clunky, but I like it and prefer it over the old. To each their own I guess.

1 Like

Not sure what’s up with the people that have issues, but mine in the Linuxserver.io docker is as solid as ever. I can’t even remember when an update caused me issues.

thanks… trying it… “onward onward into the valley of death”

If you lived near me I would take you out for a few beers!.. worked great THANK YOU!!!. 1841 works fine.

1 Like

Never mind, Found the updates, they wee in a different directory.

I have been experimenting with the new music scanner and it seems a bit buggy. For a start the command line scan doesn’t work with “Plex Music” libraries

I use a script to create libraries (sections) eg:-

“Plex Media Scanner.exe” --add-section music.best --type 8 --lang en --agent tv.plex.agents.music --location “m:\media\music\best”

This sets the scanner to “Plex Music Scanner” NOT “Plex Music” as it should.

So I manually fix that in the db then run:-

“Plex Media Scanner.exe” --scan --refresh --section 1

Which does nothing! If you --force it, then it loops through artists, but still adds no music. You CAN initiate a scan via the Plex UI but NOT via the command line. All other library types including music with scanner=“Plex Music Scanner” work fine. So it’s problems with new Plex Music library.

To recreate the problem more easily, Run Plex server FIRST, THEN rename “Plex Media Scanner.exe” so it won’t run. Add a new music library, then rename back to “Plex Media Scanner.exe” and run (using appropriate number for section)

“Plex Media Scanner.exe” --scan --refresh --force --section 1

I have a very limited hard drive 128GB for my main OS and another 48TB of storage, I moved the db, the app data and all that good stuff onto my storage drive a few weeks ago due to Plex updating about a month ago and I lost all my metadata and database information. So thankfully once I had moved that over I uninstalled Plex entirely and then went into my storage>application data>Plex media server>updates and rolled it back to the prior version.

now come to find out not only will the new server update be as limited as it is, I’m hearing updates that Plex is also starting using a new transcoder. Seriously hoping this doesn’t cause more problems than it resolves. Granted I’m using hardware transcoding on and Nvidia quadro and a dual Xeon setup, but right now I’m having no issues and just waiting for it to hit the fan. I hope they test it thoroughly before release.

1 Like

That’s precisely what beta releases are for. If you’re not willing to test / report issues, then updating beta releases can be annoying at best and risky at worst.

1 Like

well, what did you do?

i’m uninstalling/reverting because this latest update is completely borked.

2 Likes

I can’t scan my libraries at all, it just does nothing.

Running on MacOS 10.14.6. Beta channel removed my ability for my local devices to connect to my server. Tried downgrading, no change.
Plex Media Server.log (448.7 KB)

Just noticed that my Roku client connects fine, but my phone (Android 9) and iPad (iOS12/testflight) do not connect. All on the local network.

1 Like

Also ran into huge problems. Updating the music library at first took around 30 minutes. No biggie. Server seemed to work fine. A few days later, I can’t connect through local network, and I notice the CPU usage on Plex went to 40-50% and stayed there for hours. I rebooted my PC, reinstalled Plex, same thing happened. Wouldn’t even load up locally. Went back to 1.17.0.1841. Fixed my problems. Hoping for another 1.18 update that’s working better because I really like the new metadata update.

1 Like

@ bleachjt see also @ New music scanner - high 100% cpu on half number of cpu cores

I had this issue as well. The update did not seem to finish properly. I left and came back some time later to find the install still “spinning”. I’m on qnap, by the way…

When I restarted the server, i was blocked from my own data. I had to delete the server, and recreate it. It pissed me off big time because I lost many custom named personal stuff, and all of my playlists. A real pain in the a**.

This was my first Plex fail in many years. It has been quite flawless on the QNAP platform. Except for some glitchy remote access stuff (always shows not available, and I KNOW my firewall rules are correct).

well… if you had stopped for a minute and asked for help before you went and deleted everything, someone familiar with qnap might have been able to help you and you might still have all your data.

additionally, plex backs up your database automatically, (if enabled @ settings > scheduled tasks > backup database every 3 days), so you should be able to restore your database (with all your history and playlists etc), assuming the backups were enabled and you did not delete the backups.

@TeknoJunky,

Um… I stopped for a week, my friend. I posted here and on qnap site as well. It does not always go as planned. I just found this post today. Its not always easy to know what to search for. Sometimes you have to know what the problem is to even know how to search. I lost a week trying to find help. I cut my losses, and reinstalled the server.

Thank you for the constructive portion of your post, which is regarding the database backup. It might be worth looking into, at least for future issues.

1 Like