Had more crashes in one evening on this version than I’ve had in the last year.
Will probably roll back.
No crashes for me - I didn’t update :)>-
Few years back there was a buggy update that affected me. Since then, I normally wait a day or two, read the forums to see if there are issues then update.
@astrofisher I’ll probably have to go with that plan. It’s a good one. But to be honest, I think I’m a little OCD as I hate leaving the orange banner reminding me to upgrade. I feel like I’m leaving something undone. LOL. My issue, not the program’s. 
But then a bad update is so rare from Plex that I suppose the occasional need roll back is a fairly painless resolution.
@JordanHarris said:
Isn’t this an “early access” version of something like that? It’s perfectly acceptable to have bugs in an early access release, isn’t it? For the official release, that’s a different story.
I’m not on a beta list - it’s a PlexPass stable release from my knowledge. Maybe the wrong version was pushed?
@danjames92 said:
@mjovanovic said:
@raevengel said:
No, it absolutely isn’t OK. I’ve got this same 500 error multiple times tonight. Only change was upgrading. Previously stable. Really virulent bug. Only way I can get it working again is to close the Plex server and restart. It otherwise appears to be fine when it crashes.Dude, relax - just roll back to the version linked here. It takes 5 minutes and it doesn’t impact your DB or movies in any way. Things will just be where you last left off. Crashes suck but this isn’t a regular thing.
Yeah people overreacting way too much here.
Maybe true, but they didn’t have to push the release when they did. And if people don’t tell the devs there’s a problem they won’t know.
And for those of us who manage a Plex server and who aren’t devs themselves, it’s a little scary when things start going wrong inexplicably. To say nothing of the completely non-techie family members who use it and have no idea why things are going wrong. From the interface, it wasn’t clear at all what was happening as the server was still showing as running and connected from within the Plex Roku app.
I have the utmost respect for the devs and have defended them strongly when people were getting so terrible about the new Plex interface. I think the world of them. Anyone can have a buggy release or push the wrong one accidentally. It’s fine.
@raevengel said:
@JordanHarris said:
Isn’t this an “early access” version of something like that? It’s perfectly acceptable to have bugs in an early access release, isn’t it? For the official release, that’s a different story.I’m not on a beta list - it’s a PlexPass stable release from my knowledge. Maybe the wrong version was pushed?
I really doubt that. Just a bug that wasn’t caught - specific to Windows machines. We’ll know the exact problem in the next version’s release notes.
@kegobeer-plex said:
You uninstall 0.9.16.1 and install 0.9.16.0.
Hey thanks, I thought it was harder than that. Maybe in past versions… rolled back and all is fine now. I will try and refrain from pressing the upgrade button so soon after a release in the future. Been burnt by that button too many times…
+1 on the 500 Internal Server error message.
Personally, I don’t want to roll-back. I want to roll FORWARD.
Waiting on the fix…
Same problem here…500 internal server error message
Log attached
How do I “roll back” to the previous version?
@SomethingWicked said:
How do I “roll back” to the previous version?
https://forums.plex.tv/discussion/comment/1148972/#Comment_1148972
On Windows10, it says that we are supposed to go to the Control Panel, and select “uninstall.” When I get ready to do this, it gives me a warning that the app, PLUS all related data/files will be removed/deleted. ← Not really a risk that I’m willing to take!!!
Plex folks: I have purchased not one, but TWO PlexPass accounts. I realize that this gives us some “early exposure” to somewhat pre-release versions of the software (and I appreciate that!)
But, what I’d appreciate MORE, is some sort of “roll-back” button, adjacent to the UPGRADE button. (This is the second time in the past month that I’ve experienced these types of “bugs.”)
Plex is now/currently COMPLETELY USELESS to my family and myself.
Also, please post updates on your Employee-only release site, that CAUTIONS/prevents MORE people from downloading this version of the code. At the moment, things look “just fine” on YOUR area of the support blog. Instead, there should be some sort of WARNING message!
We LOVE our/your Plex app!!! (That’s why I’ve paid TWICE as much as most people = to support the cause!!!)
Your app has been VERY innovative.
Please keep that innovation alive and health, and implement a nice/friendly “roll back” button, too! (e.g. keep the prior version of code on “standby” each time we upgrade, so we can have an easy/fast/smooth/error-free way to also roll-back.)
Peace.
@njross@yahoo.com said:
On Windows10, it says that we are supposed to go to the Control Panel, and select “uninstall.” When I get ready to do this, it gives me a warning that the app, PLUS all related data/files will be removed/deleted. ← Not really a risk that I’m willing to take!!!
Uninstalling Plex doesn’t delete your metadata or your settings, so you shouldn’t really refrain from doing it if you want to be able to use Plex before a bug fix is released.
@JordanHarris said:
Isn’t this an “early access” version of something like that? It’s perfectly acceptable to have bugs in an early access release, isn’t it? For the official release, that’s a different story.
That is my understanding. Plex Plass != “stable/final”
Bugs will happen, unfortunately, I cannot run the installer to roll back as it insists PMS is still running, I killed the entire process tree, opened a DOS prompt and did a taskkill, etc. No go. However, because simply restarting (after killing) PMS (as in the current buggy version) seems to get it back on track (for how long I dont know just yet), I’ll just patiently await a hot fix.
@raevengel said:
@danjames92 said:
@mjovanovic said:
@raevengel said:
No, it absolutely isn’t OK. I’ve got this same 500 error multiple times tonight. Only change was upgrading. Previously stable. Really virulent bug. Only way I can get it working again is to close the Plex server and restart. It otherwise appears to be fine when it crashes.Dude, relax - just roll back to the version linked here. It takes 5 minutes and it doesn’t impact your DB or movies in any way. Things will just be where you last left off. Crashes suck but this isn’t a regular thing.
Yeah people overreacting way too much here.
Maybe true, but they didn’t have to push the release when they did. And if people don’t tell the devs there’s a problem they won’t know.
And for those of us who manage a Plex server and who aren’t devs themselves, it’s a little scary when things start going wrong inexplicably. To say nothing of the completely non-techie family members who use it and have no idea why things are going wrong. From the interface, it wasn’t clear at all what was happening as the server was still showing as running and connected from within the Plex Roku app.
I have the utmost respect for the devs and have defended them strongly when people were getting so terrible about the new Plex interface. I think the world of them. Anyone can have a buggy release or push the wrong one accidentally. It’s fine.
It’s early access beta software. People need to understand the implications of using beta software. It has bugs.
I’m considering rolling back too, but I’m using the PMS service…are there any extra steps if the 3rd party PMS service is used? Wondering if the PMS service needs to be reconfigured/reinstalled too or if it really is just as simple as uninstall 0.9.16.1 and install 0.9.16.0.
@danjames92 said:
@raevengel said:
@danjames92 said:
@mjovanovic said:
@raevengel said:
No, it absolutely isn’t OK. I’ve got this same 500 error multiple times tonight. Only change was upgrading. Previously stable. Really virulent bug. Only way I can get it working again is to close the Plex server and restart. It otherwise appears to be fine when it crashes.Dude, relax - just roll back to the version linked here. It takes 5 minutes and it doesn’t impact your DB or movies in any way. Things will just be where you last left off. Crashes suck but this isn’t a regular thing.
Yeah people overreacting way too much here.
Maybe true, but they didn’t have to push the release when they did. And if people don’t tell the devs there’s a problem they won’t know.
And for those of us who manage a Plex server and who aren’t devs themselves, it’s a little scary when things start going wrong inexplicably. To say nothing of the completely non-techie family members who use it and have no idea why things are going wrong. From the interface, it wasn’t clear at all what was happening as the server was still showing as running and connected from within the Plex Roku app.
I have the utmost respect for the devs and have defended them strongly when people were getting so terrible about the new Plex interface. I think the world of them. Anyone can have a buggy release or push the wrong one accidentally. It’s fine.
It’s early access beta software. People need to understand the implications of using beta software. It has bugs.
That isn’t how it is presented to us as end user consumers. Yes, you get new features first as PlexPass subscribers before free users but nowhere does this say that as a paid PlexPass member, you are beta testing software. If this is the case, Plex needs to make some major changes in how they present PlexPass. Most people won’t want to essentially pay money to be a beta tester without the option to opt out.
It does say you have access to preview releases.
https://support.plex.tv/hc/en-us/articles/201844613
Although not explicitly stated, I’ve always seen preview releases treated as “might not be quite ready for prime time” releases. The devs should probably add a statement in there better explaining potential risks.
@raevengel said:
@danjames92 said:
@raevengel said:
@danjames92 said:
@mjovanovic said:
@raevengel said:
No, it absolutely isn’t OK. I’ve got this same 500 error multiple times tonight. Only change was upgrading. Previously stable. Really virulent bug. Only way I can get it working again is to close the Plex server and restart. It otherwise appears to be fine when it crashes.Dude, relax - just roll back to the version linked here. It takes 5 minutes and it doesn’t impact your DB or movies in any way. Things will just be where you last left off. Crashes suck but this isn’t a regular thing.
Yeah people overreacting way too much here.
Maybe true, but they didn’t have to push the release when they did. And if people don’t tell the devs there’s a problem they won’t know.
And for those of us who manage a Plex server and who aren’t devs themselves, it’s a little scary when things start going wrong inexplicably. To say nothing of the completely non-techie family members who use it and have no idea why things are going wrong. From the interface, it wasn’t clear at all what was happening as the server was still showing as running and connected from within the Plex Roku app.
I have the utmost respect for the devs and have defended them strongly when people were getting so terrible about the new Plex interface. I think the world of them. Anyone can have a buggy release or push the wrong one accidentally. It’s fine.
It’s early access beta software. People need to understand the implications of using beta software. It has bugs.
That isn’t how it is presented to us as end user consumers. Yes, you get new features first as PlexPass subscribers before free users but nowhere does this say that as a paid PlexPass member, you are beta testing software. If this is the case, Plex needs to make some major changes in how they present PlexPass. Most people won’t want to essentially pay money to be a beta tester without the option to opt out.
Preview = beta.
