[[Support] binhex - DelugeVPN]

On 6/11/2018 at 8:32 PM, Magic815 said:

 

Are you sure? All research I've done seems to indicate hardlinking can never work across drives. And multiple drives in a share (which is what UnRAID does) is going to have that problem. In looking at my downloads, I see two copies of every torrent downloaded. One in the "Downloads" share, and one in the "Media" share. Maybe symlinking would work with UnRAID? It definitely is copying on my end, when I have the setting set to 'hardlink instead of copy.'

 

I've actually been running this on my synology device. Am thinking about moving to unRaid with a new build shortly though and I think you should be able to hardlink within a user share (just not across user shares).

 

 

[[Support] binhex - DelugeVPN]

On 6/5/2018 at 7:17 PM, Magic815 said:

Does anyone know how well this works with the 'Hardlink instead of copy' option found in Sonarr and Radarr? I only have one torrent tracker attached to Sonarr/Radarr, and it's a private tracker that I want to be permaseeding on. I just wasn't sure if anyone has confirmed that it will keep seeding in deluge in this setup, after Sonarr/Radarr have ingested it on their end.

 

Edit: Also, I'm curious to know if it actually hardlinks, or if it's going to resort to copying between folders on the unraid server, which would mean taking double the space for every torrent downloaded.

 

Yes, the hardlinks option in sonarr/radarr should work for seeding with deluge and won't take double the space. I've had this setup running with sonarr/radarr and deluge for a few months with hardlinks for seeding.

[[Support] binhex - DelugeVPN]

Was hoping that someone could take a look at my logs and figure out what's going wrong with the delugevpn docker that I have on my Synology NAS. Have been using it for a few months and had it working perfectly but it started not working last night for some reason. I'm able to start up the docker but am not able to access deluge either via the WebGUI or through the remote Deluge thin client on my laptop. Only thing I can think of is the LAN_NETWORK variable but I've tried the IP for both my home LAN Network (192.168.0.1) and the docker bridge network (172.17.0.1) without any luck. I previously had that variable set as the docker bridge network when I had the docker working. 

supervisord.log