[Support] binhex - SABnzbdVPN

binhex · July 14, 2016

ok inclusion of strong certs and higher encryption ciphers is now done, if you want to enable this then please do the following:-

1. go to unraid webui, left click docker container icon and select edit

2. click on advanced view (top right) and add in environment variable named "STRONG_CERTS" and set the value to "yes"

3. change the "VPN_PORT" value to "1197"

4. click on save.

The action of clicking on "save" should force a pull down of the latest image as well as saving the config changes, if this doesnt happen then please click on "advanced view" in the main list view showing all your containers, then select the small grey "force update" link.

net2wire · July 14, 2016

Thanks for the stronger encryption Binhex. I don't see very much difference in speed if any at all.

newoski · July 14, 2016

ok inclusion of strong certs and higher encryption ciphers is now done, if you want to enable this then please do the following:-

1. go to unraid webui, left click docker container icon and select edit

2. click on advanced view (top right) and add in environment variable named "STRONG_CERTS" and set the value to "yes"

3. change the "VPN_PORT" value to "1197"

4. click on save.

The action of clicking on "save" should force a pull down of the latest image as well as saving the config changes, if this doesnt happen then please click on "advanced view" in the main list view showing all your containers, then select the small grey "force update" link.

Everything is working perfectly. No loss in speed. Could you clarify what makes this encryption option stronger?

net2wire · July 14, 2016

btw after several tries of editing as suggested I ended up removing docker+image files and instead reinstalled via CA. Several of the fields seemed different than the previous install, and I added field paths as necessary (ex: "incomplete" field) and all is well now. Logs look good. No speed issues.

usermod: no changes
[info] Env var PUID defined as 99
[info] Env var PGID defined as 100
[info] Permissions already set for /config and /data
[info] Starting Supervisor...
2016-07-14 14:57:13,075 CRIT Set uid to user 0
2016-07-14 14:57:13,075 INFO Included extra file "/etc/supervisor/conf.d/sabnzbdvpn.conf" during parsing
2016-07-14 14:57:13,079 INFO supervisord started with pid 25
2016-07-14 14:57:14,081 INFO spawned: 'start-script' with pid 28
2016-07-14 14:57:14,082 INFO spawned: 'sabnzbd-script' with pid 29
2016-07-14 14:57:14,083 INFO spawned: 'privoxy-script' with pid 30
2016-07-14 14:57:14,091 DEBG 'sabnzbd-script' stdout output:
[info] VPN is enabled, checking VPN tunnel local ip is valid

2016-07-14 14:57:14,091 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2016-07-14 14:57:14,091 INFO success: sabnzbd-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2016-07-14 14:57:14,091 INFO success: privoxy-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2016-07-14 14:57:14,091 DEBG 'privoxy-script' stdout output:
[info] VPN is enabled, checking VPN tunnel local ip is valid

2016-07-14 14:57:14,094 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2016-07-14 14:57:14,105 DEBG 'start-script' stdout output:
[info] VPN provider defined as pia

2016-07-14 14:57:14,107 DEBG 'start-script' stdout output:
[info] VPN strong certs defined, copying to /config/openvpn/...

2016-07-14 14:57:14,110 DEBG 'start-script' stdout output:
[info] VPN config file (ovpn extension) is located at /config/openvpn/openvpn.ovpn

2016-07-14 14:57:14,113 DEBG 'start-script' stdout output:
[info] Env vars defined via docker -e flags for remote host, port and protocol, writing values to ovpn file...

2016-07-14 14:57:14,123 DEBG 'start-script' stdout output:
[info] VPN provider remote gateway defined as XXX.XXXXXXXX.com
[info] VPN provider remote port defined as 1197
[info] VPN provider remote protocol defined as udp

2016-07-14 14:57:14,132 DEBG 'start-script' stdout output:
[info] VPN provider username defined as "username"

2016-07-14 14:57:14,139 DEBG 'start-script' stdout output:
[info] VPN provider password defined as "password"

2016-07-14 14:57:14,142 DEBG 'start-script' stdout output:
[warn] Password contains characters which could cause authentication issues, please consider changing this if possible

2016-07-14 14:57:14,161 DEBG 'start-script' stdout output:
[info] Default route for container is 172.17.0.1

2016-07-14 14:57:14,170 DEBG 'start-script' stdout output:
[info] Setting permissions recursively on /config/openvpn...

2016-07-14 14:57:14,180 DEBG 'start-script' stdout output:
[info] Adding 192.168.2.0/24 as route via docker eth0

2016-07-14 14:57:14,180 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2016-07-14 14:57:14,181 DEBG 'start-script' stdout output:
default via 172.17.0.1 dev eth0
172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.11
192.168.2.0/24 via 172.17.0.1 dev eth0

2016-07-14 14:57:14,181 DEBG 'start-script' stdout output:
--------------------

2016-07-14 14:57:14,185 DEBG 'start-script' stdout output:
[info] iptable_mangle support detected, adding fwmark for tables

2016-07-14 14:57:14,204 DEBG 'start-script' stdout output:
[info] Adding additional incoming port 8087 for eth0

2016-07-14 14:57:14,232 DEBG 'start-script' stdout output:
[info] Adding additional outgoing port 8087 for eth0

2016-07-14 14:57:14,241 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2016-07-14 14:57:14,242 DEBG 'start-script' stdout output:
-P INPUT DROP
-P FORWARD ACCEPT
-P OUTPUT DROP
-A INPUT -i tun0 -j ACCEPT
-A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A INPUT -i eth0 -p udp -m udp --sport 1197 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 8080 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --sport 8080 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 8090 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --sport 8090 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 8087 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --sport 8087 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 8118 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --sport 8118 -j ACCEPT
-A INPUT -p udp -m udp --sport 53 -j ACCEPT
-A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A OUTPUT -o tun0 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A OUTPUT -o eth0 -p udp -m udp --dport 1197 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --dport 8080 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 8080 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --dport 8090 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 8090 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --dport 8087 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 8087 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --dport 8118 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 8118 -j ACCEPT
-A OUTPUT -p udp -m udp --dport 53 -j ACCEPT
-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A OUTPUT -o lo -j ACCEPT

2016-07-14 14:57:14,242 DEBG 'start-script' stdout output:
--------------------

2016-07-14 14:57:14,242 DEBG 'start-script' stdout output:
[info] nameservers

2016-07-14 14:57:14,243 DEBG 'start-script' stdout output:
nameserver 8.8.8.8
nameserver 8.8.4.4

2016-07-14 14:57:14,244 DEBG 'start-script' stdout output:
--------------------
[info] Starting OpenVPN...

2016-07-14 14:57:14,249 DEBG 'start-script' stdout output:
Thu Jul 14 14:57:14 2016 OpenVPN 2.3.11 x86_64-unknown-linux-gnu [sSL (OpenSSL)] [LZO] [EPOLL] [MH] [iPv6] built on May 12 2016
Thu Jul 14 14:57:14 2016 library versions: OpenSSL 1.0.2h 3 May 2016, LZO 2.09
Thu Jul 14 14:57:14 2016 WARNING: file 'credentials.conf' is group or others accessible

2016-07-14 14:57:14,285 DEBG 'start-script' stdout output:
Thu Jul 14 14:57:14 2016 UDPv4 link local: [undef]
Thu Jul 14 14:57:14 2016 UDPv4 link remote: [AF_INET]172.98.67.53:1197

2016-07-14 14:57:14,372 DEBG 'start-script' stdout output:
Thu Jul 14 14:57:14 2016 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this

2016-07-14 14:57:14,820 DEBG 'start-script' stdout output:
Thu Jul 14 14:57:14 2016 WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1570', remote='link-mtu 1542'
Thu Jul 14 14:57:14 2016 WARNING: 'cipher' is used inconsistently, local='cipher AES-256-CBC', remote='cipher BF-CBC'
Thu Jul 14 14:57:14 2016 WARNING: 'auth' is used inconsistently, local='auth SHA256', remote='auth SHA1'
Thu Jul 14 14:57:14 2016 WARNING: 'keysize' is used inconsistently, local='keysize 256', remote='keysize 128'

2016-07-14 14:57:14,820 DEBG 'start-script' stdout output:
Thu Jul 14 14:57:14 2016 [88ayd890089d77d8fdfd788df7d8fd87] Peer Connection Initiated with [AF_INET]172.98.67.53:1197

2016-07-14 14:57:17,351 DEBG 'start-script' stdout output:
Thu Jul 14 14:57:17 2016 TUN/TAP device tun0 opened
Thu Jul 14 14:57:17 2016 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
Thu Jul 14 14:57:17 2016 /usr/bin/ip link set dev tun0 up mtu 1500

2016-07-14 14:57:17,352 DEBG 'start-script' stdout output:
Thu Jul 14 14:57:17 2016 /usr/bin/ip addr add dev tun0 local 10.118.1.6 peer 10.118.1.5

2016-07-14 14:57:17,362 DEBG 'start-script' stdout output:
Thu Jul 14 14:57:17 2016 Initialization Sequence Completed

2016-07-14 14:57:17,481 DEBG 'privoxy-script' stdout output:
[info] Configuring Privoxy...

2016-07-14 14:57:17,492 DEBG 'sabnzbd-script' stdout output:
[info] All checks complete, starting SABnzbd...

2016-07-14 14:57:17,533 DEBG 'privoxy-script' stdout output:
[info] All checks complete, starting Privoxy...

2016-07-14 14:57:17,534 DEBG 'privoxy-script' stderr output:
2016-07-14 14:57:17.534 2b7432906dc0 Info: Privoxy version 3.0.24
2016-07-14 14:57:17.534 2b7432906dc0 Info: Program name: /usr/bin/privoxy

binhex · July 15, 2016

ok inclusion of strong certs and higher encryption ciphers is now done, if you want to enable this then please do the following:-

1. go to unraid webui, left click docker container icon and select edit

2. click on advanced view (top right) and add in environment variable named "STRONG_CERTS" and set the value to "yes"

3. change the "VPN_PORT" value to "1197"

4. click on save.

The action of clicking on "save" should force a pull down of the latest image as well as saving the config changes, if this doesnt happen then please click on "advanced view" in the main list view showing all your containers, then select the small grey "force update" link.

Everything is working perfectly. No loss in speed. Could you clarify what makes this encryption option stronger?

you would really need to talk to PIA for a proper explanation, but in short the certificates used are of a larger key length and the ciphers used are more complex, and thus this should make any hack attempts difficult/impossible.

just to be clear, as far as im aware there were never any breaches even with the older less secure certs and ciphers, this is purely PIA upping their game a bit.

newoski · July 15, 2016

Cool. Thanks!

Sent from my HTC6535LVW using Tapatalk

Adam64 · July 15, 2016

I made the change to strong certs and got these warnings in the log:

2016-07-15 13:52:15,998 DEBG 'start-script' stdout output:

Fri Jul 15 13:52:15 2016 WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1570', remote='link-mtu 1542'

Fri Jul 15 13:52:15 2016 WARNING: 'cipher' is used inconsistently, local='cipher AES-256-CBC', remote='cipher BF-CBC'

Fri Jul 15 13:52:15 2016 WARNING: 'auth' is used inconsistently, local='auth SHA256', remote='auth SHA1'

Fri Jul 15 13:52:15 2016 WARNING: 'keysize' is used inconsistently, local='keysize 256', remote='keysize 128'

It still seems to start. Any need for concern?

unevent · July 16, 2016

I made the change to strong certs and got these warnings in the log:

2016-07-15 13:52:15,998 DEBG 'start-script' stdout output:

Fri Jul 15 13:52:15 2016 WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1570', remote='link-mtu 1542'

Fri Jul 15 13:52:15 2016 WARNING: 'cipher' is used inconsistently, local='cipher AES-256-CBC', remote='cipher BF-CBC'

Fri Jul 15 13:52:15 2016 WARNING: 'auth' is used inconsistently, local='auth SHA256', remote='auth SHA1'

Fri Jul 15 13:52:15 2016 WARNING: 'keysize' is used inconsistently, local='keysize 256', remote='keysize 128'

It still seems to start. Any need for concern?

Add "verb 5" to the config file and start the VPN again (without the " "). Look in the log file for Data Channel Decrypt and Encrypt headers. According to PIA, is shows those warnings as the local settings differ from remote settings. Not an issue if the Data Channel Encrypt & Decrypt report the proper ciphers being used. Example log taken from my pfsense box:

Jul 15 21:11:17 	openvpn 	75479 	WARNING: 'cipher' is used inconsistently, local='cipher AES-256-CBC', remote='cipher BF-CBC'
Jul 15 21:11:17 	openvpn 	75479 	WARNING: 'auth' is used inconsistently, local='auth SHA256', remote='auth SHA1'
Jul 15 21:11:17 	openvpn 	75479 	WARNING: 'keysize' is used inconsistently, local='keysize 256', remote='keysize 128'
Jul 15 21:11:17 	openvpn 	75479 	Data Channel Encrypt: Cipher 'AES-256-CBC' initialized with 256 bit key
Jul 15 21:11:17 	openvpn 	75479 	Data Channel Encrypt: Using 256 bit message hash 'SHA256' for HMAC authentication
Jul 15 21:11:17 	openvpn 	75479 	Data Channel Decrypt: Cipher 'AES-256-CBC' initialized with 256 bit key
Jul 15 21:11:17 	openvpn 	75479 	Data Channel Decrypt: Using 256 bit message hash 'SHA256' for HMAC authentication
Jul 15 21:11:17 	openvpn 	75479 	Control Channel: TLSv1.2, cipher TLSv1/SSLv3 DHE-RSA-AES256-GCM-SHA384, 4096 bit RSA

betaman · July 19, 2016

ok im stumped for now, i will have to rack my brain for any ideas, just to double check i did a clean install here and it started with no issues

Ok, I've successfully got strong encryption running on your DelugeVPN docker but I still can't get this docker to start. One thing I noticed is that nothing is written to the /config folder (in my case, /mnt/cache/appdata/SABnzbdVPN/). The directory is however created successfully when pull down the image. Here's the folder permissions of my /mnt/cache/appdata directory:

drwxrwxr-x  4 nobody users 113 Jul 19 10:11 SABnzbd/
drwxrwxrwx  2 nobody users   6 Jul 19 11:33 SABnzbdVPN/
drwxrwxrwx  7 nobody users 256 Jul 19 10:58 delugeVPN/
drwxrwxr-x  3 nobody users  24 Jul 19 11:19 downloads/
drwxrwxrwx 13 nobody users 168 Jun  2 13:29 emby/
drwxrwxrwx  7 nobody users 232 Jul 19 13:04 sonarr/

All other dockers are working correctly and the non-VPN verison of your SABnzbd docker is also working correctly?! Still stumped...just thought I'd check back on whether there's any other info I can provide? No SABnzbdVPN log is generated since no files are being written to the /config directory and the UnRAID log is useless.

Bjonness406 · July 19, 2016

ok im stumped for now, i will have to rack my brain for any ideas, just to double check i did a clean install here and it started with no issues

Ok, I've successfully got strong encryption running on your DelugeVPN docker but I still can't get this docker to start. One thing I noticed is that nothing is written to the /config folder (in my case, /mnt/cache/appdata/SABnzbdVPN/). The directory is however created successfully when pull down the image. Here's the folder permissions of my /mnt/cache/appdata directory:
drwxrwxr-x  4 nobody users 113 Jul 19 10:11 SABnzbd/
drwxrwxrwx  2 nobody users   6 Jul 19 11:33 SABnzbdVPN/
drwxrwxrwx  7 nobody users 256 Jul 19 10:58 delugeVPN/
drwxrwxr-x  3 nobody users  24 Jul 19 11:19 downloads/
drwxrwxrwx 13 nobody users 168 Jun  2 13:29 emby/
drwxrwxrwx  7 nobody users 232 Jul 19 13:04 sonarr/
All other dockers are working correctly and the non-VPN verison of your SABnzbd docker is also working correctly?! Still stumped...just thought I'd check back on whether there's any other info I can provide? No SABnzbdVPN log is generated since no files are being written to the /config directory and the UnRAID log is useless.

What about the docker log?

betaman · July 19, 2016

No SABnzbdVPN log is generated since no files are being written to the /config directory and the UnRAID log is useless.

What about the docker log?

See above. The log is stored in the /config directory (/mnt/cache/appdata/SABnzbdVPN/) and nothing is currently being written to this directory during docker install. I think this is the root cause of my problem but I can't seem to figure out how to fix it.

Bjonness406 · July 19, 2016

No SABnzbdVPN log is generated since no files are being written to the /config directory and the UnRAID log is useless.

What about the docker log?

See above. The log is stored in the /config directory (/mnt/cache/appdata/SABnzbdVPN/) and nothing is currently being written to this directory during docker install. I think this is the root cause of my problem but I can't seem to figure out how to fix it.

Not the application log, but the docker log.

Available at the docker tab in the unraid webgui (you may need to click advanced view)

betaman · July 19, 2016

Not the application log, but the docker log.

Available at the docker tab in the unraid webgui (you may need to click advanced view)

Hmmm...can't find it. I tried both views. The log link is for syslog and the other logs are docker dependent with this one being blank?! Maybe a screenshot?

Bjonness406 · July 19, 2016

Not the application log, but the docker log.

Available at the docker tab in the unraid webgui (you may need to click advanced view)

Hmmm...can't find it. I tried both views. The log link is for syslog and the other logs are docker dependent with this one being blank?! Maybe a screenshot?

First one in on regular view, second one is advanced view.

In advanced view you can see then the log did get created, how long is has been for the last change/edit.

Just click there I have marked with red.

width=250 https://i.imgur.com/Jjf3oPX.jpg[/img]

width=250 https://i.imgur.com/HrSJRXz.jpg[/img]

betaman · July 19, 2016

Not the application log, but the docker log.

Available at the docker tab in the unraid webgui (you may need to click advanced view)

Hmmm...can't find it. I tried both views. The log link is for syslog and the other logs are docker dependent with this one being blank?! Maybe a screenshot?

First one in on regular view, second one is advanced view.

In advanced view you can see then the log did get created, how long is has been for the last change/edit.

Just click there I have marked with red.

We were talking about the same thing. Mine says "none" which makes sense because my /config directory where the log is stored is completely empty.

MyKroFt · July 19, 2016

here is my folder and its contents

Myk

betaman · July 19, 2016

here is my folder and its contents

Myk

Which is exactly how the non-VPN SABnzbd folder looks (of course minus the VPN stuff). Where can I tell if the docker installed correctly or not? The syslog is not helpful and per my pic, the docker shows installed but stopped on my docker page. When I try to start it, nothing happens. I stopped the other SABnzbd docker (binhex version as well and works perfectly) to avoid a port conflict.

binhex · July 20, 2016

here is my folder and its contents

Myk

Which is exactly how the non-VPN SABnzbd folder looks (of course minus the VPN stuff). Where can I tell if the docker installed correctly or not? The syslog is not helpful and per my pic, the docker shows installed but stopped on my docker page. When I try to start it, nothing happens. I stopped the other SABnzbd docker (binhex version as well and works perfectly) to avoid a port conflict.

ok can you please ssh into unraid and run this command, it should give us a clue as to what is going on:-

docker logs <name of your sabnzbd container>

please paste the output here

i know youve stated above that the logs dont contain anything useful, but the above command should give us something.

also if you can screenshot your settings for the container, make sure to select the advanced view option so we can see all defined values, obviously hiding your username and password.

betaman · July 20, 2016

here is my folder and its contents

Myk

Which is exactly how the non-VPN SABnzbd folder looks (of course minus the VPN stuff). Where can I tell if the docker installed correctly or not? The syslog is not helpful and per my pic, the docker shows installed but stopped on my docker page. When I try to start it, nothing happens. I stopped the other SABnzbd docker (binhex version as well and works perfectly) to avoid a port conflict.

ok can you please ssh into unraid and run this command, it should give us a clue as to what is going on:-
docker logs <name of your sabnzbd container>
please paste the output here

i know youve stated above that the logs dont contain anything useful, but the above command should give us something.

also if you can screenshot your settings for the container, make sure to select the advanced view option so we can see all defined values, obviously hiding your username and password.

It's pretty much the same as before:

http://lime-technology.com/forum/index.php?topic=45822.msg482984#msg482984

Except now I get the notification there's no such container. If you review the pic I posted above, you can see the container is installed but not running. Log output works for SABnzbd and DelugeVPN (both are your dockers). See attached.

binhex · July 20, 2016

wrong name, your container is called "binhex-sabnzbdvpn"

betaman · July 20, 2016

wrong name, your container is called "binhex-sabnzbdvpn"

LOL...sorry. I forgot I left the default name to reduce variables. Now it is the exact same output.

binhex · July 20, 2016

wrong name, your container is called "binhex-sabnzbdvpn"

LOL...sorry. I forgot I left the default name to reduce variables. Now it is the exact same output.

ok now that is really wierd, so the container looks to do a big fat nothing, hmmm, ok cane you delete the container AND the image, then use the my templates again to select the config details you had earlier to repull it down.

one quick question, are you running anything on port 8080 or 8090 on your unraid host?, unmenu for instance?.

betaman · July 20, 2016

wrong name, your container is called "binhex-sabnzbdvpn"

LOL...sorry. I forgot I left the default name to reduce variables. Now it is the exact same output.

ok now that is really wierd, so the container looks to do a big fat nothing, hmmm, ok cane you delete the container AND the image, then use the my templates again to select the config details you had earlier to repull it down.

one quick question, are you running anything on port 8080 or 8090 on your unraid host?, unmenu for instance?.

I did that exact procedure the last 3 times (hence the change to the docker name). It's as if the docker isn't really installing because the /config directory never populates with any files.

The only thing running on ports 8080 and 8090 is SABnzbd. I completely removed the non-VPN version to avoid any possible conflict but the same result. The only think I haven't tried is blowing away my image file completely and reinstalling all dockers. I was thinking of upgrading to 6.2 RC2 if I go that far though.

binhex · July 20, 2016

wrong name, your container is called "binhex-sabnzbdvpn"

LOL...sorry. I forgot I left the default name to reduce variables. Now it is the exact same output.

ok now that is really wierd, so the container looks to do a big fat nothing, hmmm, ok cane you delete the container AND the image, then use the my templates again to select the config details you had earlier to repull it down.

one quick question, are you running anything on port 8080 or 8090 on your unraid host?, unmenu for instance?.

I did that exact procedure the last 3 times (hence the change to the docker name). It's as if the docker isn't really installing because the /config directory never populates with any files.

The only thing running on ports 8080 and 8090 is SABnzbd. I completely removed the non-VPN version to avoid any possible conflict but the same result. The only think I haven't tried is blowing away my image file completely and reinstalling all dockers. I was thinking of upgrading to 6.2 RC2 if I go that far though.

that is an option but i didnt really want to suggest that unless i run out of ideas (which i nearly have hehe). ok last thing to check, can you double check the folder you are pointing at on the host side does exist, this has to be true for all of the volume mappings you have defined, also double check there is no accidental whitespace at the start or the end of the paths (both container and host paths) for all defined volumes.

betaman · July 20, 2016

that is an option but i didnt really want to suggest that unless i run out of ideas (which i nearly have hehe). ok last thing to check, can you double check the folder you are pointing at on the host side does exist, this has to be true for all of the volume mappings you have defined, also double check there is no accidental whitespace at the start or the end of the paths (both container and host paths) for all defined volumes.

Attached is the output of my /mnt/cache/appdata/ directory. I used the dropdowns in the docker config to avoid any typos.

[Support] binhex - SABnzbdVPN

Recommended Posts

Link to comment

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

binhex

binhex

binhex

Posted Images

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Join the conversation