2 hours ago, Henning said:

Lately I have problems connecting to the daemon from my Deluge 1.3.15 installation on my Windows PC. Deluge Docker is running on another computer in the same network with unraid as OS. Connecting via the web interface is no problem.

The real fix is running the 2.0 docker with the 2.0 windows front end. See here for some help. *(disclaimer. I don't use the windows client, I use linux desktop machines. The following information is what I obtained with 2 minutes of googling and reading)

https://forum.deluge-torrent.org/viewtopic.php?f=12&t=55404&start=20#p230175

I'm adding a new 10TB UD drive to my existing 5TB UD drive that's full. New drive is currently in preclear, prepping for additional seeding space. What's best practice for adding additional storage space to Deluge without disturbing what's preexisting?

 

Edit: thinking this through further, if I simply change the Downloads folder to the new drive and changing nothing else I should be fine (i.e. continue to seed existing Linux distros from the existing full disk).. new disk isn't finished preclearing or I'd test...

Edited August 21, 20196 yr by BBLV

8 hours ago, BBLV said:

I'm adding a new 10TB UD drive to my existing 5TB UD drive that's full. New drive is currently in preclear, prepping for additional seeding space. What's best practice for adding additional storage space to Deluge without disturbing what's preexisting?

 

Edit: thinking this through further, if I simply change the Downloads folder to the new drive and changing nothing else I should be fine (i.e. continue to seed existing Linux distros from the existing full disk).. new disk isn't finished preclearing or I'd test...

im not quite clear on your setup here, so are you replacing the 5TB UD (unassigned devices i guess this means) with your 10TB drive, or do you want to somehow combine the 10TB and the existing 5TB drive?.

 

if you simply want to swap the 5TB for the 10TB then its a fairly simple process, stop the container, rsync data from 5TB drive to 10TB drive, reconfigure docker container to target new 10TB drive, start container.

 

if you want to combine the two then this is a lot harder to do.

 

i have to ask the question, why is your drive so large?, wouldn't it be better to seed from your array if you want to seed for long periods of time?, any drive using UD is of course not protected from disk failure, but you of course know that i guess.

Edited August 21, 20196 yr by binhex

8 hours ago, binhex said:

im not quite clear on your setup here, so are you replacing the 5TB UD (unassigned devices i guess this means) with your 10TB drive, or do you want to somehow combine the 10TB and the existing 5TB drive?.

 

if you simply want to swap the 5TB for the 10TB then its a fairly simple process, stop the container, rsync data from 5TB drive to 10TB drive, reconfigure docker container to target new 10TB drive, start container.

 

if you want to combine the two then this is a lot harder to do.

 

i have to ask the question, why is your drive so large?, wouldn't it be better to seed from your array if you want to seed for long periods of time?, any drive using UD is of course not protected from disk failure, but you of course know that i guess.

I wanted to keep the seeding going 24/7 and didn't want to constantly spin up the array drives, hence the usage of unassigned devices for Deluge. I don't want to replace the existing 5TB drive and don't necessarily want to combine the drives, just want to add additional storage space but continue to seed from both drives. My preclear should be done tomorrow on this new 10TB drive and I'll try my method mentioned above and comment back on how it works out.

6 minutes ago, BBLV said:

wanted to keep the seeding going 24/7 and didn't want to constantly spin up the array drives

If you create a share for this on the array you can have both drives assigned and they will be the only ones that spin up (plus parity if you have it installed).

19 minutes ago, wgstarks said:

If you create a share for this on the array you can have both drives assigned and they will be the only ones that spin up (plus parity if you have it installed).

Not a bad idea. Can't remember where I originally read that UD was the way to go, but your method makes a lot of sense.

Tried to access delugevpn today and nothing gives following error message

 

An error occurred.

Sorry, the page you are looking for is currently unavailable.
Please try again later.

If you are the system administrator of this resource then you should check the error log for details.

 

Did a complete reinstall following spaceinvaders video to the letter and nothing!

 

any help?

2 hours ago, erfly7 said:

Tried to access delugevpn today and nothing gives following error message

 

An error occurred.

Sorry, the page you are looking for is currently unavailable.
Please try again later.

If you are the system administrator of this resource then you should check the error log for details.

 

Did a complete reinstall following spaceinvaders video to the letter and nothing!

 

any help?

follow procedure in link below:-

https://github.com/binhex/documentation/blob/master/docker/faq/help.md

ok not sure what I was doing think this is the correct one.

supervisord.odt

5 minutes ago, erfly7 said:

ok not sure what I was doing think this is the correct one.

supervisord.odt 40.43 kB · 1 download

that is a succesful start, you sure the LAN_NETWORK is correct?, from your log:-

2019-08-22 01:16:24.885197 [info] LAN_NETWORK defined as '192.168.1.0/24'

see here for help Q4:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

yes my router page is at 192.168.0.1

 

So I just copy

 

echo "# force iptable mangle module to load (required for *vpn dockers)" >> /boot/config/go echo "/sbin/modprobe iptable_mangle" >> /boot/config/go

 

into the terminal in Unraid?

Edited August 22, 20196 yr by erfly7

11 minutes ago, erfly7 said:

yes my router page is at 192.168.0.1

 

So I just copy

then you have defined LAN_NETWORK incorrectly, read faq.

so it should be 192.168.0.0/24?

so it should be 192.168.0.0/24?

Correct

Sent from my CLT-L09 using Tapatalk

Thank you so much I am an idiot.

On 8/21/2019 at 10:33 AM, BBLV said:

Not a bad idea. Can't remember where I originally read that UD was the way to go, but your method makes a lot of sense.

So changing my data target folder to the new drive killed my seeding from the old drive, as expected... Now I'm forced to copy the old 5TB drive's contents to the new 10TB drive and will worry about this again when this new drive is near full. By then maybe it will be time to buy a new 10TB drive to replace my current dual 6TB parity drives and move the Deluge data folder to its own share on the array.

Edited August 23, 20196 yr by BBLV

On 8/22/2019 at 1:33 AM, BBLV said:

Not a bad idea. Can't remember where I originally read that UD was the way to go, but your method makes a lot of sense.

My solution is that torrents which are leeching are held, unprotected, in a folder on the cache drive (but a folder on UD would be just as good).  When the torrent finishes downloading,  deluge moves it to a folder on the protected array.  In this way, the parity drive is only involved during the nightly copy of newly completed downloads from cache.  If the cache drive were to fail, I would only lose currently downloading torrents, which could be easily restarted.  This has been working well for me over many years.

I need some help to get this running. I followed spaceinvaders video but no dice. 

 

I have my own VPN that I run on my Router. Even if I disable the VPN in the options for binhex-delugevpn it still doesn't work. Even if I get the normal version of deluge with no VPN, the download will start then it drops down to 0 within 5 seconds. Any ideas?

 

i think it might be this that could be preventing the downloads from starting properly? (see image)

 

 

 

 

*EDIT

 

Issue fixed. I got my paths wrong in Deluge settings. 

Edited August 25, 20196 yr by z0ki

On 5/12/2019 at 10:42 AM, megna22 said:

could someone please post an example on how to configure qbittorrent or DelugeVPN with torguard Thanks

did you every get this to work with delugeVPN and Torguard? Please post, much thanks

 

On 8/16/2019 at 10:38 PM, Henning said:

So now that I downgraded and the torrents are gone my next question would be:

Is it possible to restore it? I do not have a backup of the appdata folder but I found multiple archives in the appdata/binhex-delugevpn/archive folder which seems to hold backup of torrent states:

 

 

Extracting them and overwriting the files in appdata/binhex-delugevpn/state did not work. Even rebuilding the image after it.

Did someone restored a backup sucessfully and are my files sufficient?

 

Someone able to answer this? Still havent touched deluge since than and am willing to have last try of restoring before starting the work of readding all the torrents manually.

I am humbly seeking assistance in setting up the DelugeVPN docker container on a Synology DS918+ NAS system. I have followed the guide from here as best I could:

 

http://tomthegreat.com/2018/03/11/setting-up-deluge-with-vpn-on-synology-using-docker/

 

Unfortunately, I am unable to access the Deluge setup wizard after going through the process (Step 12). Looking at the supervisord.log file, it seems the problem is related to this:

 

DEBG 'start-script' stdout output:
ERROR: Cannot open TUN/TAP dev /dev/net/tun: No such device (errno=19)
Exiting due to fatal error

 

I have attached the logfile in it's entirety in the hopes of finding help in this matter. My computer skills are limited and thus I don't see a of way fixing this on my own.

 

Thank you for your consideration.

supervisord_namesremoved.log

Hi,

 

I followed this tutorial to install DelugeVPN on my Synology Nas. It keeps crashing and I've found this error message in the logs:

[crit] VPN_PORT not found in /config/openvpn/XXXXXX-XXXX-XXXXX-XXXXXX-XXXXX_lu_openvpn.ovpn, exiting...

 

I'm using VPNUnlimited. Any idea what can I do to fix this?

Thanks for your work on this docker, by the way!

37 minutes ago, Walhto said:

Hi,

 

I followed this tutorial to install DelugeVPN on my Synology Nas. It keeps crashing and I've found this error message in the logs:

[crit] VPN_PORT not found in /config/openvpn/XXXXXX-XXXX-XXXXX-XXXXXX-XXXXX_lu_openvpn.ovpn, exiting...

 

I'm using VPNUnlimited. Any idea what can I do to fix this?

Thanks for your work on this docker, by the way!

Did you download the vpn config fie from your vpn site and place it in that location?

Edited August 29, 20196 yr by Armed Ferret
Spelling error

8 minutes ago, Armed Ferret said:

Did you download the vpn config fie from your vpn site and place it in that location?

Yes, I did. The file is as I downloaded it (I've changed the number by XXXXX, didn't know if it was necessary for privacy).

Hello BixHex,

 

I just updated to the latest version a few days ago and I cannot get it running on my Synology.  I've been using the previous versions for some time but this one has started giving me grief.  When I start the docker container I get the error:

 

/bin/bash: /root/init.sh: No such file or directory

 

It's as though it's trying to run the inital run script to see that all the previous config files are in place etc. but not being able to do so as it cannot locate that /root/init.sh location on the synology.  I know Synology Docker is a bit different than others with its file locations but most containers I've been able to get working.  This one I'm struggling with.  Any advise would be helpful.

 

Added: Found a reference to the fact that /bin/bash might not be available in Synology Docker?!

It’s because bash is not part of the image. Launching shell with /bin/sh would work. However, I don’t know if it’s possible to configure that on Synology...

 

Any help would be great.

Edited August 30, 20196 yr by Lipora
missing info