Thanks for the support, it's working fine now! 

I got an error in " FIX COMMON PROBLEMS"

 

The error was :

Docker Application binhex-delugevpn, Container Port 58946 not found or changed on installed application

 

i have not changed anything when this error occurred.

 

I tryed to change the port inside deluge, and in docker to 58946, before it was 58846.

 

But now i can not get into deluge anymore..

 

What did i do wrong ?

 

Thanks for any reply

1 hour ago, Unlime said:

tryed to change the port inside deluge,

 

This is what has tripped you up, NEVER change the port on the container side, its designed to work with a specific port, if you want to run it on a different port then you only change the host side port.

 

The "error" you were seeing isnt an error per say, it simply telling you your missing an ADDITIONAL port specification for your currently defined template, this is due to the fact that i added in an incoming port that will be used when the user has specified VPN_ENABLED is false, if your using the VPN functionality then this port isnt used at all.

 

So to fix your stuff, change the port back to 58846 on the container side, manually edit the port setting for deluge in the config file located in /config/core.conf and then run and you should be back as you were, if you want to get rid of the "error" then add an additional port with container side being 58946 (host side whatever you want) and re-run the fix common problems plugin to confirm.

I only changed the port on the container side becuase i couldt get in to deluge after i had changed inside ..

 

I dont care about what port i run, i only changed it because "fix common problems" told me.

 

I have dont what you told and its working now, so than you very much.

 

I use vpn, so then i dont need to do anyhing about it ?

1 minute ago, Unlime said:

i only changed it because "fix common problems" told me.

 

if it aint broke dont fix it, just cos a tool tells you there is a problem doesnt necessarily mean its a problem for you, and in this case its completely harmless.

 

2 minutes ago, Unlime said:

use vpn, so then i dont need to do anyhing about it ?

 

correct.

Hi,

 

When i download a torrent it is going onto the cache drive but not moving to my share folder, i have tried MOVER but still nothing.

 

Can anyone tell me what i am doing wrong please.

 

 

Greygoose,

 

I think the setting you need is inside the delugeVPN preferences.  This is how I have mine setup:

 

 

Edited April 21, 20179 yr by scott47
Realized I needed to add docker settings

Hi Scott47

 

Thanks for the help, it is appreciated.

 

I have it setup as follows.

 

 

What is /data mapped to in your delugeVPN docker?

 

I'm thinking that if you map it to /mnt/cache/Downloads, the file could be locked *on the cache drive* by deluge.  If it's moved, you'd stop seeding.

 

If you map /data to /mnt/user/Downloads in the docker, it should be movable but then sometimes containers don't like to be mapped on user shares so that might not work for completely different reasons

Hi Gog,

 

I have it mapped like this,.

17 hours ago, binhex said:

 

if it aint broke dont fix it, just cos a tool tells you there is a problem doesnt necessarily mean its a problem for you, and in this case its completely harmless.

 

 

correct.

Thank you for the reply

 

 

Hi Gog,

 

I have it mapped like this,.

 

Have you tried stopping the deluge docker then run the mover manually?

 

Sent from my SGH-I337M using Tapatalk

 

 

 

I've just switch from deluge to delugevpn.  I've installed the docker and all seams to work well when accessing on using the webui (on local unraid box).  I'm having an issue when trying to connect from a deluge client on another machine in my network.  I'm using a comcast router that DHCP server issues address as 10.0.0.X.  My unraid box is 10.0.0.111 .  I took a guess that my LAN_NETWORK value was wrong and changed that...but no go. Screen shot of settings attached.  Any suggestions ?

 

 

2 hours ago, krh1009 said:

My unraid box is 10.0.0.111 .  I took a guess that my LAN_NETWORK value was wrong and changed that...but no go. Screen shot of settings attached.  Any suggestions ?

 

Your LAN network is defined incorrectly. It should be 10.0.0.0/24

 

 

BINGO!   Thank you!

One more question... I had very slow download speeds with pia, so I'm trying to switch to express VPN as a provider.  I'm running int a problem, attached are the head and tail of  my supervisord.log.

 

18 hours ago, Gog said:

 

Have you tried stopping the deluge docker then run the mover manually?

 

Sent from my SGH-I337M using Tapatalk

 

 

 

 

I did that and it sorted the issue, i was also missing a /   from the config which i changed.  now eveything is good

 

Thanks for the help

One more question... I had very slow download speeds with pia, so I'm trying to switch to express VPN as a provider.  I'm running int a problem, attached are the head and tail of  my supervisord.log.
 

I need the full log to diagnose any issues, but at a guess I would say your attempting to connect to the wrong port or endpoint.

Sent from my SM-G900F using Tapatalk

On 18/04/2017 at 1:47 AM, Jazzepi said:

I'm trying to run this Docker inside an Ubuntu 16.10 VirtualBox VM on my Windows machine. After following the instructions I don't see anything in the debug output about the VPN or or PRIVOXY even though I have them both enabled from the environment varaibles. I also don't see a "config/openvpn" folder in the configuration directory mounted in /data/deluge/config even after running the container. Any assist would be greatly appreciated.

 

I can reach the deluge UI so that seems to be working properly, but I haven't tried to add any torrents to it.

 

 

Here's my docker log for the startup

media@media-VirtualBox:~$ docker logs arch-deluge 
2017-04-17 20:34:55.458777 [info] Starting Supervisor...
2017-04-17 20:34:57,803 CRIT Set uid to user 0
2017-04-17 20:34:57,803 INFO Included extra file "/etc/supervisor/conf.d/deluge.conf" during parsing
2017-04-17 20:34:57,815 INFO supervisord started with pid 5
2017-04-17 20:34:58,819 INFO spawned: 'deluge-script' with pid 44
2017-04-17 20:34:58,848 INFO spawned: 'deluge-web-script' with pid 45
2017-04-17 20:34:58,871 DEBG 'deluge-script' stdout output:
[info] Deluge config file already exists, skipping copy

2017-04-17 20:34:58,881 INFO success: deluge-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2017-04-17 20:34:58,882 INFO success: deluge-web-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2017-04-17 20:34:58,885 DEBG 'deluge-script' stdout output:
[info] Starting Deluge daemon...

2017-04-17 20:35:02,799 DEBG 'deluge-web-script' stdout output:
[info] Starting Deluge webui...

 

Here's the environment variables that I set.

media@media-VirtualBox:~$ docker exec arch-deluge env
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
HOSTNAME=d3e21fb63431
VPN_ENABLED=yes
VPN_USER=*****
VPN_PASS=*****
VPN_REMOTE=america.vpn.airdns.org
VPN_PORT=443
VPN_PROTOCOL=udp
VPN_DEVICE_TYPE=tun
VPN_PROV=airvpn
ENABLE_PRIVOXY=yes
LAN_NETWORK=192.168.1.0/24
NAME_SERVERS=8.8.8.8,8.8.4.4
DEBUG=true
UMASK=000
PUID=1000
PGID=1000
HOME=/home/nobody
TERM=xterm
LANG=en_GB.UTF-8
 

Here's the systemd unit definition that runs the docker as a service

media@media-VirtualBox:~$ docker exec arch-deluge env

[Unit]
Description=arch-deluge in Docker container
After=docker.service
Requires=docker.service

[Service]
TimeoutStartSec=0
Restart=always
ExecStartPre=-/usr/bin/docker stop arch-deluge
ExecStartPre=-/usr/bin/docker rm arch-deluge
ExecStartPre=-/usr/bin/docker pull binhex/arch-deluge
ExecStart=/bin/bash -c "/usr/bin/docker run --rm -t \
    -p 8112:8112 \
    -p 8118:8118 \
    -p 58846:58846 \
    -p 58946:58946 \
    -e VPN_ENABLED=yes \
    -e VPN_USER=**** \
    -e VPN_PASS=**** \
    -e VPN_REMOTE=america.vpn.airdns.org \
    -e VPN_PORT=443 \
    -e VPN_PROTOCOL=udp \
    -e VPN_DEVICE_TYPE=tun \
    -e VPN_PROV=airvpn \
    -e ENABLE_PRIVOXY=yes \
    -e LAN_NETWORK=192.168.1.0/24 \
    -e NAME_SERVERS=8.8.8.8,8.8.4.4 \
    -e DEBUG=true \
    -e UMASK=000 \
    -e PUID=$(/usr/bin/id -u media) \
    -e PGID=$(/usr/bin/id -g media) \
    -v /data/deluge/data:/data \
    -v /data/deluge/config:/config \
    -v /etc/localtime:/etc/localtime:ro \
    --cap-add=NET_ADMIN \
    --name arch-deluge binhex/arch-deluge "
ExecStartPost=-/bin/bash -c "sleep 10; chown -R media:media /data"
ExecStop=-/usr/bin/docker stop -t 3 arch-deluge
ExecStop=-/usr/bin/docker rm arch-deluge
Restart=always
RestartSec=10s

[Install]
WantedBy=multi-user.target

 

Finally, here's the supervisor d.log output.

 

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

2017-04-17 20:34:44.461950 [info] System information Linux d3e21fb63431 4.8.0-46-generic #49-Ubuntu SMP Fri Mar 31 13:57:14 UTC 2017 x86_64 GNU/Linux
2017-04-17 20:34:44.768869 [info] PUID defined as '1000'
2017-04-17 20:34:54.406403 [info] PGID defined as '1000'
2017-04-17 20:34:54.675630 [info] UMASK defined as '000'
2017-04-17 20:34:54.945410 [info] Permissions already set for volume mappings
2017-04-17 20:34:55.157419 [info] Setting permissions on files/folders inside container...
2017-04-17 20:34:57,803 CRIT Set uid to user 0
2017-04-17 20:34:57,803 INFO Included extra file "/etc/supervisor/conf.d/deluge.conf" during parsing
2017-04-17 20:34:57,815 INFO supervisord started with pid 5
2017-04-17 20:34:58,819 INFO spawned: 'deluge-script' with pid 44
2017-04-17 20:34:58,848 INFO spawned: 'deluge-web-script' with pid 45
2017-04-17 20:34:58,871 DEBG 'deluge-script' stdout output:
[info] Deluge config file already exists, skipping copy

2017-04-17 20:34:58,881 INFO success: deluge-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2017-04-17 20:34:58,882 INFO success: deluge-web-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2017-04-17 20:34:58,885 DEBG 'deluge-script' stdout output:
[info] Starting Deluge daemon...

2017-04-17 20:35:02,799 DEBG 'deluge-web-script' stdout output:
[info] Starting Deluge webui...

 

Please set the DEBUG env var to true, restart the container and then post the ENTIRE /config/supervisord.log file here and i will take a look, im afraid partial logs can hide the issue, obviously make sure to remove your username and password from the log.

 

4 hours ago, binhex said:

 

I need the full log to diagnose any issues, but at a guess I would say your attempting to connect to the wrong port or endpoint.

Sent from my SM-G900F using Tapatalk
 

 

 

Here is my log file (user/pass deleted)

my.log

 
Here is my log file (user/pass deleted)
my.log

Well the tunnel is up, you don't have a incoming port but that's a different issue, so you should be able to connect to the deluge webui is that not the case?

Sent from my SM-G900F using Tapatalk

Hey there. Love this docker container. 

 

However I'm having an issue which causes Deluge to not start. The startup process is giving me some errors. Here are my logs: https://pastebin.com/NK2kJSUV

I posted this issue on Github at first. I didn't see the support forum link at the bottom of the readme until just now.

Edited April 23, 20179 yr by Rourke

9 hours ago, binhex said:

Well the tunnel is up, you don't have a incoming port but that's a different issue, so you should be able to connect to the deluge webui is that not the case?

Sent from my SM-G900F using Tapatalk
 

It's working.  Thanks

Hello,

 

Im trying to run "transmission-vpn" but im not able to connect and no clue where could be the problem

Only what i see in the log, that even ive defined "tun5" in Docker config, it still set "tun0" (in -A INPUT/OUTPUT)

 

Docker si in running state - but loading login page, just error

 

Thanks

 

supervisord.log

Wrong support thread, this is deluge, not transmission.  That being sent, the VPN part should be the same so...

 

It looks like there is something wrong with your VPN config, openVPN is not initialising

 

I don't know why tou would define 'tun5' for device type.  If memory serves, the script hardcodes it to device_type+0 so I would expect tun50 but I can't check from work.

 

Can you stop the docker, set debug to true, start the docker, wait a few minutes and post supervisor.log?