blackbeardrrr

Thanks so much, Squid! This did the trick! It was a lot less scary with you guiding me through it. Much appreciated.

"APPS" used to work for me. I don't know if this stopped working because of a recent upgrade of Unraid OS, but here is the behavior I'm seeing: If I click on "APPS", I get a yellow warning message, saying: "Click Install to download and install the Community Applications plugin" If I click the Install button, I get: "plugin: installing: https://raw.githubusercontent.com/Squidly271/community.applications/master/plugins/community.applications.plg plugin: downloading https://raw.githubusercontent.com/Squidly271/community.applications/master/plugins/community.applications.plg plugin: downloading: https://raw.githubusercontent.com/Squidly271/community.applications/master/plugins/community.applications.plg ... done plugin: not reinstalling same version" I am on 6.10.3.

Apologies in advance for this silly question, but: is it possible to RE-install community applications? When I upgraded it using the GUI, it said that the package was corrupted, but the UI shows the latest package was installed. I fear there is an inconsistency, so wanted to reinstall it. Can I safely remove CA and then install it again? Or is there a better way? Thanks!

First off, thank you rix for developing this awesome app. I'm posting this here to help other users can make use of this information. No action required - the problem was resolved by updating the ripper docker. If you feel that this post is too basic, please feel free to remove. I installed ripper via Unraid Community Applications. It runs as a docker. This was months ago. Things were working great. Not being very familiar with docker, I didn't know how to check the version, or even update the version. Or even know that the version was the cause of the problem I was having. Honestly, I was expecting Unraid to have a little "update" option for each installed application within the Apps tab. Problem: At some point, for some reason, ripper just wouldn't rip. It would spit out the dvd after a few seconds and drop a blank folder into the Finished folder. For every dvd. Steps: I googled "unraid logs." first result said to go here: http://tower/log/syslog When I do that, I saw: Nov 7 21:11:38 Tower kernel: sr 2:0:0:0: [sr0] tag#21 Sense Key : 0x5 [current] Nov 7 21:11:38 Tower kernel: sr 2:0:0:0: [sr0] tag#21 ASC=0x6f ASCQ=0x3 Nov 7 21:11:38 Tower kernel: sr 2:0:0:0: [sr0] tag#21 CDB: opcode=0x28 28 00 00 00 08 00 00 00 02 00 Nov 7 21:11:38 Tower kernel: blk_update_request: I/O error, dev sr0, sector 8192 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Nov 7 21:11:38 Tower kernel: Buffer I/O error on dev sr0, logical block 1024, async page read Started googling, and that lead me to believe that there was something wrong trying to read the disk. Changed the SATA cable Tried a different SATA port on the motherboard Bought a new dvd drive Nothing worked. Finally happened upon this thread within the unraid forums, and saw in a previous post that there was a ripper-specific log available: cat /mnt/user/appdata/ripper/Ripper.log When I did that, I saw: MSG:5021,131332,1,"This application version is too old. Please download the latest version at http://www.makemkv.com/ or enter a registration key to continue using the current version.","This application version is too old. Please download the latest version at %1 or enter a registration key to continue using the current version.","http://www.makemkv.com/" MSG:1005,0,1,"MakeMKV v1.16.5 linux(x64-release) started","%1 started","MakeMKV v1.16.5 linux(x64-release)" MSG:5074,0,0,"Automatic checking for updates is enabled, you may disable it in preferences if you don't want MakeMKV to contact web server.","Automatic checking for updates is enabled, you may disable it in preferences if you don't want MakeMKV to contact web server." At that point, I started exploring in the UI how the heck to update ripper, thinking that the image might be old. I figured, if I didn't know how to update ripper, then I probably never updated it since installing it. Found it under Docker > Check for updates > then run the update using the link in the Version column. Success! Basically, I didn't know where to look for the ripper-specific logs, and I didn't know how to update the app. Thanks again! I'm a happy camper.