be4con Posted July 19, 2019 Share Posted July 19, 2019 22 minutes ago, binhex said: ok thats fine then, so it def should be re-generating a default core.conf file if one doesnt exist in /config, can you paste the output of the following command from ssh to your unraid host:- ls -al <path to the /config path on the host> e.g. ls -al /mnt/user/appdata/binhex-deluge/ total 69252 drwxrwxrwx+ 1 nobody users 19 Jul 18 14:47 ./ drwxrwxrwx 1 nobody users 152 Jan 4 2018 ../ drwxrwxrwx 1 nobody users 54 Jul 15 14:35 archive/ -rw------- 1 nobody users 56 May 30 2017 auth -rw-rw-rw- 1 nobody users 7654644 Mar 17 09:45 blocklist.cache -rw-rw-rw- 1 nobody users 308 Mar 17 09:45 blocklist.conf -rw-rw-rw- 1 nobody users 308 Mar 13 09:45 blocklist.conf~ -rw-rw-rw- 1 nobody users 202981 Jul 19 10:13 deluge-web.log -rw-rw-rw- 1 nobody users 1355 Jul 19 09:42 deluged.log -rw-rw-rw- 1 nobody users 5635 Mar 19 20:53 dht.state -rw-rw-rw- 1 nobody users 115 Jun 1 2017 extractor.conf -rw-rw-rw- 1 nobody users 114 May 31 2017 extractor.conf~ -rw------- 1 nobody users 260 Jul 15 14:36 hostlist.conf -rw-rw-rw- 1 nobody users 168 May 30 2017 hostlist.conf.1.2.old -rw------- 1 nobody users 209 Jul 15 14:36 hostlist.conf.bak drwxrwxrwx 1 nobody users 299 Jan 12 2019 icons/ -rw-rw-rw- 1 nobody users 43206 Jan 16 2019 label.conf -rw-rw-rw- 1 nobody users 43148 Jan 16 2019 label.conf~ -rw-rw-rw- 1 nobody users 150 Apr 11 2018 ltconfig.conf -rw-rw-rw- 1 nobody users 79 Apr 11 2018 ltconfig.conf~ -rw-r--r-- 1 nobody users 162 May 30 2017 perms.txt drwxrwxrwx 1 nobody users 46 Apr 11 2018 plugins/ -rw-rw-rw- 1 nobody users 6115 Mar 19 20:53 session.state drwxrwxrwx 1 nobody users 56 May 30 2017 ssl/ drwxrwxrwx 1 nobody users 62 Jul 16 09:48 state/ -rw-r--r-- 1 nobody users 10353688 Jul 19 09:42 supervisord.log -rw-r--r-- 1 nobody users 10485974 Mar 19 2018 supervisord.log.1 -rw-r--r-- 1 nobody users 10485820 Mar 11 2018 supervisord.log.2 -rw-r--r-- 1 nobody users 10486229 Mar 4 2018 supervisord.log.3 -rw-r--r-- 1 nobody users 10485976 Feb 16 2018 supervisord.log.4 -rw-r--r-- 1 nobody users 10486150 Feb 9 2018 supervisord.log.5 -rw------- 1 nobody users 751 Jul 15 14:36 web.conf -rw-rw-rw- 1 nobody users 683 May 31 2017 web.conf.bak -rw-rw-rw- 1 nobody users 683 May 30 2017 web.conf~ Quote Link to comment
binhex Posted July 19, 2019 Author Share Posted July 19, 2019 19 minutes ago, be4con said: total 69252 drwxrwxrwx+ 1 nobody users 19 Jul 18 14:47 ./ drwxrwxrwx 1 nobody users 152 Jan 4 2018 ../ drwxrwxrwx 1 nobody users 54 Jul 15 14:35 archive/ -rw------- 1 nobody users 56 May 30 2017 auth -rw-rw-rw- 1 nobody users 7654644 Mar 17 09:45 blocklist.cache -rw-rw-rw- 1 nobody users 308 Mar 17 09:45 blocklist.conf -rw-rw-rw- 1 nobody users 308 Mar 13 09:45 blocklist.conf~ -rw-rw-rw- 1 nobody users 202981 Jul 19 10:13 deluge-web.log -rw-rw-rw- 1 nobody users 1355 Jul 19 09:42 deluged.log -rw-rw-rw- 1 nobody users 5635 Mar 19 20:53 dht.state -rw-rw-rw- 1 nobody users 115 Jun 1 2017 extractor.conf -rw-rw-rw- 1 nobody users 114 May 31 2017 extractor.conf~ -rw------- 1 nobody users 260 Jul 15 14:36 hostlist.conf -rw-rw-rw- 1 nobody users 168 May 30 2017 hostlist.conf.1.2.old -rw------- 1 nobody users 209 Jul 15 14:36 hostlist.conf.bak drwxrwxrwx 1 nobody users 299 Jan 12 2019 icons/ -rw-rw-rw- 1 nobody users 43206 Jan 16 2019 label.conf -rw-rw-rw- 1 nobody users 43148 Jan 16 2019 label.conf~ -rw-rw-rw- 1 nobody users 150 Apr 11 2018 ltconfig.conf -rw-rw-rw- 1 nobody users 79 Apr 11 2018 ltconfig.conf~ -rw-r--r-- 1 nobody users 162 May 30 2017 perms.txt drwxrwxrwx 1 nobody users 46 Apr 11 2018 plugins/ -rw-rw-rw- 1 nobody users 6115 Mar 19 20:53 session.state drwxrwxrwx 1 nobody users 56 May 30 2017 ssl/ drwxrwxrwx 1 nobody users 62 Jul 16 09:48 state/ -rw-r--r-- 1 nobody users 10353688 Jul 19 09:42 supervisord.log -rw-r--r-- 1 nobody users 10485974 Mar 19 2018 supervisord.log.1 -rw-r--r-- 1 nobody users 10485820 Mar 11 2018 supervisord.log.2 -rw-r--r-- 1 nobody users 10486229 Mar 4 2018 supervisord.log.3 -rw-r--r-- 1 nobody users 10485976 Feb 16 2018 supervisord.log.4 -rw-r--r-- 1 nobody users 10486150 Feb 9 2018 supervisord.log.5 -rw------- 1 nobody users 751 Jul 15 14:36 web.conf -rw-rw-rw- 1 nobody users 683 May 31 2017 web.conf.bak -rw-rw-rw- 1 nobody users 683 May 30 2017 web.conf~ ok im going to need further logs here to see whats going on, can you please do the following procedure:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md 1 Quote Link to comment
be4con Posted July 19, 2019 Share Posted July 19, 2019 18 minutes ago, binhex said: ok im going to need further logs here to see whats going on, can you please do the following procedure:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md Not sure how to complete this step: 3. Set the env var key "DEBUG" to a value of "true". Can you give me a pointer? Quote Link to comment
binhex Posted July 19, 2019 Author Share Posted July 19, 2019 1 hour ago, be4con said: Not sure how to complete this step: 3. Set the env var key "DEBUG" to a value of "true". Can you give me a pointer? left click icon for this app in unraid web ui, select edit, scroll down and change the value for DEBUG to true Quote Link to comment
be4con Posted July 19, 2019 Share Posted July 19, 2019 29 minutes ago, binhex said: left click icon for this app in unraid web ui, select edit, scroll down and change the value for DEBUG to true Yes, that's where I looked but I don't have that value - there is no DEBUG field. Sorry for being a pain on this... Quote Link to comment
binhex Posted July 19, 2019 Author Share Posted July 19, 2019 25 minutes ago, be4con said: there is no DEBUG field. Sorry for being a pain on this... thats my bad, thought i added debug to this docker image, looks like i didnt, ok in that case just start the container again and attach the /config/supervisord.log file Quote Link to comment
be4con Posted July 19, 2019 Share Posted July 19, 2019 8 minutes ago, binhex said: thats my bad, thought i added debug to this docker image, looks like i didnt, ok in that case just start the container again and attach the /config/supervisord.log file No new supervisord.log file created unfortunately 😧 The last log file listed for the container within the unraid UI is 23 hours ago, is that any use, it's showing errors? Quote Link to comment
binhex Posted July 19, 2019 Author Share Posted July 19, 2019 2 minutes ago, be4con said: No new supervisord.log file created unfortunately 😧 The last log file listed for the container within the unraid UI is 23 hours ago, is that any use, it's showing errors? sure attach it. Quote Link to comment
be4con Posted July 19, 2019 Share Posted July 19, 2019 (edited) 11 minutes ago, binhex said: sure attach it. Here you go Log for binhex-deluge.htm Edited July 19, 2019 by be4con Quote Link to comment
kidd Posted July 21, 2019 Share Posted July 21, 2019 Recently (maybe 3 days ago) I noticed an issue with delugevpn not working anymore (I am unable to access the WebGUI. I just get an error refused connect). I do not remember making any changes to my docker container or router. I'm trying to determine if I have something misconfigured on the server side, or on the router side (pfSense). The following is the contents of my supervisord.log file (after removal of some personal identifying information). I made sure to pull the latest image down from binhex/arch-delugevpn. I'm not sure if my exact docker configuration is required, but if necessary please let me know: Created by... ___. .__ .__ \_ |__ |__| ____ | |__ ____ ___ ___ | __ \| |/ \| | \_/ __ \\ \/ / | \_\ \ | | \ Y \ ___/ > < |___ /__|___| /___| /\___ >__/\_ \ \/ \/ \/ \/ \/ https://hub.docker.com/u/binhex/ 2019-07-20 18:09:54.956068 [info] System information Linux 0c23a282d53f 5.1.18-300.fc30.x86_64 #1 SMP Mon Jul 15 15:42:34 UTC 2019 x86_64 GNU/Linux 2019-07-20 18:09:54.988354 [info] PUID defined as '1000' 2019-07-20 18:09:55.040803 [info] PGID defined as '1000' 2019-07-20 18:09:55.090992 [info] UMASK defined as '000' 2019-07-20 18:09:55.121569 [info] Permissions already set for volume mappings 2019-07-20 18:09:55.158459 [info] DELUGE_DAEMON_LOG_LEVEL defined as 'info' 2019-07-20 18:09:55.190752 [info] DELUGE_WEB_LOG_LEVEL defined as 'info' 2019-07-20 18:09:55.223578 [info] VPN_ENABLED defined as 'yes' 2019-07-20 18:09:55.260659 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/CA Toronto.ovpn dos2unix: converting file /config/openvpn/CA Toronto.ovpn to Unix format... 2019-07-20 18:09:55.311798 [info] VPN remote line defined as 'remote ca-toronto.privateinternetaccess.com 1198' 2019-07-20 18:09:55.341151 [info] VPN_REMOTE defined as 'ca-toronto.privateinternetaccess.com' 2019-07-20 18:09:55.374902 [info] VPN_PORT defined as '1198' 2019-07-20 18:09:55.410902 [info] VPN_PROTOCOL defined as 'udp' 2019-07-20 18:09:55.444396 [info] VPN_DEVICE_TYPE defined as 'tun0' 2019-07-20 18:09:55.476164 [info] VPN_PROV defined as 'pia' 2019-07-20 18:09:55.509889 [info] LAN_NETWORK defined as '192.168.1.0/24' 2019-07-20 18:09:55.542493 [info] NAME_SERVERS defined as '209.222.18.222,209.222.18.218' 2019-07-20 18:09:55.572058 [info] VPN_USER defined as '***REDACTED***' 2019-07-20 18:09:55.608192 [info] VPN_PASS defined as '***REDACTED***' 2019-07-20 18:09:55.639684 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS) 2019-07-20 18:09:55.670823 [info] STRICT_PORT_FORWARD defined as 'yes' 2019-07-20 18:09:55.704246 [info] ENABLE_PRIVOXY defined as 'yes' 2019-07-20 18:09:55.860724 [info] Starting Supervisor... 2019-07-20 18:09:56,047 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing 2019-07-20 18:09:56,047 INFO Set uid to user 0 succeeded 2019-07-20 18:09:56,050 INFO supervisord started with pid 6 2019-07-20 18:09:57,052 INFO spawned: 'start-script' with pid 152 2019-07-20 18:09:57,055 INFO spawned: 'watchdog-script' with pid 153 2019-07-20 18:09:57,055 INFO reaped unknown pid 7 2019-07-20 18:09:57,064 DEBG 'start-script' stdout output: [info] VPN is enabled, beginning configuration of VPN [debug] Environment variables defined as follows BASH=/bin/bash BASHOPTS=checkwinsize:cmdhist:complete_fullquote:extquote:force_fignore:globasciiranges:hostcomplete:interactive_comments:progcomp:promptvars:sourcepath BASH_ALIASES=() BASH_ARGC=() BASH_ARGV=() BASH_CMDS=() BASH_LINENO=([0]="0") BASH_SOURCE=([0]="/root/start.sh") BASH_VERSINFO=([0]="5" [1]="0" [2]="7" [3]="1" [4]="release" [5]="x86_64-pc-linux-gnu") BASH_VERSION='5.0.7(1)-release' DEBUG=true DELUGE_DAEMON_LOG_LEVEL=info DELUGE_WEB_LOG_LEVEL=info DIRSTACK=() ENABLE_PRIVOXY=yes EUID=0 GROUPS=() HOME=/home/nobody HOSTNAME=0c23a282d53f HOSTTYPE=x86_64 IFS=$' \t\n' LANG=en_GB.UTF-8 LAN_NETWORK=192.168.1.0/24 MACHTYPE=x86_64-pc-linux-gnu NAME_SERVERS=209.222.18.222,209.222.18.218 OPTERR=1 OPTIND=1 OSTYPE=linux-gnu PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin PGID=1000 PIPESTATUS=([0]="0") PPID=6 PS4='+ ' PUID=1000 PWD=/ RUN_UP_SCRIPT=yes SHELL=/bin/bash SHELLOPTS=braceexpand:hashall:interactive-comments SHLVL=1 STRICT_PORT_FORWARD=yes 2019-07-20 18:09:57,064 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2019-07-20 18:09:57,064 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2019-07-20 18:09:57,065 DEBG 'start-script' stdout output: SUPERVISOR_ENABLED=1 SUPERVISOR_GROUP_NAME=start-script SUPERVISOR_PROCESS_NAME=start-script TERM=xterm UID=0 UMASK=000 VPN_CONFIG='/config/openvpn/CA Toronto.ovpn' VPN_DEVICE_TYPE=tun0 VPN_ENABLED=yes VPN_OPTIONS= VPN_PASS=***REDACTED*** VPN_PORT=1198 VPN_PROTOCOL=udp VPN_PROV=pia VPN_REMOTE=ca-toronto.privateinternetaccess.com VPN_USER=***REDACTED*** _='[debug] Environment variables defined as follows' [debug] Directory listing of files in /config/openvpn as follows 2019-07-20 18:09:57,067 DEBG 'watchdog-script' stderr output: dos2unix: 2019-07-20 18:09:57,067 DEBG 'watchdog-script' stderr output: converting file /config/core.conf to Unix format... 2019-07-20 18:09:57,067 DEBG 'start-script' stdout output: total 32 drwxrwxr-x 2 nobody users 4096 Jul 20 18:09 . drwxrwxr-x 9 nobody users 4096 Jul 20 18:09 .. -rwxrwxr-x 1 nobody users 2025 Apr 5 13:44 ca.rsa.2048.crt -rwxrwxr-x 1 nobody users 3173 Jul 20 18:09 CA Toronto.ovpn -rwxrwxr-x 1 nobody users 20 Jul 20 17:41 credentials.conf -rwxrwxr-x 1 nobody users 869 Apr 5 13:44 crl.rsa.2048.pem 2019-07-20 18:09:57,068 DEBG 'watchdog-script' stdout output: [debug] Waiting for valid IP address from tunnel... 2019-07-20 18:09:57,126 DEBG 'start-script' stdout output: [debug] Contents of ovpn file /config/openvpn/CA Toronto.ovpn as follows... 2019-07-20 18:09:57,127 DEBG 'start-script' stdout output: remote ca-toronto.privateinternetaccess.com 1198 client dev tun proto udp resolv-retry infinite nobind persist-key cipher aes-128-cbc auth sha1 tls-client remote-cert-tls server auth-user-pass credentials.conf compress verb 1 <crl-verify> ***REDACTED*** </crl-verify> <ca> ***REDACTED*** </ca> disable-occ 2019-07-20 18:09:57,144 DEBG 'start-script' stdout output: [info] Default route for container is 172.17.0.1 2019-07-20 18:09:57,150 DEBG 'start-script' stdout output: [info] Adding 209.222.18.222 to /etc/resolv.conf 2019-07-20 18:09:57,156 DEBG 'start-script' stdout output: [info] Adding 209.222.18.218 to /etc/resolv.conf 2019-07-20 18:10:27,192 DEBG 'start-script' stderr output: Error: error sending query: Could not send or receive, because of network error 2019-07-20 18:10:27,194 DEBG 'start-script' stdout output: [crit] ca-toronto.privateinternetaccess.com cannot be resolved, possible DNS issues 2019-07-20 18:10:27,195 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 139819682697000 for <Subprocess at 139819682747112 with name start-script in state RUNNING> (stdout)> 2019-07-20 18:10:27,195 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 139819682696272 for <Subprocess at 139819682747112 with name start-script in state RUNNING> (stderr)> 2019-07-20 18:10:27,195 INFO exited: start-script (exit status 1; not expected) 2019-07-20 18:10:27,195 DEBG received SIGCHLD indicating a child quit Quote Link to comment
binhex Posted July 21, 2019 Author Share Posted July 21, 2019 Adding 209.222.18.218 to /etc/resolv.conf2019-07-20 18:10:27,192 DEBG 'start-script' stderr output:Error: error sending query: Could not send or receive, because of network error2019-07-20 18:10:27,194 DEBG 'start-script' stdout output:[crit] ca-toronto.privateinternetaccess.com cannot be resolved, possible DNS issues2019-07-20 18:10:27,195 DEBG fd 8 closed, stopped monitoring (stdout)>2019-07-20 18:10:27,195 DEBG fd 10 closed, stopped monitoring (stderr)>2019-07-20 18:10:27,195 INFO exited: start-script (exit status 1; not expected)2019-07-20 18:10:27,195 DEBG received SIGCHLD indicating a child quit[/code] You have DNS resolution issues, this may be transitory or maybe permanent in which case you would need to change the name servers you are using. you are also in the wrong support thread this is for deluge only so any replies please put in delugevpnSent from my CLT-L09 using Tapatalk Quote Link to comment
binhex Posted July 21, 2019 Author Share Posted July 21, 2019 Here you goLog for binhex-deluge.htmSo looking at your log I can only assume you have have file system corruption on your cache drive as it seems this container is unable to create files as can be seen by the cp command line in the logSent from my CLT-L09 using Tapatalk 1 Quote Link to comment
be4con Posted July 21, 2019 Share Posted July 21, 2019 (edited) 7 hours ago, binhex said: So looking at your log I can only assume you have have file system corruption on your cache drive as it seems this container is unable to create files as can be seen by the cp command line in the log Sent from my CLT-L09 using Tapatalk That sounds serious - any idea what I need to do to resolve it? EDIT: Actually when I pondered on that statement, I realised I wasn't 100% sure what you meant by cache drive and a little research made me realise that I don't have a cache drive, just the 3 disks in my array and a parity disk. So, I can't have a corrupt file system on my cache drive! Any other ideas? Is it worth me just deleting the image and starting from fresh? If so can I rescue my torrent state? Edited July 21, 2019 by be4con Quote Link to comment
binhex Posted July 22, 2019 Author Share Posted July 22, 2019 23 hours ago, be4con said: That sounds serious - any idea what I need to do to resolve it? EDIT: Actually when I pondered on that statement, I realised I wasn't 100% sure what you meant by cache drive and a little research made me realise that I don't have a cache drive, just the 3 disks in my array and a parity disk. So, I can't have a corrupt file system on my cache drive! Any other ideas? Is it worth me just deleting the image and starting from fresh? If so can I rescue my torrent state? ahh ok writing to the array directly, in that case then i would try re-creating your docker image file, see the procedure here for how to do this:- https://forums.unraid.net/topic/36647-official-guide-restoring-your-docker-applications-in-a-new-image-file/ 1 Quote Link to comment
be4con Posted July 22, 2019 Share Posted July 22, 2019 2 hours ago, binhex said: ahh ok writing to the array directly, in that case then i would try re-creating your docker image file, see the procedure here for how to do this:- https://forums.unraid.net/topic/36647-official-guide-restoring-your-docker-applications-in-a-new-image-file/ I get the following error when trying to add the container back in: Pulling image: binhex/arch-deluge:latest TOTAL DATA PULLED: 0 B Command:root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='binhex-deluge' --net='bridge' --log-opt max-size='50m' --log-opt max-file='1' -e TZ="Europe/London" -e HOST_OS="Unraid" -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -p '8112:8112/tcp' -p '58846:58846/tcp' -p '58946:58946/tcp' -p '58946:58946/udp' -v '/mnt/cache/appdata/data':'/data':'rw' -v '/mnt/user/appdata/binhex-deluge':'/config':'rw' 'binhex/arch-deluge' Unable to find image 'binhex/arch-deluge:latest' locally /usr/bin/docker: Error response from daemon: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 209.244.0.4:53: read udp 192.168.11.208:39687->209.244.0.4:53: read: no route to host. See '/usr/bin/docker run --help'. The command failed. Any suggestions? Quote Link to comment
binhex Posted July 22, 2019 Author Share Posted July 22, 2019 3 hours ago, be4con said: read: no route to host. i would say you have networking issues, either on your unraid host or in general on your home lan, check unraid can resolve hostnames and ping, if thats ok then check firewall/router/vlans/modem etc. 1 Quote Link to comment
be4con Posted July 23, 2019 Share Posted July 23, 2019 (edited) 14 hours ago, binhex said: i would say you have networking issues, either on your unraid host or in general on your home lan, check unraid can resolve hostnames and ping, if thats ok then check firewall/router/vlans/modem etc. That was wierd, no network issues but that problem self resolved. Different error this morning but at least it is able to pull files now: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='binhex-deluge' --net='bridge' --log-opt max-size='50m' --log-opt max-file='1' -e TZ="Europe/London" -e HOST_OS="Unraid" -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -p '8112:8112/tcp' -p '58846:58846/tcp' -p '58946:58946/tcp' -p '58946:58946/udp' -v '/mnt/cache/appdata/data':'/data':'rw' -v '/mnt/user/appdata/binhex-deluge':'/config':'rw' 'binhex/arch-deluge' 07cb605bb9c7e448a47588de8e3dbab63d2ed1f626cebaff3b018d57139056ff /usr/bin/docker: Error response from daemon: error while creating mount source path '/mnt/user/appdata/binhex-deluge': mkdir /mnt/user/appdata/binhex-deluge: no medium found. The command failed. This is really frustrating. Any suggestions on what to do next? EDIT: I've cracked it. I had noticed that I couldn't do anything in my appdata folder, it wouldn't allow me to add or take anything from the folder. I tried to change permissions and that didn't change anything. So, I decided to play around with the Unraid settings for that share and see what happened. I noticed that the 'Use Cache Disk' option was set to 'Only'. I changed it to 'No' and bingo. I've never touched that setting, so I have no idea why it was set to 'Only' and I can only assume it happened the last time the OS updated. It does fit in with what you saw in the log though. Thanks for helping me work through this, really appreciated. I just need to sort out the deluge config again now and I'm back (almost) to where I started. Edited July 23, 2019 by be4con SOLVED! Quote Link to comment
be4con Posted July 23, 2019 Share Posted July 23, 2019 Hopefully this is my last support question - I know I should know the answer to this problem, but I'm struggling. My seeding torrents have all reappeared showing as 100% but I need to reconfigure Deluge. My torrents download to the following share: /mnt/user/Downloads/deluge/incomplete and when they are complete they move to: /mnt/user/Downloads/deluge/complete My watch folder for torrents is: /mnt/user/Downloads/deluge/torrentfiles I'm pretty sure in the deluge config previously these locations were just listed as /data/incomplete, /data/complete and /data/torrentfiles but that no longer seems to be correct. If I set it as that then the torrents reset to 0% and start to download again. I can't find where they are downloading to though, nor where they move to when completed. I tried using the paths above, but those aren't right either. Similarly for the AutoAdd plugin it fails, complaining 'Path does not exist' Quote Link to comment
JonathanM Posted July 23, 2019 Share Posted July 23, 2019 33 minutes ago, be4con said: I can't find where they are downloading to though, nor where they move to when completed. https://forums.unraid.net/topic/57181-real-docker-faq/#comment-564306 1 Quote Link to comment
be4con Posted July 23, 2019 Share Posted July 23, 2019 19 minutes ago, jonathanm said: https://forums.unraid.net/topic/57181-real-docker-faq/#comment-564306 Brilliant, thanks. I should have known that, but it's such a long time since I set this up last that it's all gone from memory and I couldn't find it online when I searched. Quote Link to comment
Timbiotic Posted July 30, 2019 Share Posted July 30, 2019 (edited) On 1/21/2016 at 3:56 PM, binhex said: IMPORTANT - Deluge 2.x compatibility issues There is currently an issue with radarr connecting to deluge 2.x, they havent got support in place for deluge 2.x yet, sonarr looks to have some basic support in place but there may still be some small issues. see here for issue for radarr:- https://github.com/Radarr/Radarr/issues/3562 see here for issue for sonarr:- https://github.com/Sonarr/Sonarr/issues/2412 According to a post on the sonarr issue thread, this is the problem in a nutshell:- https://github.com/Sonarr/Sonarr/issues/2412#issuecomment-469070076 couchpotato at this time looks to be unable to communicate with deluge 2.x (even against latest commits to master), no information shown in log, even if logging level set to debug. There is also the possibility that private trackers have not vetted deluge 2.x as a torrent client and thus it may not be permitted at this time (check with your private site admin). if you wish to rollback to Deluge 1.x then follow Q5. from the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/unraid.md I’m trying to make my thin client work again in windows, so I need deluge 1.x. I’ve checked the old builds and only see 2.0 or higher. Is this the correct url https://hub.docker.com/r/binhex/arch-deluge/builds I saw a tag tab but when i put in "binhex/arch-deluge:1.3.15_18_ge050905b2-1-01" it fails because i am guessing the build is missing Edited July 30, 2019 by Timbiotic Quote Link to comment
binhex Posted July 30, 2019 Author Share Posted July 30, 2019 1 hour ago, Timbiotic said: Is this the correct url https://hub.docker.com/r/binhex/arch-deluge/builds here is the procedure for targeting a specific tagged image, see Q5.:- https://github.com/binhex/documentation/blob/master/docker/faq/unraid.md Quote Link to comment
Timbiotic Posted July 30, 2019 Share Posted July 30, 2019 22 minutes ago, binhex said: here is the procedure for targeting a specific tagged image, see Q5.:- https://github.com/binhex/documentation/blob/master/docker/faq/unraid.md Right and when i go to builds as it says in the instructions there isnt anything below 2.0 so how do i tag 1.3.15_18 if there are no builds for it? Quote Link to comment
binhex Posted July 30, 2019 Author Share Posted July 30, 2019 14 minutes ago, Timbiotic said: Right and when i go to builds as it says in the instructions there isnt anything below 2.0 so how do i tag 1.3.15_18 if there are no builds for it? ahh sorry looks like the views have changed, try the 'Tags' tab instead to view all available tagged images, then follow the rest of the instructions in the linked faq. 1 Quote Link to comment
neitakk Posted July 31, 2019 Share Posted July 31, 2019 (edited) After a fresh unraid install, and adding the Deluge app, setting it up with shared folder "downloads" on install, it says "/home/nobody/downloads" in the Deluge settings, and I can't figure out why. *edit: I know I can change the address, but I was sure the file path came up correctly before. Therefore, I feel that there may be something wrong with my setup that I cannot see myself Edited July 31, 2019 by neitakk Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.