Errors occurred while processing updates for the following Rock-ons (Plex: [‘Cannot add/remove volume definitions of the container (plex-linuxserver.io) as it belongs to an installed Rock-on (Plex). Uninstall it first and try again.’, ‘NoneType: None\n’]).
NoneType: None
I am not sure what I would need to do for this one, but any guidance would be great
@kraiszero, hello again. Ah yes. There has been a major realignment on Rock-ons in the last couple of weeks, undertaken primarily by @phillxnet, to bring all kinds of Rock-on attributes into alignment, to make it easier for automated validation when new ones are submitted.
This mainly affects Rock-ons where the name (which is also the “key”) has changed. So far, identified on where this will cause a conflict are these listed here:
When I tested (and updated my boxes) plex did not show these challenges (but it might also depend on how “old” your Plex Rock-on installation is).
The current workaround when running into this issue is indeed following the recommendation of reinstalling the Rock-on. The sequence I have followed:
noting down the installation parameters for the affected Rock-on (and any other ones on that list, as unfortunately the Rock-on definition update stops at each failure, not after it evaluated each conflict first, so it’s more of a sequential thing).
uninstall Rock-on(s)
Run the update of the Rock-ons list
re-install previously uninstalled Rock-on(s)
Since there has been a name change for these, I believe, unfortunately, you can’t take the short cut of creating a settings backup via the WebUI, uninstall affected Rock-ons and then run the restore process (I have not tried that in this scenario, but I believe it wouldn’t work).
Apologies for this breaking change, but this has been something that the team has wanted to address for some time for better ease of use (and submitting new Rock-ons following more clear guidelines).