[ARCHIVE] binhex docker repository


Recommended Posts

Or binhex, clear your browser cache and then look at this:  http://lime-technology.com/forum/index.php?topic=37958.msg351212#msg351212

 

yep looks nasty :-(, i've just this minute updated all the templates to point at the newly created issue assets that i linked to a couple of posts ago, i have no idea how CA links to the images, im assuming it traverses the xml templates and uses that for the links to the images, right?, if that is true then it should be springing back to life right now.

 

im also assuming the post you linked to showing whats listed in my repo (http://lime-technology.com/forum/index.php?topic=37958.msg351212#msg351212) doesn't dynamically update the link to the images, so will need to be manually modified for the new url's, i would do this myself but i obviously don't have permissions to edit your post, please let me know if you know of a way i can help out, as i know it will be tedious to update.

 

Thanks again for your help Squid, its appreciated.

CA will automatically pick up the changes to the templates with the new url.  The post I'll update tonight (it's just a custom version of CA that creates the entire thread for me)

Link to comment

Weird, still broken for me. I tried refreshing applications in Community Applications, but it didn't help

 

yeah your a bit fast off the mark there mate :-), i needed to update all the links in all the templates, this has just been done, can you please refresh again and let me know if this is now fixed.

 

p.s. make sure you clear your browsers cache and you may also need to disable CA cache as well, not sure how to do this as i dont currently use CA but if you get stuck im sure Squid could help you - quote from earlier "Or you can try disabling local server caching within CA settings (which is it's default operational mode)"

 

cheers.

It takes up to 2 hours for the appfeed to pick up changes to the templates

Link to comment

binhex - The sabnzbdvpn docker was working for few days after the rollback and stopped working few days later. I do not recall updating this docker since I thought it was just better to wait it out for a while before any upgrades. Honestly I do not know why this stopped working. Please see the logs from the webgui below. Note that this was tried with a new container with explicitly set group permissions of 777 also when I saw the access permissions.

 

2016-01-05 18:39:33,021 CRIT Set uid to user 0
2016-01-05 18:39:33,021 WARN Included extra file "/etc/supervisor/conf.d/sabnzbdvpn.conf" during parsing
2016-01-05 18:39:33,023 INFO supervisord started with pid 1
2016-01-05 18:39:34,025 INFO spawned: 'privoxy' with pid 7
2016-01-05 18:39:34,025 INFO spawned: 'start' with pid 8
2016-01-05 18:39:34,026 INFO spawned: 'sabnzbd' with pid 9
2016-01-05 18:39:34,029 DEBG 'privoxy' stdout output:
[info] VPN is enabled, checking VPN tunnel local ip is valid

2016-01-05 18:39:34,029 INFO success: privoxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2016-01-05 18:39:34,029 INFO success: start entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2016-01-05 18:39:34,032 DEBG 'sabnzbd' stdout output:
[info] VPN is enabled, checking VPN tunnel local ip is valid

2016-01-05 18:39:34,033 DEBG 'start' stdout output:
[info] VPN is enabled, beginning configuration of OpenVPN

2016-01-05 18:39:34,036 DEBG 'start' stdout output:
[info] VPN provider defined as pia

2016-01-05 18:39:34,036 DEBG 'start' stdout output:
[info] VPN provider defined as pia

2016-01-05 18:39:34,038 DEBG 'start' stdout output:
[info] VPN provider remote gateway and port defined as nl.privateinternetaccess.com 1194

2016-01-05 18:39:34,061 DEBG 'start' stderr output:
RTNETLINK answers: Operation not permitted

2016-01-05 18:39:34,062 DEBG 'start' stderr output:
RTNETLINK answers: Operation not permitted

2016-01-05 18:39:34,062 DEBG 'start' stderr output:
RTNETLINK answers: Operation not permitted

2016-01-05 18:39:34,063 DEBG 'start' stderr output:
RTNETLINK answers: Operation not permitted

2016-01-05 18:39:34,063 DEBG 'start' stdout output:
[info] ip routing table

2016-01-05 18:39:34,063 DEBG 'start' stdout output:
default via 172.17.42.1 dev eth0 

2016-01-05 18:39:34,063 DEBG 'start' stdout output:
172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.20 

2016-01-05 18:39:34,063 DEBG 'start' stdout output:
--------------------

2016-01-05 18:39:34,064 DEBG 'start' stderr output:
iptables v1.4.21: can't initialize iptables table `filter': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.

2016-01-05 18:39:34,065 DEBG 'start' stderr output:
iptables v1.4.21: can't initialize iptables table `filter': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.

2016-01-05 18:39:34,065 DEBG 'start' stderr output:
iptables v1.4.21: can't initialize iptables table `filter': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.

 

Oh okay, thanks for checking. I use the VPN version since some newsnet aggregators are do not support SSL (downloading API's). It just gives me the confidence running the VPN version of SABnzbd and there is no/negligible hit in downloading speeds for me.

 

So SABnzbdVPN still has the connection issues and need to be rolled back to previous version.

 

My error, thought you were talking about delugevpn.  I just run reg sab, never saw the need to have my news run through a vpn as I'm only d/lding.

 

 

Also, most news providers support ssl connections, so traffic is obfuscated anyway if you use ssl.

 

hi htpcnewbie, sorry for not responding earlier, i saw tooviral's reply to you saying its working ok for him and assumed you saw the reply and found that it was a config issue or something on your end and we were all ok, it looks like this isnt the case eh. OK i can take a look at this but my testing is going to be very limited as i dont have an account for a usenet provider at the moment, so i can test the vpn side of things but cant prove that i can receive data over the tunnel.

 

Can you give me as much detail as possible as to what your seeing, post your supervisor log file, any errors your seeing in sabnzbd webuio (if you can access it), the more info i have to work with the better basically, I will try and take a look tonight if i get time.

 

edit - just going back a few posts and spotted this from yourself on the 31st dec http://lime-technology.com/forum/index.php?topic=38055.msg430223#msg430223 so are you saying it was working ok after the rollback of the packages and it broke AFTER this?.

 

ok i did manage to do some testing on this last night and can confirm a clean out of the box pull down of sabnzbdvpn does work as far as establishing a tunnel, i can access sabnzbd webui and i can see a valid ip for the vpn adapter, the log you sent with the permission denied messages is VERY odd, can you try deleting the container and image you have and re-pull down, you dont need to blow away your config, at least not for now.

Link to comment

tldr; how do I modify/write to the auth file for Deluge so I can log in?

 

Hello all -- I realize this may have been asked before but I tried searching...repeatedly...and could not find a resolution.

 

Started the Deluge container and attempting to log in. It's asking for a password so I opened the auth file and received a long string that I recognized from other portions of this thread. From my understanding, it's formatted:

 

username:password:10

 

I have tried copy/pasting, manually entering the string multiple times. I'm just not getting in at this point. Then I saw a message indicating that I need to add a line to the file. I realize it might be a stupid question to some (please forgive), but how do I modify this file? I've tried remotely accessing it from another computer, pushing an updated file over to it. I'm not able to access that area it seems. My auth file is located in /mnt/cache/appdata/deluge for reference.

Link to comment

Hi everyone,

 

I'm having a problem with Sonarr, when I try to access the webui it just shows the loading screen. I have just set it up with Deluge. The log shows:

 

2016-01-09 22:20:31,837 DEBG 'sonarr' stdout output:
[Error] DownloadedEpisodesImportService: Import failed, path does not exist or is not accessible by Sonarr: /complete/xxxxxxx

 

Thanks!

 

 

Link to comment

binhex, CHBMB - Thanks for checking. I am still lost as to why I get the errors. Yes, it was working for few days after you rolled back to previous version but I may have clicked on update accidentally, it is broken now. I have tried the following and I get the same error as before:

1. created a new docker app location, set perms to 777 and restarted

2. closed the docker plugin completely and restarted

3. restarted the server, pulled fresh image of sabnzbdvpn with a clean sabnzbd app location

 

None of the above worked and I am at loss as to what I need to try. The complete logs from the time I click on start docker to stop is copied below. I have also attached screenshots of my docker template. Please let me know if you need additional information or have any ideas that I can try.

 

One key learning from this exercise is I am going to take docker image backups as part of my weekly scripts in addition to the apps. Thank you again for the all the help and your time in sorting this!

 

 

2016-01-09 17:32:36,936 CRIT Set uid to user 0
2016-01-09 17:32:36,949 WARN Included extra file "/etc/supervisor/conf.d/sabnzbdvpn.conf" during parsing
2016-01-09 17:32:36,954 INFO supervisord started with pid 1
2016-01-09 17:32:37,955 INFO spawned: 'privoxy' with pid 7
2016-01-09 17:32:37,957 INFO spawned: 'start' with pid 8
2016-01-09 17:32:37,958 INFO spawned: 'sabnzbd' with pid 9
2016-01-09 17:32:37,961 DEBG 'privoxy' stdout output:
[info] VPN is enabled, checking VPN tunnel local ip is valid

2016-01-09 17:32:37,961 INFO success: privoxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2016-01-09 17:32:37,961 INFO success: start entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2016-01-09 17:32:37,962 DEBG 'sabnzbd' stdout output:
[info] VPN is enabled, checking VPN tunnel local ip is valid

2016-01-09 17:32:37,964 DEBG 'start' stdout output:
[info] VPN is enabled, beginning configuration of OpenVPN

2016-01-09 17:32:37,969 DEBG 'start' stdout output:
[info] VPN provider defined as pia
[info] VPN provider defined as pia

2016-01-09 17:32:37,976 DEBG 'start' stdout output:
[info] VPN provider remote gateway and port defined as nl.privateinternetaccess.com 1194

2016-01-09 17:32:38,026 DEBG 'start' stderr output:
RTNETLINK answers: Operation not permitted

2016-01-09 17:32:38,026 DEBG 'start' stderr output:
RTNETLINK answers: Operation not permitted

2016-01-09 17:32:38,027 DEBG 'start' stderr output:
RTNETLINK answers: Operation not permitted

2016-01-09 17:32:38,027 DEBG 'start' stderr output:
RTNETLINK answers: Operation not permitted

2016-01-09 17:32:38,027 DEBG 'start' stdout output:
[info] ip routing table

2016-01-09 17:32:38,028 DEBG 'start' stdout output:
default via 172.17.42.1 dev eth0 

2016-01-09 17:32:38,028 DEBG 'start' stdout output:
172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.7 

2016-01-09 17:32:38,028 DEBG 'start' stdout output:
--------------------

2016-01-09 17:32:38,032 DEBG 'start' stderr output:
iptables v1.4.21: can't initialize iptables table `filter': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.

2016-01-09 17:32:38,033 DEBG 'start' stderr output:
iptables v1.4.21: can't initialize iptables table `filter': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.

2016-01-09 17:32:38,034 DEBG 'start' stderr output:
iptables v1.4.21: can't initialize iptables table `filter': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.

2016-01-09 17:32:38,035 DEBG 'start' stderr output:
iptables v1.4.21: can't initialize iptables table `filter': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.

2016-01-09 17:32:38,036 DEBG 'start' stderr output:
iptables v1.4.21: can't initialize iptables table `filter': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.

2016-01-09 17:32:38,037 DEBG 'start' stderr output:
iptables v1.4.21: can't initialize iptables table `filter': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.

2016-01-09 17:32:38,037 DEBG 'start' stderr output:
iptables v1.4.21: can't initialize iptables table `filter': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.

2016-01-09 17:32:38,038 DEBG 'start' stderr output:
iptables v1.4.21: can't initialize iptables table `filter': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.

2016-01-09 17:32:38,039 DEBG 'start' stderr output:
iptables v1.4.21: can't initialize iptables table `filter': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.

2016-01-09 17:32:38,040 DEBG 'start' stderr output:
iptables v1.4.21: can't initialize iptables table `filter': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.

2016-01-09 17:32:38,040 DEBG 'start' stderr output:
iptables v1.4.21: can't initialize iptables table `filter': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.

2016-01-09 17:32:38,041 DEBG 'start' stderr output:
iptables v1.4.21: can't initialize iptables table `filter': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.

2016-01-09 17:32:38,041 DEBG 'start' stderr output:
iptables v1.4.21: can't initialize iptables table `filter': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.

2016-01-09 17:32:38,042 DEBG 'start' stderr output:
iptables v1.4.21: can't initialize iptables table `filter': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.

2016-01-09 17:32:38,042 DEBG 'start' stderr output:
iptables v1.4.21: can't initialize iptables table `filter': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.

2016-01-09 17:32:38,043 DEBG 'start' stderr output:
iptables v1.4.21: can't initialize iptables table `filter': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.

2016-01-09 17:32:38,044 DEBG 'start' stderr output:
iptables v1.4.21: can't initialize iptables table `filter': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.

2016-01-09 17:32:38,044 DEBG 'start' stderr output:
iptables v1.4.21: can't initialize iptables table `filter': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.

2016-01-09 17:32:38,045 DEBG 'start' stderr output:
iptables v1.4.21: can't initialize iptables table `filter': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.

2016-01-09 17:32:38,046 DEBG 'start' stderr output:
getsockopt failed strangely: Operation not permitted

2016-01-09 17:32:38,047 DEBG 'start' stderr output:
getsockopt failed strangely: Operation not permitted

2016-01-09 17:32:38,047 DEBG 'start' stderr output:
getsockopt failed strangely: Operation not permitted

2016-01-09 17:32:38,048 DEBG 'start' stderr output:
getsockopt failed strangely: Operation not permitted

2016-01-09 17:32:38,048 DEBG 'start' stderr output:
iptables v1.4.21: can't initialize iptables table `filter': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.

2016-01-09 17:32:38,049 DEBG 'start' stderr output:
iptables v1.4.21: can't initialize iptables table `filter': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.

2016-01-09 17:32:38,050 DEBG 'start' stderr output:
iptables v1.4.21: can't initialize iptables table `filter': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.

2016-01-09 17:32:38,050 DEBG 'start' stdout output:
[info] iptables

2016-01-09 17:32:38,050 DEBG 'start' stderr output:
iptables v1.4.21: can't initialize iptables table `filter': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.

2016-01-09 17:32:38,050 DEBG 'start' stdout output:
--------------------

2016-01-09 17:32:38,050 DEBG 'start' stdout output:
[info] nameservers

2016-01-09 17:32:38,050 DEBG 'start' stdout output:
nameserver 8.8.8.8
nameserver 8.8.4.4

2016-01-09 17:32:38,051 DEBG 'start' stdout output:
--------------------

2016-01-09 17:32:38,051 DEBG 'start' stdout output:
[info] Starting OpenVPN...

2016-01-09 17:32:38,082 DEBG 'start' stdout output:
Sat Jan 9 17:32:38 2016 OpenVPN 2.3.9 x86_64-unknown-linux-gnu [sSL (OpenSSL)] [LZO] [EPOLL] [MH] [iPv6] built on Dec 24 2015
Sat Jan 9 17:32:38 2016 library versions: OpenSSL 1.0.2e 3 Dec 2015, LZO 2.09
Sat Jan 9 17:32:38 2016 WARNING: file 'credentials.conf' is group or others accessible

2016-01-09 17:32:38,121 DEBG 'start' stdout output:
Sat Jan 9 17:32:38 2016 UDPv4 link local: [undef]
Sat Jan 9 17:32:38 2016 UDPv4 link remote: [AF_INET]46.166.190.183:1194

2016-01-09 17:32:38,245 DEBG 'start' stdout output:
Sat Jan 9 17:32:38 2016 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this

2016-01-09 17:32:38,628 DEBG 'start' stdout output:
Sat Jan 9 17:32:38 2016 [Private Internet Access] Peer Connection Initiated with [AF_INET]46.166.190.183:1194

2016-01-09 17:32:39,629 INFO success: sabnzbd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-01-09 17:32:41,002 DEBG 'start' stdout output:
Sat Jan 9 17:32:41 2016 ERROR: Cannot ioctl TUNSETIFF tun: Operation not permitted (errno=1)
Sat Jan 9 17:32:41 2016 Exiting due to fatal error

2016-01-09 17:32:41,003 DEBG 'start' stdout output:
[info] nameservers

2016-01-09 17:32:41,003 DEBG 'start' stdout output:
nameserver 8.8.8.8
nameserver 8.8.4.4

2016-01-09 17:32:41,003 DEBG 'start' stdout output:
--------------------
[info] Starting OpenVPN...

2016-01-09 17:32:41,005 DEBG 'start' stdout output:
Sat Jan 9 17:32:41 2016 OpenVPN 2.3.9 x86_64-unknown-linux-gnu [sSL (OpenSSL)] [LZO] [EPOLL] [MH] [iPv6] built on Dec 24 2015
Sat Jan 9 17:32:41 2016 library versions: OpenSSL 1.0.2e 3 Dec 2015, LZO 2.09
Sat Jan 9 17:32:41 2016 WARNING: file 'credentials.conf' is group or others accessible

2016-01-09 17:32:41,045 DEBG 'start' stdout output:
Sat Jan 9 17:32:41 2016 UDPv4 link local: [undef]
Sat Jan 9 17:32:41 2016 UDPv4 link remote: [AF_INET]46.166.190.183:1194

2016-01-09 17:32:41,165 DEBG 'start' stdout output:
Sat Jan 9 17:32:41 2016 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this

2016-01-09 17:32:41,553 DEBG 'start' stdout output:
Sat Jan 9 17:32:41 2016 [Private Internet Access] Peer Connection Initiated with [AF_INET]46.166.190.183:1194

2016-01-09 17:32:43,780 DEBG 'start' stdout output:
Sat Jan 9 17:32:43 2016 ERROR: Cannot ioctl TUNSETIFF tun: Operation not permitted (errno=1)
Sat Jan 9 17:32:43 2016 Exiting due to fatal error

2016-01-09 17:32:43,781 DEBG fd 9 closed, stopped monitoring (stdout)>
2016-01-09 17:32:43,781 DEBG fd 14 closed, stopped monitoring (stderr)>
2016-01-09 17:32:43,781 INFO exited: start (exit status 1; not expected)
2016-01-09 17:32:43,781 DEBG received SIGCLD indicating a child quit
2016-01-09 17:32:41,003 DEBG 'start' stdout output:
[info] nameservers

2016-01-09 17:32:41,003 DEBG 'start' stdout output:
nameserver 8.8.8.8
nameserver 8.8.4.4

2016-01-09 17:32:41,003 DEBG 'start' stdout output:
--------------------
[info] Starting OpenVPN...

2016-01-09 17:32:41,005 DEBG 'start' stdout output:
Sat Jan 9 17:32:41 2016 OpenVPN 2.3.9 x86_64-unknown-linux-gnu [sSL (OpenSSL)] [LZO] [EPOLL] [MH] [iPv6] built on Dec 24 2015
Sat Jan 9 17:32:41 2016 library versions: OpenSSL 1.0.2e 3 Dec 2015, LZO 2.09
Sat Jan 9 17:32:41 2016 WARNING: file 'credentials.conf' is group or others accessible

2016-01-09 17:32:41,045 DEBG 'start' stdout output:
Sat Jan 9 17:32:41 2016 UDPv4 link local: [undef]
Sat Jan 9 17:32:41 2016 UDPv4 link remote: [AF_INET]46.166.190.183:1194

2016-01-09 17:32:41,165 DEBG 'start' stdout output:
Sat Jan 9 17:32:41 2016 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this

2016-01-09 17:32:41,553 DEBG 'start' stdout output:
Sat Jan 9 17:32:41 2016 [Private Internet Access] Peer Connection Initiated with [AF_INET]46.166.190.183:1194

2016-01-09 17:32:43,780 DEBG 'start' stdout output:
Sat Jan 9 17:32:43 2016 ERROR: Cannot ioctl TUNSETIFF tun: Operation not permitted (errno=1)
Sat Jan 9 17:32:43 2016 Exiting due to fatal error

2016-01-09 17:32:43,781 DEBG fd 9 closed, stopped monitoring (stdout)>
2016-01-09 17:32:43,781 DEBG fd 14 closed, stopped monitoring (stderr)>
2016-01-09 17:32:43,781 INFO exited: start (exit status 1; not expected)
2016-01-09 17:32:43,781 DEBG received SIGCLD indicating a child quit
2016-01-09 17:35:35,384 WARN received SIGTERM indicating exit request
2016-01-09 17:35:35,384 DEBG killing sabnzbd (pid 9) with signal SIGTERM
2016-01-09 17:35:35,384 INFO waiting for privoxy, sabnzbd to die
2016-01-09 17:35:35,384 DEBG fd 19 closed, stopped monitoring (stderr)>
2016-01-09 17:35:35,384 DEBG fd 15 closed, stopped monitoring (stdout)>
2016-01-09 17:35:35,384 INFO stopped: sabnzbd (terminated by SIGTERM)
2016-01-09 17:35:35,384 DEBG received SIGCLD indicating a child quit
2016-01-09 17:35:35,403 INFO reaped unknown pid 23103
2016-01-09 17:35:35,403 DEBG received SIGCLD indicating a child quit
2016-01-09 17:35:35,403 DEBG killing privoxy (pid 7) with signal SIGTERM
2016-01-09 17:35:35,403 DEBG fd 8 closed, stopped monitoring (stderr)>
2016-01-09 17:35:35,403 DEBG fd 6 closed, stopped monitoring (stdout)>
2016-01-09 17:35:35,403 INFO stopped: privoxy (terminated by SIGTERM)
2016-01-09 17:35:35,403 DEBG received SIGCLD indicating a child quit

Done

 

 

 

ok i did manage to do some testing on this last night and can confirm a clean out of the box pull down of sabnzbdvpn does work as far as establishing a tunnel, i can access sabnzbd webui and i can see a valid ip for the vpn adapter, the log you sent with the permission denied messages is VERY odd, can you try deleting the container and image you have and re-pull down, you dont need to blow away your config, at least not for now.

SABNzbdVPN_screenshot1.jpg.97724ab1a94f59e25b774e38c1d544aa.jpg

SABNzbdVPN_screenshot2.jpg.548f6fcbaa2f787feb113785ec5823e7.jpg

SABNzbdVPN_screenshot3.jpg.a728bb041a178fc6e4cffc6497406b51.jpg

Link to comment

Ok, so I've never used SABnzbd before, but seeing as I use PIA as well I just pulled it and it's working fine...  :-\

 

Just to check, your PIA subscription hasn't subscribed has it?  Worth stating the obvious sometimes...  ???

 

Anyway here's my config...

 

MdkHMSB.jpg

 

Only thing that I noticed is that in your template there is no option for VPN proxy like I have on mine, so one more thing I thought of, although I can't see why it should make a difference is to delete your my-binhex-sabnzbdvpn template as well after deleting the container and the appdata folder...

 

uQlx9PO.jpg

 

 

 

Link to comment

Is there a way for me to check to see if sabnzbdvpn is in fact using the vpn tunnel?

 

I may be wrong, but I know binhex's delugeVPN has a "killswitch" if the VPN isn't up, no traffic is allowed to pass.  Can't imagine the sabnzbd container would be any different...

Link to comment

CHBMB - A big *hugz* to you! The only thing I did was delete the template and redo everything in the template (exactly same as before) and it works. I didn't have to even delete the old app files and no clean start. Something seemed to have been corrupted in the template and I didn't quite expect that.

 

In a nutshell the fix for the issue was - if your docker doesn't work as expected inspite of checking everything, start with a new template.

 

Ok, so I've never used SABnzbd before, but seeing as I use PIA as well I just pulled it and it's working fine...  :-\

 

Just to check, your PIA subscription hasn't subscribed has it?  Worth stating the obvious sometimes...  ???

 

Anyway here's my config...

 

MdkHMSB.jpg

 

Only thing that I noticed is that in your template there is no option for VPN proxy like I have on mine, so one more thing I thought of, although I can't see why it should make a difference is to delete your my-binhex-sabnzbdvpn template as well after deleting the container and the appdata folder...

 

uQlx9PO.jpg

Link to comment

Is there a way for me to check to see if sabnzbdvpn is in fact using the vpn tunnel?

 

I may be wrong, but I know binhex's delugeVPN has a "killswitch" if the VPN isn't up, no traffic is allowed to pass.  Can't imagine the sabnzbd container would be any different...

That would be great! Hopefully binhex can confirm...
Link to comment

sabnzbdvpn will stop downloading if the vpn tunnel is not established. You can check it using the approach below (assuming you can ssh into the server).

 

You can login to the sabnzbdvpn docker using 'docker exec -it binhex-sabnzbdvpn /bin/bash' after the docker is running.

'top' will show you which processes are running. When a nzb is downloading, you can kill ('kill -9 pid#) the openvpn process based on the pid from the 'top' command. You should see that the nzb download is stopped.

 

Is there a way for me to check to see if sabnzbdvpn is in fact using the vpn tunnel?

 

I may be wrong, but I know binhex's delugeVPN has a "killswitch" if the VPN isn't up, no traffic is allowed to pass.  Can't imagine the sabnzbd container would be any different...

That would be great! Hopefully binhex can confirm...

Link to comment

I'm having issues accessing the webUI for Deluge -- could I please get some help?

 

When I open the webUI it prompts me for a password. I enter the password for localhost and it returns an error message for an invalid password. I added a second line to the auth file with a new user since I saw some posts about doing this, although I'm not being prompted to specify a username. I still cannot access Deluge webUI.

 

Could someone please provide me with some direction for this? I'd be extremely grateful.

Link to comment

Is it possible for me to download straight to my user shares/array? I have a great number of files that I'd like to reseed longterm.

 

Please describe the process -- when I am in the Deluge UI and I define the path for the shares to the existing content, it does not succeed with a force recheck.

 

Plainly and simply, I'd like to download to and seed from the share. How do I set this up?

Link to comment

Fantastic. Just what I was after. And I'll try the same thing with delugevpn...

 

sabnzbdvpn will stop downloading if the vpn tunnel is not established. You can check it using the approach below (assuming you can ssh into the server).

 

You can login to the sabnzbdvpn docker using 'docker exec -it binhex-sabnzbdvpn /bin/bash' after the docker is running.

'top' will show you which processes are running. When a nzb is downloading, you can kill ('kill -9 pid#) the openvpn process based on the pid from the 'top' command. You should see that the nzb download is stopped.

Link to comment

Htpcnewbie I spotted your issue, if you look at your first screenshot you can see you must of accidentally unticked the privileged flag for sabnzbdvpn, that's why you were getting the permission denied messages, obviously going with a new template sets it to the correct config :-)

 

Link to comment

Is there a way for me to check to see if sabnzbdvpn is in fact using the vpn tunnel?

 

I may be wrong, but I know binhex's delugeVPN has a "killswitch" if the VPN isn't up, no traffic is allowed to pass.  Can't imagine the sabnzbd container would be any different...

That would be great! Hopefully binhex can confirm...

 

Confirmed, both sabnzbdvpn and delugevpn use the same base docker image which sets up Iptables, so they both work in identical ways to establish the VPN tunnel.

Link to comment

Htpcnewbie I spotted your issue, if you look at your first screenshot you can see you must of accidentally unticked the privileged flag for sabnzbdvpn, that's why you were getting the permission denied messages, obviously going with a new template sets it to the correct config :-)

 

I didn't spot that....  But nuke and pave for the win! 

 

Too late binhex I already had the big hugz!  ;D

 

It's great to understand the reason behind it though, I'd not spotted that myself. 

Link to comment

Htpcnewbie I spotted your issue, if you look at your first screenshot you can see you must of accidentally unticked the privileged flag for sabnzbdvpn, that's why you were getting the permission denied messages, obviously going with a new template sets it to the correct config :-)

 

I didn't spot that....  But nuke and pave for the win! 

 

Too late binhex I already had the big hugz!  ;D

 

It's great to understand the reason behind it though, I'd not spotted that myself.

 

Lol indeed you get the gold star mate, thanks for helping out it is appreciated.

Link to comment

Is it possible (and if so how) to use Deluge to download directly to and seed directly from my disks or shares? I just have /config and /data both located on the cache but I cannot find where Deluge is downloading the files to (/homes/nobody/Downloads ??) and when I attempt to seed an already completed torrent by pointing to either the user share or the specific disk on the array, Deluge can't seem to follow the path so it says it's 0% finished.

 

Is there a more efficient and unraid-friendly way to do what I'm asking that maybe I'm unaware of?

Link to comment
Guest
This topic is now closed to further replies.