tjb_altf4

Passkey will come eventually, I had mine turn up 12-24 hours later... servers are being crushed with requests from new folders... which is fantastic. Same applies with handing out WU, they simply are struggling to keep up.

Probably this: https://foldingforum.org/viewtopic.php?f=61&t=32424

Using the priority via parameters seems to have a much nice outcome than the "light" workload setting, as it rotates between cores/threads. Light (alone) just smashes the same half of my CPU core set.

I'm only able to get it to work by running in incognito mode.

Nearly forgot, also upgraded host GPU from AMD 5450 to Nvidia GT710, which has made GUI mode much nicer. There seems to be some weirdness on the older AMD card on my 4K monitor that resulted in microscopic text on normal sized GUI... no such issues with the GT710. This is only to do with the basic display driver, never had any issues in VMs with the appropriate drivers.

Build is still going strong, nearing 2 years later, running 24/7, and it is still serving me well... a testament to both the OS and the hardware. A couple of updates recently: move from 4TB to 10TB array drives underway 10GbE network upgrade (direct connection) network upgrade to Unifi gear, hosting the controller on unraid. Hoping to upgrade case soon for more space, with either go down a rack mount solution path i.e. rosewill 4u, or the new fractal define 7 xl.

If the vm hardware profiles are similar enough, you could set up a boot loader as a new vm template and point it to the vdisks of the other 2 vms, much like a traditional dual boot scenario.

Use a timezone calculator (google) to work out UTC time/date compared to your AEST time/date you want to schedule. It should only be a pain to sort out once.

Successfully upgraded GPU under 6.8.0, which failed and appeared to prevent booting under 6.8.1 Might skip this release...

...and because I'm a glutton for punishment I'm going to try the same hardware upgrade under 6.8.0

Currently can't boot, killed modprobe -r $drivers hanging. Had multiple successful boots into 6.8.1, but I just changed GPU (I use GUI boot mode). Tried power cycling and trying again, no dice. Safe mode doesn't allow for boot either. Finally pulled up an out for chkdsk on windows, on completion of check no errors were found. Popped back to unraid... Still with the same error. Rolled back hardware, no difference. Rolled back to previous unraid version as a last measure... Yes I'm finally up and running again (on 6.8.0)

Upgraded last night, smooth sailing so far. I did noticed one issue, exiting from the web terminal session kicks you straight into a fresh terminal session. Not great, not terrible :p

This happened to me while I was at work lol

Is it the current expected behaviour that on the unraid dashboard that the client tunnel remains long after session has been disconnected? From a user perspective, I would expect this to either show only active tunnels, or show all tunnels but with a status of disconnected (or similar) when that is the case. Other than also being stuck in the custom docker IP access dilemma for one of my applications, this implementation is superb

You could also look at Jackett, which moves that logic to a separate application that is accessible by multiple applications and is well maintained

Happy Unraid user of about 3 years or so, and I'm on my second build now (with build #3 in the next 12 months). Unraid allowed me to consolidate a bunch of separate machines with separate storage into a single more easily managed system. It also lowered the barrier to entry to technologies like virtualisation, docker and just linux in general.

Wow, just had a look, I've got this issue too. Investigating further it seems to be symbolic link in the recycle folder, causing it to loop to infinity. NFI how that was created, but emptying the recycle bin removed the link and all is normal again.

Hopefully he is kind enough to create an updated v1 based image/tag should the non-deluge components need major updating. Otherwise sitting on the most recent v1 tag works just fine IMO as deluge v1 hasn't been updated in 2 years.

I don't think the old client supports v2, and win/mac doesn't have an updated client, only linux so far. V2 users are stuck with webUI for now.

OK this was fun to work out what had happened, this setting is now disabled by default as per changelog below. Changelogs our saviour! I'm sure there was good reasoning behind the change, but it has made a less than intuitive process even more difficult. Could we look at improving the process for creating a "duplicate" docker @Squid? For those that stumble over the problem, this is how to re-enable the ability to create a duplicate docker container. Setting to re-enable reinstall default can be found on the settings of the CA page, change Enable Reinstall Default: setting from No (default) to Yes

Didn't realise v2.0 was ready for prime time, good job deluge devs! Hopefully a smooth transition as I understand it was a complete rewrite, have a few plugins and custom settings. Might just freeze auto updates for a bit while I get on top of some other maintenance first.

Within Unraid itself in VM settings, in the new GUI it's set to the Downstream option. I haven't used onboard sound on this setup, so I can't confirm whats needed, but maybe double check what your default audio device is set to in your VM's OS..

Do a search in community apps, then choose the option "Click Here To Get More Results From DockerHub"

Double check on your tracker's forum, you might find although it's not on the specified "approved" list, it's not on the blacklist either... its just untested. I noticed that's the case on one of my trackers. No way to specify an older version in this container config, and going to an earlier tag would not be a viable solution. If you are 100% locked to the versions stated, maybe see if binhex's rTorrentVPN or qBittorrentVPN uses a suitable version for your tracker