LesterCovax

+1 for the feature suggestion In the meantime though, you don't need to extract the entire archive to retrieve a single file/folder from it (unless you're talking about access times and such due to a large single file). Here's a simple CLI guide I found. It's even easier if you just open up the archive with something like 7zip. https://www.cyberciti.biz/faq/linux-unix-extracting-specific-files/

It started working after I deleted the path to have the boot device backed up. Will retest and get diagnostics when I get a chance.

I just noticed the other day that my backups stopped working with the process having been hung for two months. I rebooted Unraid, manually initiated a backup, and it still hung on backing up notifications. I'll try removing the boot drive from the backup and try again, but it really needs some way to notify users if the process is ongoing for far too long (e.g. two months ;p ) Here's where it gets stuck, with the 'Abort' button doing nothing: Here are my settings: Cheers!

I had to roll back to that version due to tracker whitelisting as well (and even got a nastygram from an admin asking for a lot of proof on my setup due to inconsistencies). You need to re-add the actual `*.torrent` files for the torrents you had active AFAIK. I first moved/copied everything from the `completed` folder to the `incomplete` folder. I then copied all of my `*.torrent` files from the `/data/.torrents` directory to my `/data/.torrents_add` directory, which is configured to auto-add any torrents in that directory using the `autoadd` plugin. It will populate the torrents for every `*.torrent` file you added and should then check the progress against what you moved from your `completed` to `incomplete` directory. You can select them all and choose "Force Recheck" if it's not doing it for some reason. Then just wait a long long time depending on how large your torrents are. For any that I still don't have the `*.torrent` file for, but the files were in `completed`, I just check a list on the tracker itself for torrents I haven't fully seeded and redownload the torrent file, or just manually find it on the tracker if it's not on the list. Royal PITA, it is

It could be that the local user template is overriding the repo template. Deleting the container, then deleting the user template in ~/.docker/templates-user, followed by recreating the container should work. At first I was thinking that not updating template changes automatically is a bad thing, but it would be annoying if someone made custom changes and had them wiped automatically. The difficulty comes in notifying people of necessary changes if they have everything automated.