[Support] binhex - DelugeVPN


Recommended Posts

2 minutes ago, wgstarks said:

I’ve never tried, but pretty sure you just need to change the mapping in the docker template.

Hey, thanks for the reply. I'm trying to run multiple instances of DelugeVPN and I need to change the internal port used within the container for that if it's possible with configuration. The reason I would like more than one instance is because deluge starts to become fragile and slow past 1500 to 2500 torrents.

Link to comment

Note: this is a copy of the GitHib issue #110 ("docker-compose up deluge" works, "docker-compose up" does not) as i am not sure where the best place to post such questions/issues is. Apologies if this is the wrong place.

 

I created a docker-compose service for arch-delugevpn:

 deluge:
    image: binhex/arch-delugevpn:latest
    container_name: deluge
    restart: always
    cap_add:
      - NET_ADMIN
    environment:
      - PUID=999
      - PGID=999
      - VPN_ENABLED=yes
      - VPN_USER=<login>
      - VPN_PASS=<password>
      - VPN_PROV=pia
      - STRICT_PORT_FORWARD=yes
      - ENABLE_PRIVOXY=yes
      - LAN_NETWORK=192.168.10.0/24
      - NAME_SERVERS=1.1.1.1,8.8.4.4
      - UMASK=000
      - DEBUG=false
      - DELUGE_DAEMON_LOG_LEVEL=info
      - DELUGE_WEB_LOG_LEVEL=debug
    volumes:
      - $PWD/deluge/config:/config
      - /mnt/2TB1/deluge:/data
      - /etc/localtime:/etc/localtime:ro
    labels:
      caddy.address: http://deluge.my.domain
      caddy.targetport: "8112"

 

When starting it individually via `docker-compose up deluge` I get a correct startup and a fully working container:

root@srv /e/docker# docker-compose up deluge
Recreating deluge ... done
Attaching to deluge
deluge           | Created by...
deluge           | ___.   .__       .__
deluge           | \_ |__ |__| ____ |  |__   ____ ___  ___
deluge           |  | __ \|  |/    \|  |  \_/ __ \\  \/  /
deluge           |  | \_\ \  |   |  \   Y  \  ___/ >    <
deluge           |  |___  /__|___|  /___|  /\___  >__/\_ \
deluge           |      \/        \/     \/     \/      \/
deluge           |    https://hub.docker.com/u/binhex/
deluge           |
deluge           | 2019-05-06 13:10:25.153235 [info] System information Linux ee56835d263f 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 GNU/Linux
deluge           | 2019-05-06 13:10:25.179594 [info] PUID defined as '999'
deluge           | 2019-05-06 13:10:25.256661 [info] PGID defined as '999'
deluge           | 2019-05-06 13:10:25.328264 [info] UMASK defined as '000'
deluge           | 2019-05-06 13:10:25.361891 [info] Permissions already set for volume mappings
deluge           | 2019-05-06 13:10:25.391162 [info] DELUGE_DAEMON_LOG_LEVEL defined as 'info'
deluge           | 2019-05-06 13:10:25.416152 [info] DELUGE_WEB_LOG_LEVEL defined as 'debug'
deluge           | 2019-05-06 13:10:25.441148 [info] VPN_ENABLED defined as 'yes'
deluge           | 2019-05-06 13:10:25.471236 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/Switzerland.ovpn
(...)


 

When starting it as part of the global `docker-compose up`, it fails to start:

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

2019-05-06 13:08:47.140703 [info] System information Linux 8e5db03d43ac 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 GNU/Linux
2019-05-06 13:08:47.175570 [info] PUID defined as '999'
2019-05-06 13:08:47.204582 [info] PGID defined as '999'
2019-05-06 13:08:47.258333 [info] UMASK defined as '000'
2019-05-06 13:08:47.294058 [info] Permissions already set for volume mappings
2019-05-06 13:08:47.324459 [info] DELUGE_DAEMON_LOG_LEVEL defined as 'info'
2019-05-06 13:08:47.349228 [info] DELUGE_WEB_LOG_LEVEL defined as 'debug'
2019-05-06 13:08:47.377825 [info] VPN_ENABLED defined as 'yes'
2019-05-06 13:08:47.411000 [crit] No OpenVPN config file located in /config/openvpn/ (ovpn extension), please download from your VPN provider and then restart this container, exiting...

 

What could be the reason for this difference in startup (all the other docker containers started globally or individually are fine - it is just delugevpn which has this behaviour so I believe the problem is with the way I start this particular container)

Link to comment
11 hours ago, WoJ said:

$PWD/deluge/config:/config

this is your issue, dont use $PWD, you must use absolute paths, this is why you are then getting this:-

11 hours ago, WoJ said:

[crit] No OpenVPN config file located in /config/openvpn/ (ovpn extension), please download from your VPN provider and then restart this container, exiting...

because $PWD is not resolving.

Link to comment
17 hours ago, advancedSLICEDbanana said:

I'm trying to run multiple instances of DelugeVPN and I need to change the internal port

dont do this, you should never change the container port, you change the host port, if you change the container port it will most likely break things.

Link to comment
5 hours ago, binhex said:

this is your issue, dont use $PWD, you must use absolute paths, this is why you are then getting this:

Thank you, it was indeed the problem.

I do not understand yet why it affected only that particular container (other also had a similar volume declaration) and why it was appearing in one mode and not the other ("up deluge" vs. "up") but it is good advice anyway and I changed it everywhere to a path without $PWD (relative not absolute, though).

Link to comment
40 minutes ago, WoJ said:

I do not understand yet why it affected only that particular container

it will of affected all your containers, the only reason you spotted it this time is that this particular container requires certain files (as in /config/openvpn) to be in place in order to start correctly, all your other containers most probably do not require certain files to exist and thus it just writes everything in '/deluge/config' (as i would guess $PWD = '').

Link to comment
2 minutes ago, binhex said:

it will of affected all your containers, the only reason you spotted it this time is that this particular container requires certain files (as in /config/openvpn) to be in place in order to start correctly, all your other containers most probably do not require certain files to exist and thus it just writes everything in '/deluge/config' (as i would guess $PWD = '').

Well, other containers use the local directory mapped to the container directory to handle data, config files etc. 

So if I had $PWD/somecontainer:/etc/something and $PWD was empty, it would map a nonexistent /somecontainer folder to /etc/something within the container. If the container expected to find or write something there it would have failed.

I edited the configuration of these other containers via their mapped volume (which  used $PWD) and it was taken into account correctly.

 

The other point is that "docker-compose up deluge" worked fine, while "docker-compose up" did not (for deluge).

 

I agree with you that it is definitely better to be explicit with the paths and I modified them everywhere (even when it was working fine with $PWD, and it still works fine), I am just trying to completely understand the behaviour.

Link to comment
3 minutes ago, WoJ said:

So if I had $PWD/somecontainer:/etc/something and $PWD was empty, it would map a nonexistent /somecontainer folder to /etc/something within the container.

this is true, as per your findings, are you using 'docker-compose up' for these other containers?, or 'docker-compose up <name of service>'? as you said that one succeeds and one doesn't.

 

 

Link to comment
7 hours ago, binhex said:

dont do this, you should never change the container port, you change the host port, if you change the container port it will most likely break things.

Ok thanks for the advise. If I’m not mistaken, running multiple Deluge containers with the same internal ports will not work using bridge networking. Do you know if any ways to deploy multiple instances of your Deluge container in Docker?

Link to comment
4 minutes ago, advancedSLICEDbanana said:

If I’m not mistaken, running multiple Deluge containers with the same internal ports will not work using bridge networking.

you are mistaken, this is not correct, its the HOST ports that cannot be the same, the container ports can (and in most cases should be) the same if you are deploying multiple containers for the same image.

  • Like 1
Link to comment
1 hour ago, binhex said:

this is true, as per your findings, are you using 'docker-compose up' for these other containers?, or 'docker-compose up <name of service>'? as you said that one succeeds and one doesn't.

 

 

When starting the containers individually (docker-compose up containername), each succeeds (including deluge) 

 

When starting them all together via docker-compose up, they all succeed except for deluge (with the error about missing ovpn file) 

 

Now that I changed $PWD to . (current dir), they all succeed no matter how they are started. 

 

This is really strange but at least now everything works :)

Link to comment

Hi, Privoxy is not starting. I tried repulling the image but I'm still getting the same issue. This is all I'm seeing in the log

2019-05-07 18:22:00,596 DEBG 'watchdog-script' stdout output:
[debug] Waiting for Privoxy process to start...

2019-05-07 18:22:01,600 DEBG 'watchdog-script' stdout output:
[warn] Wait for Privoxy process to start aborted, too many retries
[warn] Showing output from command before exit...

2019-05-07 18:22:03,603 DEBG fd 16 closed, stopped monitoring <POutputDispatcher at 22775243352888 for <Subprocess at 22775243981656 with name watchdog-script in state RUNNING> (stdout)>
2019-05-07 18:22:03,603 DEBG fd 20 closed, stopped monitoring <POutputDispatcher at 22775243353056 for <Subprocess at 22775243981656 with name watchdog-script in state RUNNING> (stderr)>
2019-05-07 18:22:03,604 INFO exited: watchdog-script (exit status 1; not expected)
2019-05-07 18:22:03,604 DEBG received SIGCHLD indicating a child quit

I was working fine until the update you all mentioned last week (Thursday?) but it's not working anymore. 

 

Any ideas?

 

UPDATE: I was going to delete this before moderators approved, but I found a solution and thought I'd go ahead a post it for others. I stopped container, deleted the "privoxy" folder from the container folder, and restarted as suggested earlier. Didn't work for others leading to an updated image from binhex but it seems to have fixed my issue. It seems to be working now.

Edited by nowhere99
Found solution
  • Thanks 1
Link to comment

Anyone else having trouble with the docker after updating to 6.7.0? I updated Unraid, but the Deluge docker keeps saying "update ready", but when I hit "apply update", it checks a few things but doesn't pull any new data and I can't get to the web GUI. Everything was working perfectly prior to updating from 6.6.7 to 6.7.0.

 

Any tips? I've restarted twice and tried applying update each time with no success.

 

Edit: Appears something broke my network connection, although I didn't change anything when updating Unraid to 6.7.0?? I'm getting the error: "Interface Ethernet Port 1 is down. Check cable!"

Edited by BBLV
Link to comment
10 hours ago, BBLV said:

Anyone else having trouble with the docker after updating to 6.7.0? I updated Unraid, but the Deluge docker keeps saying "update ready", but when I hit "apply update", it checks a few things but doesn't pull any new data and I can't get to the web GUI. Everything was working perfectly prior to updating from 6.6.7 to 6.7.0.

 

I'm awaiting further reports before I risk an update!

Link to comment

Hi

 

I need help with the following error in the docker log.

I have VPN enabled =yes and added my ipvanish credentials and copied the opvn file.

The WebUI is not accessible even though the docker starts. Below is the only error I have.... tried manually creating the log file but didn't help.

 

Options error: --status fails with '/tmp/openvpn/openvpn-status.log': No such file or directory (errno=2)

Link to comment

** I solved my issue, folder permissions resolved my issues. Wouldn't download to folder, once i corrected that its back to regular speed. **


Hi

I recently started messing around with unRaid. I installed this container and everything appears to be working, it connects to Toronto PIA with OpenVPN, Deluge starts up and will accept files. The file starts downloading and then the connection just slows down until it times out on the tracker.

For testing purposes I setup the non-vpn Deluge and it works with no issues. Only when I use delugevpn does it not work. It also seems like whenever i restart the container it connects, the speed hits 500kb/sec and then teeters down to 0.0 in about 30 seconds. I don't see anything in the logs that would help me solve this issue. The logs do show that the script is updating the port.
Hoping someone can point me in the correct direction.

All of the troubleshooting i have read is either outdated or did not fix my issues.

I have install ITConfig add-on in Deluge and changed the utp and udp settings, made no difference
I downloaded the torguard magent link and it reports the vpn is working and can see the files, but does the same thing where it times out.
PIA app works flawlessly on all the other Windows machines on the network

 



 

Edited by GameraGarage
im dumb and folders are hard
Link to comment

I cannot for the life of me figure out what is going on. I am using Rancher 1.6. I had this installed and running smoothly on a previous machine. I got a new machine, did the install and cannot access the UI at all. Even tried blowing out the config folder and starting from scratch. The logs show no issue, shows. Here is the yml:

delugevpn:

cap_add:

- NET_ADMIN

image: binhex/arch-delugevpn

environment:

VPN_ENABLED: 'yes'

VPN_PROV: airvpn

ENABLE_PRIVOXY: 'yes'

LAN_NETWORK: 192.168.1.1/24

NAME_SERVERS: 209.222.18.222,37.235.1.174,8.8.8.8,209.222.18.218,37.235.1.177,8.8.4.4

DELUGE_DAEMON_LOG_LEVEL: info

DELUGE_WEB_LOG_LEVEL: info

DEBUG: 'false'

UMASK: '000'

PGID: '1100'

PUID: '1100'

stdin_open: true volumes:

- /mnt/zpool2/apps/deluge/data:/data

- /mnt/zpool2/apps/deluge/config:/config

tty: true

ports:

- 8112:8112/tcp

- 8118:8118/tcp

- 58846:58846/tcp

- 58946:58946/tcp

labels: io.rancher.container.pull_image: always

 

HERE are the logs:

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

2019-05-16 14:29:43.473098 [info] System information Linux 0ced337a1d1b 4.14.85-rancher #1 SMP Sat Dec 1 12:40:08 UTC 2018 x86_64 GNU/Linux
2019-05-16 14:29:43.516948 [info] PUID defined as '1100'
2019-05-16 14:29:43.614217 [info] PGID defined as '1100'
2019-05-16 14:29:43.692712 [info] UMASK defined as '000'
2019-05-16 14:29:43.725289 [info] Permissions already set for volume mappings
2019-05-16 14:29:43.771946 [info] DELUGE_DAEMON_LOG_LEVEL defined as 'info'
2019-05-16 14:29:43.813738 [info] DELUGE_WEB_LOG_LEVEL defined as 'info'
2019-05-16 14:29:43.855183 [info] VPN_ENABLED defined as 'yes'
2019-05-16 14:29:43.909683 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/AirVPN_Spain_UDP-443.ovpn
dos2unix: converting file /config/openvpn/AirVPN_Spain_UDP-443.ovpn to Unix format...
2019-05-16 14:29:43.973419 [info] VPN remote line defined as 'remote es.vpn.airdns.org 443'
2019-05-16 14:29:44.010198 [info] VPN_REMOTE defined as 'es.vpn.airdns.org'
2019-05-16 14:29:44.048144 [info] VPN_PORT defined as '443'
2019-05-16 14:29:44.096935 [info] VPN_PROTOCOL defined as 'udp'
2019-05-16 14:29:44.136620 [info] VPN_DEVICE_TYPE defined as 'tun0'
2019-05-16 14:29:44.172465 [info] VPN_PROV defined as 'airvpn'
2019-05-16 14:29:44.202096 [info] LAN_NETWORK defined as '192.168.1.1/24'
2019-05-16 14:29:44.246305 [info] NAME_SERVERS defined as '8.8.8.8,8.8.4.4'
2019-05-16 14:29:44.286562 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2019-05-16 14:29:44.333397 [info] ENABLE_PRIVOXY defined as 'yes'
2019-05-16 14:29:44.894983 [info] Starting Supervisor...
2019-05-16 14:29:45,100 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing
2019-05-16 14:29:45,100 INFO Set uid to user 0 succeeded
2019-05-16 14:29:45,105 INFO supervisord started with pid 13
2019-05-16 14:29:46,109 INFO spawned: 'privoxy-script' with pid 143
2019-05-16 14:29:46,111 INFO spawned: 'start-script' with pid 144
2019-05-16 14:29:46,114 INFO spawned: 'watchdog-script' with pid 145
2019-05-16 14:29:46,115 INFO reaped unknown pid 14
2019-05-16 14:29:46,127 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2019-05-16 14:29:46,127 INFO success: privoxy-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2019-05-16 14:29:46,127 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2019-05-16 14:29:46,128 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2019-05-16 14:29:46,131 DEBG 'watchdog-script' stderr output:
dos2unix: converting file /config/core.conf to Unix format...

2019-05-16 14:29:46,196 DEBG 'start-script' stdout output:
[info] Default route for container is 10.42.0.1

2019-05-16 14:29:46,204 DEBG 'start-script' stdout output:
[info] Adding 8.8.8.8 to /etc/resolv.conf

2019-05-16 14:29:46,210 DEBG 'start-script' stdout output:
[info] Adding 8.8.4.4 to /etc/resolv.conf

2019-05-16 14:29:46,368 DEBG 'start-script' stdout output:
[info] Attempting to load iptable_mangle module...

2019-05-16 14:29:46,370 DEBG 'start-script' stderr output:
modprobe: FATAL: Module iptable_mangle not found in directory /lib/modules/4.14.85-rancher

2019-05-16 14:29:46,371 DEBG 'start-script' stdout output:
[warn] Unable to load iptable_mangle module using modprobe, trying insmod...

2019-05-16 14:29:46,375 DEBG 'start-script' stderr output:
insmod: ERROR: could not load module /lib/modules/iptable_mangle.ko: No such file or directory

2019-05-16 14:29:46,376 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-05-16 14:29:46,414 DEBG 'start-script' stdout output:
[info] Docker network defined as    10.42.0.0/16

2019-05-16 14:29:46,423 DEBG 'start-script' stdout output:
[info] Adding 192.168.1.1/24 as route via docker eth0

2019-05-16 14:29:46,425 DEBG 'start-script' stderr output:
Error: Invalid prefix for given prefix length.

2019-05-16 14:29:46,425 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2019-05-16 14:29:46,426 DEBG 'start-script' stdout output:
default via 10.42.0.1 dev eth0 
10.42.0.0/16 dev eth0 proto kernel scope link src 10.42.60.5 

2019-05-16 14:29:46,427 DEBG 'start-script' stdout output:
--------------------

2019-05-16 14:29:46,606 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2019-05-16 14:29:46,608 DEBG 'start-script' stdout output:
-P INPUT DROP
-P FORWARD ACCEPT
-P OUTPUT DROP
-A INPUT -i tun0 -j ACCEPT
-A INPUT -s 10.42.0.0/16 -d 10.42.0.0/16 -j ACCEPT
-A INPUT -i eth0 -p udp -m udp --sport 443 -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 10.42.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 -o tun0 -j ACCEPT
-A OUTPUT -s 10.42.0.0/16 -d 10.42.0.0/16 -j ACCEPT
-A OUTPUT -o eth0 -p udp -m udp --dport 443 -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 10.42.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

2019-05-16 14:29:46,609 DEBG 'start-script' stdout output:
--------------------

2019-05-16 14:29:46,610 DEBG 'start-script' stdout output:
[info] Starting OpenVPN...

2019-05-16 14:29:46,626 DEBG 'start-script' stdout output:
Thu May 16 14:29:46 2019 WARNING: file 'user.key' is group or others accessible
Thu May 16 14:29:46 2019 WARNING: file 'ta.key' is group or others accessible
Thu May 16 14:29:46 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
Thu May 16 14:29:46 2019 library versions: OpenSSL 1.1.1b  26 Feb 2019, LZO 2.10

2019-05-16 14:29:46,627 DEBG 'start-script' stdout output:
[info] OpenVPN started

2019-05-16 14:29:46,627 DEBG 'start-script' stdout output:
Thu May 16 14:29:46 2019 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2019-05-16 14:29:46,627 DEBG 'start-script' stdout output:
Thu May 16 14:29:46 2019 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Thu May 16 14:29:46 2019 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication

2019-05-16 14:29:46,628 DEBG 'start-script' stdout output:
Thu May 16 14:29:46 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]185.183.106.2:443
Thu May 16 14:29:46 2019 Socket Buffers: R=[212992->212992] S=[212992->212992]
Thu May 16 14:29:46 2019 UDP link local: (not bound)
Thu May 16 14:29:46 2019 UDP link remote: [AF_INET]185.183.106.2:443

2019-05-16 14:29:46,803 DEBG 'start-script' stdout output:
Thu May 16 14:29:46 2019 TLS: Initial packet from [AF_INET]185.183.106.2:443, sid=eec4098b 08ffa336

2019-05-16 14:29:47,012 DEBG 'start-script' stdout output:
Thu May 16 14:29:47 2019 VERIFY OK: depth=1, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=airvpn.org CA, [email protected]

2019-05-16 14:29:47,012 DEBG 'start-script' stdout output:
Thu May 16 14:29:47 2019 VERIFY KU OK
Thu May 16 14:29:47 2019 Validating certificate extended key usage
Thu May 16 14:29:47 2019 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
Thu May 16 14:29:47 2019 VERIFY EKU OK
Thu May 16 14:29:47 2019 VERIFY OK: depth=0, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=Eridanus, [email protected]

2019-05-16 14:29:47,483 DEBG 'start-script' stdout output:
Thu May 16 14:29:47 2019 Control Channel: TLSv1.2, cipher TLSv1.2 DHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
Thu May 16 14:29:47 2019 [Eridanus] Peer Connection Initiated with [AF_INET]185.183.106.2:443

2019-05-16 14:29:48,646 DEBG 'start-script' stdout output:
Thu May 16 14:29:48 2019 SENT CONTROL [Eridanus]: 'PUSH_REQUEST' (status=1)

2019-05-16 14:29:48,821 DEBG 'start-script' stdout output:
Thu May 16 14:29:48 2019 PUSH: Received control message: 'PUSH_REPLY,comp-lzo no,redirect-gateway  def1 bypass-dhcp,dhcp-option DNS 10.16.140.1,route-gateway 10.16.140.1,topology subnet,ping 10,ping-restart 60,ifconfig 10.16.140.169 255.255.255.0,peer-id 1,cipher AES-256-GCM'

2019-05-16 14:29:48,822 DEBG 'start-script' stdout output:
Thu May 16 14:29:48 2019 OPTIONS IMPORT: timers and/or timeouts modified
Thu May 16 14:29:48 2019 OPTIONS IMPORT: compression parms modified
Thu May 16 14:29:48 2019 OPTIONS IMPORT: --ifconfig/up options modified
Thu May 16 14:29:48 2019 OPTIONS IMPORT: route options modified
Thu May 16 14:29:48 2019 OPTIONS IMPORT: route-related options modified
Thu May 16 14:29:48 2019 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Thu May 16 14:29:48 2019 OPTIONS IMPORT: peer-id set
Thu May 16 14:29:48 2019 OPTIONS IMPORT: adjusting link_mtu to 1625
Thu May 16 14:29:48 2019 OPTIONS IMPORT: data channel crypto options modified
Thu May 16 14:29:48 2019 Data Channel: using negotiated cipher 'AES-256-GCM'
Thu May 16 14:29:48 2019 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Thu May 16 14:29:48 2019 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Thu May 16 14:29:48 2019 ROUTE_GATEWAY 10.42.0.1/255.255.0.0 IFACE=eth0 HWADDR=02:c6:ef:ad:48:e3

2019-05-16 14:29:48,822 DEBG 'start-script' stdout output:
Thu May 16 14:29:48 2019 TUN/TAP device tun0 opened

2019-05-16 14:29:48,823 DEBG 'start-script' stdout output:
Thu May 16 14:29:48 2019 TUN/TAP TX queue length set to 100
Thu May 16 14:29:48 2019 /usr/bin/ip link set dev tun0 up mtu 1500

2019-05-16 14:29:48,826 DEBG 'start-script' stdout output:
Thu May 16 14:29:48 2019 /usr/bin/ip addr add dev tun0 10.16.140.169/24 broadcast 10.16.140.255

2019-05-16 14:29:48,829 DEBG 'start-script' stdout output:
Thu May 16 14:29:48 2019 /root/openvpnup.sh tun0 1500 1553 10.16.140.169 255.255.255.0 init

2019-05-16 14:29:48,898 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 140366125504104 for <Subprocess at 140366125504944 with name privoxy-script in state RUNNING> (stdout)>
2019-05-16 14:29:48,898 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 140366125601344 for <Subprocess at 140366125504944 with name privoxy-script in state RUNNING> (stderr)>
2019-05-16 14:29:48,899 INFO exited: privoxy-script (exit status 0; expected)
2019-05-16 14:29:48,899 DEBG received SIGCHLD indicating a child quit
2019-05-16 14:29:48,902 DEBG 'watchdog-script' stdout output:
[info] Deluge listening interface IP 0.0.0.0 and VPN provider IP 10.16.140.169 different, marking for reconfigure

2019-05-16 14:29:48,906 DEBG 'watchdog-script' stdout output:
[info] Deluge not running

2019-05-16 14:29:48,910 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI not running

2019-05-16 14:29:48,919 DEBG 'watchdog-script' stdout output:
[info] Privoxy not running

2019-05-16 14:29:48,974 DEBG 'start-script' stdout output:
Error: could not find any address for the name: `ns1.google.com'

2019-05-16 14:29:48,986 DEBG 'start-script' stdout output:
Error: could not find any address for the name: `resolver1.opendns.com'

2019-05-16 14:29:49,041 DEBG 'start-script' stdout output:
[warn] Cannot determine external IP address, exhausted retries setting to tunnel IP '10.16.140.169'

2019-05-16 14:29:49,124 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Deluge...
[info] Removing deluge pid file (if it exists)...

2019-05-16 14:29:49,472 DEBG 'watchdog-script' stdout output:
[info] Deluge listening interface currently defined as 0.0.0.0
[info] Deluge listening interface will be changed to 0.0.0.0
[info] Saving changes to Deluge config file /config/core.conf...

2019-05-16 14:29:49,850 DEBG 'watchdog-script' stdout output:
[info] Deluge process started
[info] Waiting for Deluge process to start listening on port 58846...

2019-05-16 14:29:50,228 DEBG 'watchdog-script' stdout output:
[info] Deluge process listening on port 58846

2019-05-16 14:29:50,902 DEBG 'watchdog-script' stdout output:
[info] No torrents with state 'Error' found

2019-05-16 14:29:50,903 DEBG 'watchdog-script' stdout output:
[info] Starting Deluge Web UI...

2019-05-16 14:29:50,903 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI started

2019-05-16 14:29:51,054 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Privoxy...

2019-05-16 14:29:52,065 DEBG 'watchdog-script' stdout output:
[info] Privoxy process started
[info] Waiting for Privoxy process to start listening on port 8118...

2019-05-16 14:29:52,085 DEBG 'watchdog-script' stdout output:
[info] Privoxy process listening on port 8118

2019-05-16 14:29:53,323 DEBG 'start-script' stdout output:
Thu May 16 14:29:53 2019 /usr/bin/ip route add 185.183.106.2/32 via 10.42.0.1

2019-05-16 14:29:53,326 DEBG 'start-script' stdout output:
Thu May 16 14:29:53 2019 /usr/bin/ip route add 0.0.0.0/1 via 10.16.140.1

2019-05-16 14:29:53,329 DEBG 'start-script' stdout output:
Thu May 16 14:29:53 2019 /usr/bin/ip route add 128.0.0.0/1 via 10.16.140.1

2019-05-16 14:29:53,331 DEBG 'start-script' stdout output:
Thu May 16 14:29:53 2019 Initialization Sequence Completed

 

Link to comment
Hi
 
I need help with the following error in the docker log.
I have VPN enabled =yes and added my ipvanish credentials and copied the opvn file.
The WebUI is not accessible even though the docker starts. Below is the only error I have.... tried manually creating the log file but didn't help.
 
Options error: --status fails with '/tmp/openvpn/openvpn-status.log': No such file or directory (errno=2)
See op documentation link, further help

Sent from my EML-L29 using Tapatalk

Link to comment

HI - Been using this for a while.. just have one question that may be simple to answer.. i added a plugin (labelplus) but was told i need to access via the GTK ui. I notice on the docker that there is GTK support, but for the life of me i dont know how to access it.. i presently access deluge via the URL, but need the added functionality supported by GTK. ANy help greatly appreciated.. And as always, wonderful tool and docker!

Link to comment

Hello, I am trying to get this container to work on Windows 10 Home/VirtualBox (with PIA).  I can load the WebUI when VPN is disabled, but not when VPN is enabled.  I am getting some errors saying it is unable to load the "tun" and "iptable_mangle" kernel modules.  It seems perhaps due to the "boot2docker" linux distribution installed by Docker Toolbox not including those modules.  I tried poking around with modprobe and insmod, but can't find those modules anywhere.  Maybe I need to switch to a full Ubuntu VM?  Any advice appreciated

 

Created by...
___.   .__       .__                   
\_ |__ |__| ____ |  |__   ____ ___  ___
 | __ \|  |/    \|  |  \_/ __ \\  \/  /
 | \_\ \  |   |  \   Y  \  ___/ >    < 
 |___  /__|___|  /___|  /\___  >__/\_ \
     \/        \/     \/     \/      \/
   https://hub.docker.com/u/binhex/
2019-05-19T04:51:04.158968346Z 
2019-05-19 04:51:04.222506 [info] System information Linux 8653b1aa6b62 4.14.116-boot2docker #1 SMP Tue May 7 00:02:53 UTC 2019 x86_64 GNU/Linux
2019-05-19 04:51:04.305272 [warn] PUID not defined (via -e PUID), defaulting to '99'
2019-05-19 04:51:04.396465 [warn] PGID not defined (via -e PGID), defaulting to '100'
2019-05-19 04:51:04.483063 [warn] UMASK not defined (via -e UMASK), defaulting to '000'
2019-05-19 04:51:04.551872 [info] Permissions already set for volume mappings
2019-05-19 04:51:04.630154 [info] DELUGE_DAEMON_LOG_LEVEL defined as 'error'
2019-05-19 04:51:04.696064 [info] DELUGE_WEB_LOG_LEVEL defined as 'error'
2019-05-19 04:51:04.764571 [info] VPN_ENABLED defined as 'yes'
2019-05-19 04:51:04.852407 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/CA Vancouver.ovpn
dos2unix: converting file /config/openvpn/CA Vancouver.ovpn to Unix format...
2019-05-19 04:51:04.972339 [info] VPN remote line defined as 'remote ca-vancouver.privateinternetaccess.com 1198'
2019-05-19 04:51:05.048131 [info] VPN_REMOTE defined as 'ca-vancouver.privateinternetaccess.com'
2019-05-19 04:51:05.131323 [info] VPN_PORT defined as '1198'
2019-05-19 04:51:05.219232 [info] VPN_PROTOCOL defined as 'udp'
2019-05-19 04:51:05.297366 [info] VPN_DEVICE_TYPE defined as 'tun0'
2019-05-19 04:51:05.372794 [info] VPN_PROV defined as 'pia'
2019-05-19 04:51:05.444010 [info] LAN_NETWORK defined as '192.168.1.0/24'
2019-05-19 04:51:05.511089 [info] NAME_SERVERS defined as '209.222.18.222,37.235.1.174,1.1.1.1,8.8.8.8,209.222.18.218,37.235.1.177,1.0.0.1,8.8.4.4'
2019-05-19 04:51:05.579170 [info] VPN_USER defined as 'secret'
2019-05-19 04:51:05.648672 [info] VPN_PASS defined as 'secret'
2019-05-19 04:51:05.715182 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2019-05-19 04:51:05.783505 [info] STRICT_PORT_FORWARD defined as 'yes'
2019-05-19 04:51:05.850706 [info] ENABLE_PRIVOXY defined as 'yes'
2019-05-19 04:51:05.957054 [info] Starting Supervisor...
2019-05-19 04:51:06,347 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing
2019-05-19 04:51:06,348 INFO Set uid to user 0 succeeded
2019-05-19 04:51:06,352 INFO supervisord started with pid 6
2019-05-19 04:51:07,358 INFO spawned: 'privoxy-script' with pid 151
2019-05-19 04:51:07,369 INFO spawned: 'start-script' with pid 152
2019-05-19 04:51:07,387 INFO spawned: 'watchdog-script' with pid 153
2019-05-19 04:51:07,389 INFO reaped unknown pid 7
2019-05-19 04:51:07,446 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN
2019-05-19T04:51:07.446367633Z 
2019-05-19 04:51:07,447 INFO success: privoxy-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2019-05-19 04:51:07,447 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2019-05-19 04:51:07,448 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2019-05-19 04:51:07,482 DEBG 'watchdog-script' stderr output:
dos2unix: 
2019-05-19 04:51:07,485 DEBG 'watchdog-script' stderr output:
converting file /config/core.conf to Unix format...
2019-05-19T04:51:07.485221614Z 
2019-05-19 04:51:07,736 DEBG 'start-script' stdout output:
[info] Default route for container is 172.17.0.1
2019-05-19T04:51:07.736755755Z 
2019-05-19 04:51:07,746 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.222 to /etc/resolv.conf
2019-05-19T04:51:07.746390518Z 
2019-05-19 04:51:07,758 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.174 to /etc/resolv.conf
2019-05-19T04:51:07.759226958Z 
2019-05-19 04:51:07,786 DEBG 'start-script' stdout output:
[info] Adding 1.1.1.1 to /etc/resolv.conf
2019-05-19T04:51:07.786440172Z 
2019-05-19 04:51:07,823 DEBG 'start-script' stdout output:
[info] Adding 8.8.8.8 to /etc/resolv.conf
2019-05-19T04:51:07.823246741Z 
2019-05-19 04:51:07,848 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.218 to /etc/resolv.conf
2019-05-19T04:51:07.849031119Z 
2019-05-19 04:51:07,866 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.177 to /etc/resolv.conf
2019-05-19T04:51:07.866386188Z 
2019-05-19 04:51:07,875 DEBG 'start-script' stdout output:
[info] Adding 1.0.0.1 to /etc/resolv.conf
2019-05-19T04:51:07.875859288Z 
2019-05-19 04:51:07,894 DEBG 'start-script' stdout output:
[info] Adding 8.8.4.4 to /etc/resolv.conf
2019-05-19T04:51:07.894462726Z 
2019-05-19 04:51:08,039 DEBG 'start-script' stdout output:
[info] Attempting to load tun kernel module...
2019-05-19T04:51:08.039642552Z 
2019-05-19 04:51:08,042 DEBG 'start-script' stderr output:
modprobe: FATAL: Module tun not found in directory /lib/modules/4.14.116-boot2docker
2019-05-19T04:51:08.042602072Z 
2019-05-19 04:51:08,044 DEBG 'start-script' stdout output:
[warn] Unable to load tun kernel module using modprobe, trying insmod...
2019-05-19T04:51:08.044463650Z 
2019-05-19 04:51:08,046 DEBG 'start-script' stderr output:
insmod: ERROR: could not load module /lib/modules/tun.ko: No such file or directory
2019-05-19T04:51:08.046896868Z 
2019-05-19 04:51:08,047 DEBG 'start-script' stdout output:
[warn] Unable to load tun kernel module, assuming its dynamically loaded
2019-05-19T04:51:08.048029200Z 
2019-05-19 04:51:08,066 DEBG 'start-script' stdout output:
[info] Attempting to load iptable_mangle module...
2019-05-19T04:51:08.066306521Z 
2019-05-19 04:51:08,068 DEBG 'start-script' stderr output:
modprobe: FATAL: Module iptable_mangle not found in directory /lib/modules/4.14.116-boot2docker
2019-05-19T04:51:08.069067887Z 
2019-05-19 04:51:08,069 DEBG 'start-script' stdout output:
[warn] Unable to load iptable_mangle module using modprobe, trying insmod...
2019-05-19T04:51:08.069963682Z 
2019-05-19 04:51:08,072 DEBG 'start-script' stderr output:
insmod: ERROR: could not load module /lib/modules/iptable_mangle.ko: No such file or directory
2019-05-19T04:51:08.072452205Z 
2019-05-19 04:51:08,073 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-05-19T04:51:08.073808775Z 
2019-05-19 04:51:08,203 DEBG 'start-script' stdout output:
[info] Docker network defined as    172.17.0.0/16
2019-05-19T04:51:08.203439225Z 
2019-05-19 04:51:08,236 DEBG 'start-script' stdout output:
[info] Adding 192.168.1.0/24 as route via docker eth0
2019-05-19T04:51:08.236295143Z 
2019-05-19 04:51:08,238 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------
2019-05-19T04:51:08.239013074Z 
2019-05-19 04:51:08,240 DEBG 'start-script' stdout output:
default via 172.17.0.1 dev eth0 
2019-05-19T04:51:08.241088940Z 
2019-05-19 04:51:08,241 DEBG 'start-script' stdout output:
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-05-19T04:51:08.241633686Z 
2019-05-19 04:51:08,242 DEBG 'start-script' stdout output:
--------------------
2019-05-19T04:51:08.242870190Z 
2019-05-19 04:51:08,330 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------
2019-05-19T04:51:08.330638843Z 
2019-05-19 04:51:08,343 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 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 -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 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
2019-05-19T04:51:08.344331429Z 
2019-05-19 04:51:08,345 DEBG 'start-script' stdout output:
--------------------
2019-05-19T04:51:08.345846333Z 
2019-05-19 04:51:08,348 DEBG 'start-script' stdout output:
[info] Starting OpenVPN...
2019-05-19T04:51:08.348841904Z 
2019-05-19 04:51:08,414 DEBG 'start-script' stdout output:
Sun May 19 04:51:08 2019 WARNING: file 'credentials.conf' is group or others accessible
Sun May 19 04:51:08 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
Sun May 19 04:51:08 2019 library versions: OpenSSL 1.1.1b  26 Feb 2019, LZO 2.10
2019-05-19T04:51:08.414446912Z 
2019-05-19 04:51:08,418 DEBG 'start-script' stdout output:
[info] OpenVPN started
2019-05-19T04:51:08.418932742Z 
2019-05-19 04:51:08,426 DEBG 'start-script' stdout output:
Sun May 19 04:51:08 2019 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
2019-05-19T04:51:08.427094469Z 
2019-05-19 04:51:08,433 DEBG 'start-script' stdout output:
Sun May 19 04:51:08 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]107.181.189.75:1198
2019-05-19T04:51:08.433707732Z 
2019-05-19 04:51:08,434 DEBG 'start-script' stdout output:
Sun May 19 04:51:08 2019 UDP link local: (not bound)
Sun May 19 04:51:08 2019 UDP link remote: [AF_INET]107.181.189.75:1198
2019-05-19T04:51:08.434331395Z 
2019-05-19 04:51:08,871 DEBG 'start-script' stdout output:
Sun May 19 04:51:08 2019 [48318619defaee809b29e6bdd000e42d] Peer Connection Initiated with [AF_INET]107.181.189.75:1198
2019-05-19T04:51:08.872143291Z 
2019-05-19 04:51:09,979 DEBG 'start-script' stdout output:
Sun May 19 04:51:09 2019 TUN/TAP device tun0 opened
2019-05-19T04:51:09.979818727Z 
2019-05-19 04:51:09,980 DEBG 'start-script' stdout output:
Sun May 19 04:51:09 2019 /usr/bin/ip link set dev tun0 up mtu 1500
2019-05-19T04:51:09.981139113Z 
2019-05-19 04:51:10,026 DEBG 'start-script' stdout output:
Sun May 19 04:51:10 2019 /usr/bin/ip addr add dev tun0 local 10.79.10.6 peer 10.79.10.5
2019-05-19T04:51:10.027059285Z 
2019-05-19 04:51:10,048 DEBG 'start-script' stdout output:
Sun May 19 04:51:10 2019 /root/openvpnup.sh tun0 1500 1558 10.79.10.6 10.79.10.5 init
2019-05-19T04:51:10.048906653Z 
2019-05-19 04:51:10,138 DEBG 'start-script' stdout output:
Sun May 19 04:51:10 2019 Initialization Sequence Completed
2019-05-19T04:51:10.139051470Z 
2019-05-19 04:51:10,412 DEBG 'start-script' stdout output:
[info] Attempting to curl https://www.privateinternetaccess.com/vpninfo/servers?version=82...
2019-05-19T04:51:10.412843670Z 
2019-05-19 04:51:10,492 DEBG 'watchdog-script' stdout output:
[info] Deluge listening interface IP 0.0.0.0 and VPN provider IP 10.79.10.6 different, marking for reconfigure
2019-05-19T04:51:10.492425988Z 
2019-05-19 04:51:10,521 DEBG 'watchdog-script' stdout output:
[info] Deluge not running
2019-05-19T04:51:10.521716383Z 
2019-05-19 04:51:10,536 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI not running
2019-05-19T04:51:10.536922108Z 
2019-05-19 04:51:10,557 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 140227393625896 for <Subprocess at 140227393624552 with name privoxy-script in state RUNNING> (stdout)>
2019-05-19 04:51:10,558 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 140227393725048 for <Subprocess at 140227393624552 with name privoxy-script in state RUNNING> (stderr)>
2019-05-19 04:51:10,558 INFO exited: privoxy-script (exit status 0; expected)
2019-05-19 04:51:10,559 DEBG received SIGCHLD indicating a child quit
2019-05-19 04:51:11,053 DEBG 'start-script' stdout output:
[info] Successfully retrieved external IP address 107.181.189.75
2019-05-19T04:51:11.054588909Z 
2019-05-19 04:51:11,235 DEBG 'start-script' stdout output:
[info] Curl successful for https://www.privateinternetaccess.com/vpninfo/servers?version=82, response code 200
2019-05-19T04:51:11.235803787Z 
2019-05-19 04:51:11,491 DEBG 'start-script' stdout output:
[info] List of PIA endpoints that support port forwarding:-
[info] ca-toronto.privateinternetaccess.com
[info] ca-montreal.privateinternetaccess.com
[info] ca-vancouver.privateinternetaccess.com
[info] de-berlin.privateinternetaccess.com
[info] de-frankfurt.privateinternetaccess.com
[info] sweden.privateinternetaccess.com
[info] swiss.privateinternetaccess.com
[info] france.privateinternetaccess.com
[info] czech.privateinternetaccess.com
[info] spain.privateinternetaccess.com
[info] ro.privateinternetaccess.com
[info] israel.privateinternetaccess.com
2019-05-19T04:51:11.491769388Z 
2019-05-19 04:51:11,509 DEBG 'start-script' stdout output:
[info] Attempting to curl http://209.222.18.222:2000/?client_id=461d9b40d87a3e330e27821a6d258e74d30f088d188df4a9bddfbef2087becd7...
2019-05-19T04:51:11.509776051Z 
2019-05-19 04:51:12,223 DEBG 'start-script' stdout output:
[info] Curl successful for http://209.222.18.222:2000/?client_id=461d9b40d87a3e330e27821a6d258e74d30f088d188df4a9bddfbef2087becd7, response code 200
2019-05-19T04:51:12.224360193Z 
2019-05-19 04:51:13,076 DEBG 'watchdog-script' stdout output:
[info] Deluge incoming port 6890 and VPN incoming port 49058 different, marking for reconfigure
2019-05-19T04:51:13.077130447Z 
2019-05-19 04:51:13,079 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Deluge...
2019-05-19T04:51:13.079709198Z 
2019-05-19 04:51:13,080 DEBG 'watchdog-script' stdout output:
[info] Removing deluge pid file (if it exists)...
2019-05-19T04:51:13.080679559Z 
2019-05-19 04:51:13,908 DEBG 'watchdog-script' stdout output:
[info] Deluge listening interface currently defined as 0.0.0.0
[info] Deluge listening interface will be changed to 0.0.0.0
[info] Saving changes to Deluge config file /config/core.conf...
2019-05-19T04:51:13.908585450Z 
2019-05-19 04:51:14,763 DEBG 'watchdog-script' stdout output:
[info] Deluge process started
[info] Waiting for Deluge process to start listening on port 58846...
2019-05-19T04:51:14.763766477Z 
2019-05-19 04:51:15,552 DEBG 'watchdog-script' stdout output:
[info] Deluge process listening on port 58846
2019-05-19T04:51:15.552194680Z 
2019-05-19 04:51:16,979 DEBG 'watchdog-script' stdout output:
Setting random_port to False..
Configuration value successfully updated.
2019-05-19T04:51:16.979403486Z 
2019-05-19 04:51:18,419 DEBG 'watchdog-script' stdout output:
Setting listen_ports to (49058, 49058)..
Configuration value successfully updated.
2019-05-19T04:51:18.419591042Z 
2019-05-19 04:51:19,951 DEBG 'watchdog-script' stdout output:
[info] No torrents with state 'Error' found
[info] Starting Deluge Web UI...
[info] Deluge Web UI started
2019-05-19T04:51:19.952113847Z 

 

Link to comment

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.