Jump to content
binhex

[Support] binhex - DelugeVPN

4977 posts in this topic Last Reply

Recommended Posts

Posted (edited)
19 minutes ago, binhex said:

Just to be clear deluge v2.x DOES work, however you will need to update all plugins to v2.x compatible and make sure your deluge thin client is updated (if you use that). If you dont use the deluge thin client and you dont need third party plugins then you should be good - see post #3 in this thread for more details regards current limitations.

Indeed, I have been using deluge v2 for just over a week, and it is running just fine.  The thin client is working well - but I do run Linux for my desktop.  I like all the new features - a welcome upgrade!

 

I also use the CouchPotato docker and have it set to use Black hole to upload torrent/magnet files to deluge - it does everything I need.

Edited by PeterB

Share this post


Link to post
Indeed, but only in the case where there is a major issue, i.e. ip leakage, for now using the tags is the best way of switching back to v1.x.
 
Just to be clear deluge v2.x DOES work, however you will need to update all plugins to v2.x compatible and make sure your deluge thin client is updated (if you use that). If you dont use the deluge thin client and you dont need third party plugins then you should be good - see post #3 in this thread for more details regards current limitations.
Good to know, so does the web GUI fall into the 3rd party plugin category?

Wob

Sent from my Pixel 3 XL using Tapatalk

Share this post


Link to post
6 minutes ago, Wob76 said:

Good to know, so does the web GUI fall into the 3rd party plugin category?

The web ui (not to be confused with the deluge thin client gui) works fine, if you cannot access the web ui then there is another issue in play (probably config related).

Share this post


Link to post
The web ui (not to be confused with the deluge thin client gui) works fine, if you cannot access the web ui then there is another issue in play (probably config related).
I can't access the web UI with 2.0, but rolling back fixes it, did the configuration requirements change?

Sent from my Pixel 3 XL using Tapatalk

Share this post


Link to post
Posted (edited)
8 minutes ago, Wob76 said:

I can't access the web UI with 2.0, but rolling back fixes it, did the configuration requirements change?
 

I didn't have to alter any docker configuration, and the web UI works fine.  Have you tried clearing browser cache, etc.

Edited by PeterB

Share this post


Link to post
32 minutes ago, PeterB said:

I didn't have to alter any docker configuration, and the web UI works fine.  Have you tried clearing browser cache, etc.

Just to chime in - I've had no problems at all with the upgrade either.  Didn't have to change any settings (other than configure the columns displayed).

Share this post


Link to post
I didn't have to alter any docker configuration, and the web UI works fine.  Have you tried clearing browser cache, etc.

Yeah, I also tried an alternative browser, it's odd, 2.0 without VPN (PIA) works fine, v1 with VPN (PIA) no problem, only change between them is the repository being pulled. Are those with it working use PIA or another VPN provider?

 

I'll investigate further at some point but for now I'm happy with v1, might wait for the plugin support to be ported.

 

Thanks for the help.

 

Sent from my Pixel 3 XL using Tapatalk

 

 

 

Share this post


Link to post
8 minutes ago, Wob76 said:

it's odd, 2.0 without VPN (PIA) works fine, v1 with VPN (PIA) no problem, only change between them is the repository being pulled. Are those with it working use PIA or another VPN provider?

That's odd! As I understand it, that has to be a problem with the VPN tunnel being established.  If the VPN is down, all connections are disabled.  Why that should change between the two releases is a puzzle.  I would try re-configuring all the docker/container settings - particularly those around the VPN.  Sorry, I'm lazy to go back through your posts - is there anything odd at all in the container log relating to the VPN?

 

Yes, I'm using PIA, currently on the Czech endpoint.

Share this post


Link to post
7 minutes ago, PeterB said:

That's odd! As I understand it, that has to be a problem with the VPN tunnel being established.  If the VPN is down, all connections are disabled.  Why that should change between the two releases is a puzzle.  I would try re-configuring all the docker/container settings - particularly those around the VPN.  Sorry, I'm lazy to go back through your posts - is there anything odd at all in the container log relating to the VPN?

 

Yes, I'm using PIA, currently on the Czech endpoint.

I went over his supervisor log and run command, can't find a reason why this ain't working, exactly same setup as me from what I can see. Also using PIA with Czech endpoint. He tried several endpoint (or so he said) so not really sure what is causing this issue.

 

Does anything work with 2.0 when the VPN is enabled @Wob76 ? Is it GUi that's down but couch/radarr/sonarr and such reach it?

Share this post


Link to post

@binhex  i finaly got deluge working correctly on V2.  pia had a special char that was in user name i didnt think much of it since it worked on V1.    anyways how does one update the plugins to work with V2?  namely the extractor and label plugin i use but plugin list is blank.

Share this post


Link to post
5 minutes ago, dirknina said:

how does one update the plugins to work with V2?  

They need to be updated by whoever the 3rd party developer is for the plugin from python v2 to python v3. Of course anyone can update them and then submit a pull request on github. Quite a few Deluge plugins are still waiting for their individual developers to update them.

 

You might want to check the github pages for those plugins. In some cases pull request are pending but haven’t been merged. I know this is true for AutoRemovePlus.

Share this post


Link to post

I had DelugeVPN working great and then I was screwing around on my server and wiped out all my configs (with no backups - lesson learned). I re-setup the docker with what I thought was identical settings to before, but now I can't seem to connect to peers on my private trackers (multiple different trackers).

 

I'm using v2.0.3 and PIA connecting to CA-Toronto. I can download public torrents just fine, and v2 is white-listed by my trackers so there shouldn't be an issue there. I've unchecked Peer Exchange and DHT, but still no luck. I've even tried with "VPN_ENABLED" set to no - no dice.

 

Any ideas?? This is very frustrating, because I had it working just fine!

Share this post


Link to post
I had DelugeVPN working great and then I was screwing around on my server and wiped out all my configs (with no backups - lesson learned). I re-setup the docker with what I thought was identical settings to before, but now I can't seem to connect to peers on my private trackers (multiple different trackers).
 
I'm using v2.0.3 and PIA connecting to CA-Toronto. I can download public torrents just fine, and v2 is white-listed by my trackers so there shouldn't be an issue there. I've unchecked Peer Exchange and DHT, but still no luck. I've even tried with "VPN_ENABLED" set to no - no dice.
 
Any ideas?? This is very frustrating, because I had it working just fine!
If you can download from public torrent sites then you have no connectivity issues so I would suspect that your private index site does not permit deluge v2 yet, double check with site admin.

Sent from my CLT-L09 using Tapatalk

Share this post


Link to post

So I've been trying to figure this out for a couple days. This my first time setting up delugevpn on this machine, so I don't have any previous config files or anything. My issue is that once connected to the webui, I can't figure out what password it wants me to enter. I've checked the auth file and the password in there is a random string of characters. It does not work, even when copied and pasted. If I edit the file and add admin:deluge:10 and restart the container, it still does not work. I have tried deleting the file, and recreating it with only admin:deluge:10, but after restarting the docker container, it appends a new entry to it with a new random password, that again does not work.

 

Here is my current auth file

admin:deluge:10
localclient:e55c8d0f44919b92be1c397663f1e2670063f729:10

and here is my supervisord.log

Created by...
___.   .__       .__                   
\_ |__ |__| ____ |  |__   ____ ___  ___
 | __ \|  |/    \|  |  \_/ __ \\  \/  /
 | \_\ \  |   |  \   Y  \  ___/ >    < 
 |___  /__|___|  /___|  /\___  >__/\_ \
     \/        \/     \/     \/      \/
   https://hub.docker.com/u/binhex/

2019-07-22 18:25:14.235708 [info] System information Linux 327ef426dad0 5.0.0-20-generic #21-Ubuntu SMP Mon Jun 24 09:32:09 UTC 2019 x86_64 GNU/Linux
2019-07-22 18:25:14.259674 [info] PUID defined as '1000'
2019-07-22 18:25:14.284497 [info] PGID defined as '130'
2019-07-22 18:25:14.323747 [info] UMASK defined as '000'
2019-07-22 18:25:14.346967 [info] Permissions already set for volume mappings
2019-07-22 18:25:14.373322 [info] DELUGE_DAEMON_LOG_LEVEL defined as 'info'
2019-07-22 18:25:14.396998 [info] DELUGE_WEB_LOG_LEVEL defined as 'info'
2019-07-22 18:25:14.423869 [info] VPN_ENABLED defined as 'yes'
2019-07-22 18:25:14.454512 [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-22 18:25:14.489628 [info] VPN remote line defined as 'remote ca-toronto.privateinternetaccess.com 1198'
2019-07-22 18:25:14.514545 [info] VPN_REMOTE defined as 'ca-toronto.privateinternetaccess.com'
2019-07-22 18:25:14.540598 [info] VPN_PORT defined as '1198'
2019-07-22 18:25:14.567639 [info] VPN_PROTOCOL defined as 'udp'
2019-07-22 18:25:14.591472 [info] VPN_DEVICE_TYPE defined as 'tun0'
2019-07-22 18:25:14.615159 [info] VPN_PROV defined as 'pia'
2019-07-22 18:25:14.639732 [info] LAN_NETWORK defined as '192.168.1.0/24'
2019-07-22 18:25:14.663797 [info] NAME_SERVERS defined as '209.222.18.222,1.1.1.1,8.8.8.8,209.222.18.218,1.0.0.1,8.8.4.4'
2019-07-22 18:25:14.687306 [info] VPN_USER defined as 'PIA_USER'
2019-07-22 18:25:14.710806 [info] VPN_PASS defined as 'PIA_PASS'
2019-07-22 18:25:14.734295 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2019-07-22 18:25:14.757749 [info] STRICT_PORT_FORWARD defined as 'yes'
2019-07-22 18:25:14.781409 [info] ENABLE_PRIVOXY defined as 'yes'
2019-07-22 18:25:14.805321 [info] Starting Supervisor...
2019-07-22 18:25:14,986 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing
2019-07-22 18:25:14,986 INFO Set uid to user 0 succeeded
2019-07-22 18:25:14,990 INFO supervisord started with pid 6
2019-07-22 18:25:15,991 INFO spawned: 'start-script' with pid 147
2019-07-22 18:25:15,992 INFO spawned: 'watchdog-script' with pid 148
2019-07-22 18:25:15,992 INFO reaped unknown pid 7
2019-07-22 18:25:15,997 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2019-07-22 18:25:15,997 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2019-07-22 18:25:15,997 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2019-07-22 18:25:15,999 DEBG 'watchdog-script' stderr output:
dos2unix: 
2019-07-22 18:25:15,999 DEBG 'watchdog-script' stderr output:
converting file /config/core.conf to Unix format...

2019-07-22 18:25:16,038 DEBG 'start-script' stdout output:
[info] Default route for container is 172.17.0.1

2019-07-22 18:25:16,041 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.222 to /etc/resolv.conf

2019-07-22 18:25:16,044 DEBG 'start-script' stdout output:
[info] Adding 1.1.1.1 to /etc/resolv.conf

2019-07-22 18:25:16,047 DEBG 'start-script' stdout output:
[info] Adding 8.8.8.8 to /etc/resolv.conf

2019-07-22 18:25:16,050 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.218 to /etc/resolv.conf

2019-07-22 18:25:16,052 DEBG 'start-script' stdout output:
[info] Adding 1.0.0.1 to /etc/resolv.conf

2019-07-22 18:25:16,055 DEBG 'start-script' stdout output:
[info] Adding 8.8.4.4 to /etc/resolv.conf

2019-07-22 18:25:16,101 DEBG 'start-script' stdout output:
[info] Attempting to load tun kernel module...

2019-07-22 18:25:16,102 DEBG 'start-script' stderr output:
modprobe: FATAL: Module tun not found in directory /lib/modules/5.0.0-20-generic

2019-07-22 18:25:16,102 DEBG 'start-script' stdout output:
[warn] Unable to load tun kernel module using modprobe, trying insmod...

2019-07-22 18:25:16,103 DEBG 'start-script' stderr output:
insmod: ERROR: could not load module /lib/modules/tun.ko: No such file or directory

2019-07-22 18:25:16,104 DEBG 'start-script' stdout output:
[warn] Unable to load tun kernel module, assuming its dynamically loaded

2019-07-22 18:25:16,111 DEBG 'start-script' stdout output:
[info] Attempting to load iptable_mangle module...

2019-07-22 18:25:16,112 DEBG 'start-script' stderr output:
modprobe: FATAL: Module iptable_mangle not found in directory /lib/modules/5.0.0-20-generic

2019-07-22 18:25:16,112 DEBG 'start-script' stdout output:
[warn] Unable to load iptable_mangle module using modprobe, trying insmod...

2019-07-22 18:25:16,113 DEBG 'start-script' stderr output:
insmod: ERROR: could not load module /lib/modules/iptable_mangle.ko: No such file or directory

2019-07-22 18:25:16,114 DEBG 'start-script' stdout output:
[warn] Unable to load iptable_mangle module, you will not be able to connect to the applications Web UI or Privoxy outside of your LAN
[info] unRAID/Ubuntu users: Please attempt to load the module by executing the following on your host: '/sbin/modprobe iptable_mangle'
[info] Synology users: Please attempt to load the module by executing the following on your host: 'insmod /lib/modules/iptable_mangle.ko'

2019-07-22 18:25:16,133 DEBG 'start-script' stdout output:
[info] Docker network defined as    172.17.0.0/16

2019-07-22 18:25:16,136 DEBG 'start-script' stdout output:
[info] Adding 192.168.1.0/24 as route via docker eth0

2019-07-22 18:25:16,137 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2019-07-22 18:25:16,137 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.2 
192.168.1.0/24 via 172.17.0.1 dev eth0 

2019-07-22 18:25:16,138 DEBG 'start-script' stdout output:
--------------------

2019-07-22 18:25:16,170 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2019-07-22 18:25:16,171 DEBG 'start-script' stdout output:
-P INPUT DROP
-P FORWARD DROP
-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 1198 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 8112 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --sport 8112 -j ACCEPT
-A INPUT -s 192.168.1.0/24 -i eth0 -p tcp -m tcp --dport 58846 -j ACCEPT
-A INPUT -s 192.168.1.0/24 -d 172.17.0.0/16 -i eth0 -p tcp -j ACCEPT
-A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT
-A INPUT -i lo -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 1198 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --dport 8112 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 8112 -j ACCEPT
-A OUTPUT -d 192.168.1.0/24 -o eth0 -p tcp -m tcp --sport 58846 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 192.168.1.0/24 -o eth0 -p tcp -j ACCEPT
-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A OUTPUT -o lo -j ACCEPT
-A OUTPUT -o tun0 -j ACCEPT

2019-07-22 18:25:16,171 DEBG 'start-script' stdout output:
--------------------

2019-07-22 18:25:16,172 DEBG 'start-script' stdout output:
[info] Starting OpenVPN...

2019-07-22 18:25:16,177 DEBG 'start-script' stdout output:
Mon Jul 22 18:25:16 2019 WARNING: file 'credentials.conf' is group or others accessible
Mon Jul 22 18:25:16 2019 OpenVPN 2.4.7 [git:makepkg/2b8aec62d5db2c17+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Feb 19 2019
Mon Jul 22 18:25:16 2019 library versions: OpenSSL 1.1.1c  28 May 2019, LZO 2.10

2019-07-22 18:25:16,178 DEBG 'start-script' stdout output:
[info] OpenVPN started
Mon Jul 22 18:25:16 2019 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2019-07-22 18:25:16,180 DEBG 'start-script' stdout output:
Mon Jul 22 18:25:16 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]172.98.67.88:1198
Mon Jul 22 18:25:16 2019 UDP link local: (not bound)
Mon Jul 22 18:25:16 2019 UDP link remote: [AF_INET]172.98.67.88:1198

2019-07-22 18:25:16,372 DEBG 'start-script' stdout output:
Mon Jul 22 18:25:16 2019 [0f6bb741d8cfe08e9d67c43afe693fcb] Peer Connection Initiated with [AF_INET]172.98.67.88:1198

as you can tell I can't find out why no passwords will authenticate

Share this post


Link to post

The password for the webui is "deluge". The auth file is for configuring the user/pass for connecting to the deluge daemon (thin client).

Share this post


Link to post
On 7/21/2019 at 12:12 AM, elenaran said:

I had DelugeVPN working great and then I was screwing around on my server and wiped out all my configs (with no backups - lesson learned). I re-setup the docker with what I thought was identical settings to before, but now I can't seem to connect to peers on my private trackers (multiple different trackers).

 

I'm using v2.0.3 and PIA connecting to CA-Toronto. I can download public torrents just fine, and v2 is white-listed by my trackers so there shouldn't be an issue there. I've unchecked Peer Exchange and DHT, but still no luck. I've even tried with "VPN_ENABLED" set to no - no dice.

 

Any ideas?? This is very frustrating, because I had it working just fine!

What are your speeds? I'm using CA-Toronto too and I'm getting a max of 3Mb/s down. 

Share this post


Link to post
On 1/14/2019 at 6:08 PM, chris_netsmart said:

with the help of binhex. I have been able to get my Deluge to work.  Thanks again for your help.

I am now having issue with connection my Windows Deluge to my Unraid Deluge as I would like to add the IPmagnet torrent to it to check on the VPN, but I am being asked for a username and password, when I am trying to add the host.

 

as anything know the details ?

Capture.JPG

 

it has been some time when I had to post something in relalating to my deulge as I have found it a great docker, but I just discovered the following and I am having issues getting
it to work again.

back in 14 Jan 19, I was trying to set up a client collection with Deluge so that I can add torrents to my docker via my workstation, and after a bit of working out I finile got it working
with a bit of help from @THF13 who posted 

Quote

 

Open /config/auth and add a second line with the following.

<username>:<password>:10


Then use those credentials to connect from the thin client, obviously using the appropriate IP and Port to reach the container.

 

 

which I did and all worked fine,

but at the beginning of the month when I try to remove access my deluge via my client connection I discovered at the connection was showing a red cycle and not a green one

 

I have recheck my settings and I can see that I have the above referance in my auth file.

and when I type in my my details, and I still getting the red cycle,

 

is there something I am missing

Share this post


Link to post
1 hour ago, chris_netsmart said:

is there something I am missing

What version of Deluge are you running? I don’t believe the Windows thin client has been upgraded for compatibility with Deluge v2 yet.

Share this post


Link to post

I am not sure on how to find my current version. But i do know is that i am running the lastest version. But i might be 2.0.3.

 

If the thin clint has not been update. Then is there a differance way to manage deluge from my desktop.

Share this post


Link to post
29 minutes ago, chris_netsmart said:

is there a differance way to manage deluge from my desktop.

Use the webUI.

Share this post


Link to post
24 minutes ago, jonathanm said:

Use the webUI.

Which i have been using.  I will keep an eye out for an up dated version of the thin clinted

Share this post


Link to post
Posted (edited)

[SOLVED]

I just installed this in docker on my Synology NAS but I have a problem with torrents not downloading or being able to send announce. All I get is Error: Connection Timed Out.

 

Looking in my supervisord.log file I don't see any indications on any issues.
Just so I dont spam this thread with a mile long log, you can see my log here: https://pastebin.com/5uEgUbhh 

 

I have forwarded the port from PIA in my router.

 

Do you know what could be the problem?

router forward.PNG

 

 

EDIT / UPDATE: I got the torrents to kinda work. The problem was that I had also setup a VPN connection in DSM. After deleting that and restarting Docker and my DelugeVPN container, I now got the announcement working. But it is not really downloading anything or it is being super slow. It looks like it keep disconnecting to the peers.

 

This is my Deluge network settings. 
deluge.PNG.a6bea2f8568efc86905a5a354a2975d5.PNG

 

EDIT / UPDATE 2: I finally got it to work. My download paths was wrong. I added another mount by adding the line "-v /volume1/docker/deluge/downloads:/downloads" and pointed my download path to "/downloads" and that was the trick.
I didn't realize that the path "/volume1/docker/deluge/downloads" wasn't accessible in the docker container.

Anyways, instead of deleting my stupid post here, I will leave it for other newbies to find, ind case they run into the same trouble :)

Edited by qbone

Share this post


Link to post
Posted (edited)

I am relatively new to unRAID and plug-ins, but Im not too new on Linux. Right now I'm having a dilemma adding the webAPI plug-in to Deluge.

I am running the latest pull from docker, this is my only issue I'm experiencing right now with it.

When I go to add the .egg file, it loads as [object File], but never appears in the plug-ins list to select. I also cannot stop my daemon, as I was figuring I'd just restart the daemon in the deluge web GUI, but it gives me 'An error occured'. I am on the latest unRAID version as well(6.7.2).

Im hoping there is another work around to this, as Im trying to get it to interface with Organizr V2.

Also here is someone on the github page having the same issue, maybe their description makes more sense.

Github link

Edited by feyded1020

Share this post


Link to post
Posted (edited)
1 hour ago, feyded1020 said:

I am relatively new to unRAID and plug-ins, but Im not too new on Linux. Right now I'm having a dilemma adding the webAPI plug-in to Deluge.

I am running the latest pull from docker, this is my only issue I'm experiencing right now with it.

When I go to add the .egg file, it loads as [object File], but never appears in the plug-ins list to select. I also cannot stop my daemon, as I was figuring I'd just restart the daemon in the deluge web GUI, but it gives me 'An error occured'. I am on the latest unRAID version as well(6.7.2).

Im hoping there is another work around to this, as Im trying to get it to interface with Organizr V2.

Also here is someone on the github page having the same issue, maybe their description makes more sense.

Github link

Just from looking at that GitHub link, it appears that you are trying to use a python 2 plugin with the latest version of Deluge which uses python 3. This plugin (along with more than a few others) must be updated to python 3 before you can use it. You can use tagging in the docker configuration to roll back to a previous (python 2) version of Deluge if you want.

 

 

SafariScreenSnapz165.jpg

 

The full tag doesn't show in the screenshot, but it's binhex/arch-delugevpn:1.3.15_18_ge050905b2-1-04

 

Edit: Some people have lost torrents when rolling back. Be sure you have a backup of the docker to restore from.

Edited by wgstarks

Share this post


Link to post
Posted (edited)

Hello,

 

  I've been trying and trying over and over to get this working with my qnap with docker.  Below is what I paste when i SSH (I took out the UN/PW), and I always get the same error.

 

standard_init_linux.go:185: exec user process caused "exec format error"                                                                                                                                                                    

docker run -d \

    --cap-add=NET_ADMIN \

    -p 8112:8112 \

    -p 8118:8118 \

    -p 58846:58846 \

    -p 58946:58946 \

   --name=delugevpn \

   -v /share/cachedev1_data/downloads/deluge/data:/data\

   -v /share/cachedev1_data/downloads:/download \

   -v /share/cachedev1_data/downloads/deluge/config:/config\

   -v /etc/localtime:/etc/localtime:ro \

    -e VPN_ENABLED=yes \

   -e VPN_USER=****** \

   -e VPN_PASS=****** \

    -e VPN_PROV=pia \

    -e STRICT_PORT_FORWARD=yes \

    -e ENABLE_PRIVOXY=yes \

    -e LAN_NETWORK=192.168.1.0/24 \

    -e NAME_SERVERS=209.222.18.222,84.200.69.80,37.235.1.174,1.1.1.1,209.222.18.218,37.235.1.177,84.200.70.40,1.0.0.1 \

    -e DELUGE_DAEMON_LOG_LEVEL=info \

    -e DELUGE_WEB_LOG_LEVEL=info \

    -e DEBUG=false \

    -e UMASK=0000 \

    -e PUID=1000 \

    -e PGID=0 \

    binhex/arch-delugevpn

 

What am i doing wrong?

 

Edited by failurbydesign

Share this post


Link to post

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.