[Support] binhex - DelugeVPN


Recommended Posts

1 hour ago, binhex said:

Try wireguard

Sent from my 22021211RG using Tapatalk
 

Changed to Wireguard, still getting:

2022-12-28 21:05:38,291 DEBG 'start-script' stdout output:
[warn] Unable to successfully download PIA json to generate token for wireguard from URL 'https://www.privateinternetaccess.com/gtoken/generateToken'
[info] 12 retries left
[info] Retrying in 10 secs...

Link to comment
3 hours ago, frodr said:

binhex deluge-ups works fine with PIA. But binhex radarr and sonarr indexer stopped connecting a few days back.

 

Log from binhex-sonarr:

2022-12-28 19:35:22,555 DEBG 'radarr' stdout output:
[Warn] RadarrErrorPipeline: Invalid request Validation failed: 
 -- : Unable to connect to indexer, check the log for more details
 

 

What log is it referring to?

 

Log from binhex deluge-van.
2022-12-28 19:37:20,522 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '56946'

 

I found errors in radarr log file. Can anyone say what I have to do to fix indexer log on issues, please?

 

2022-12-28 22:38:14.9|Error|Newznab|An error occurred while processing indexer feed.

 

[v4.2.4.6635] System.Net.Http.HttpRequestException: Resource temporarily unavailable (nzbfinder.ws:443)

---> System.Net.Sockets.SocketException (11): Resource temporarily unavailable

 

and

 

[v4.2.4.6635] System.Net.Http.HttpRequestException: Connection refused (localhost:8112)

---> System.Net.Sockets.SocketException (111): Connection refused

 

 

binhex radarr log file..rtf

Link to comment

I'm having an issue and I don't know if it's Deluge, the tracker, my OPNsense router, or my modem (modem is in passthrough so I really doubt it).  Based on the evidence, I am almost certain it's Deluge or the tracker, because this problem is happening with only one specific tracker out of the five or so trackers I am using at the moment.

 

Presently on the problematic tracker Deluge is seeding 1286 torrents (total for all trackers is 1697 torrents).  The problematic tracker's web site reports that I am only seeding exactly 1200 torrents at this moment.  Earlier today it reported 1179 torrents seeding.  Does anyone know what might cause this on my end before I start asking questions of the tracker admins?  Many users of said tracker are seeding more torrents than I am.

 

Also, the torrents that are missing according to the tracker, report being connected to the tracker in Deluge (no tracker error).  I have tried update tracker (does nothing), force recheck (does nothing), pause torrent and restart (tracker temporarily sees the torrent again then loses it after a while), deleting the torrent readding force recheck.  Nothing fixes it permanently or for more than about an hour.  It also seems to hover around the same torrents.  I have even been uploading on some while the tracker reports I'm not even hosting as well.

 

I don't think it's settings in OPNsense as I do not lose any torrents on any other trackers.  I'm also allowing a rediculiously huge number of connections:

 

image.thumb.png.f9a0c69d7f339ad7396377a84c8701d8.png

 

This is particularly bad because it can happen on new torrents as well as old ones.  I almost got two HNR's because the tracker thought I was not seeding.  Luckily, I caught it in time.  

 

Also, I paused about 100 torrents on said tracker and the tracker maintained connection to all the remaining torrents properly.

Edited by craigr
Link to comment
On 12/28/2022 at 10:59 PM, frodr said:

 

I found errors in radarr log file. Can anyone say what I have to do to fix indexer log on issues, please?

 

2022-12-28 22:38:14.9|Error|Newznab|An error occurred while processing indexer feed.

 

[v4.2.4.6635] System.Net.Http.HttpRequestException: Resource temporarily unavailable (nzbfinder.ws:443)

---> System.Net.Sockets.SocketException (11): Resource temporarily unavailable

 

and

 

[v4.2.4.6635] System.Net.Http.HttpRequestException: Connection refused (localhost:8112)

---> System.Net.Sockets.SocketException (111): Connection refused

 

 

binhex radarr log file..rtf 11.17 kB · 0 downloads

I would be very happy if anyone can point a direction to fix this problem: binhex-delugevpn works fine, but indexers in Sonarr and Radarr can not connect. Error happened during last week. Sonarr and Radarr communicates thru deluge-vpn.

Link to comment

I'm having a strange issue with seeding using this container. I have it set up to both public and private trackers. I've searched the forums for the past hour, but I'm struggling to find anything that helps. Any help would be much appreciated! The information I have so far is below:

 

  1. Seeding on private trackers doesn't appear to be working fully on all trackers, I only seem to be able to provide file parts to a very very small number of peers (kb's).
  2. Downloads mostly work (for some reason the ubuntu desktop image I only have one seed I can download from out of 1400 odd in the swarm, other torrents seem fine), and when I check the port status, my PIA VPN's IP and Port set by the container on start-up are open (using online port checker tools, and netcat from another linux machine).
  3. I'm assuming the issue is my outbound traffic is not routing correctly through to the other peers as I don't seem to have an issue with inbound traffic.
  4. There are peers I am seeding to, however only rarely does one appear that I start uploading to (I've attached two torrents, one unicorn which I seeded about 10gb to a single other peer showing it's not my upload speed, and one which is typical of the rest of my torrents). I assume those rare peers fully connectable, and I am not fully connectable in the swarm; hence the other peers don't receive as much data because I'm not connectable. I know they are getting files from other peers in the swarm as I can see their % going up.
  5. The settings on the docker are mostly unmodified, just additional port mappings to enable me to route other containers through the VPN.

image.png.bc2519aa23ac1194b65b904738900408.png

 

image.thumb.png.29f392391cc54217e420d220d7ec4b65.png

 

image.png.583b731d109f4bb7d3cb2120fd7dbfe9.png

 

image.png.fd6bc1d1cf57ac8a42333b561062369d.png

 

image.png.d32e19d2e63a6bd9af5b495569b71c82.png

Edited by Locke
Link to comment
On 12/28/2022 at 11:10 PM, johnny2678 said:

 looks like multiple DNS servers set via NAME_SERVERS but failover not working.  Changed mine to 1.0.0.1, 8.8.8.8 and looks like it's working now

Same for me . .  I had a problem in Sonarr and Radarr with the Privoxy connection on  port 8118.

The change in Deluge NAME_SERVERS solved the problem . .

Link to comment
4 minutes ago, elcapitano said:

Same for me . .  I had a problem in Sonarr and Radarr with the Privoxy connection on  port 8118.

The change in Deluge NAME_SERVERS solved the problem . .

I have a slew of entries in this field in my config (i don't remember why - as i set this up years ago). Is it safe to delete all of those and just go with 1.0.0.1 and 8.8.8.8? I am happy to post all the addresses i have in that key field if that would help.

Link to comment
51 minutes ago, helpermonkey said:

I have a slew of entries in this field in my config (i don't remember why - as i set this up years ago). Is it safe to delete all of those and just go with 1.0.0.1 and 8.8.8.8? I am happy to post all the addresses i have in that key field if that would help.

I made a copy of the Ip's, and put in 1.0.0.1 and 8.8.8.8 - All my problems solved

 

Edited by elcapitano
  • Like 1
Link to comment
1 hour ago, elcapitano said:

I made a copy of the Ip's, and put in 1.0.0.1 and 8.8.8.8 - All my problems solved

 

I was having the same issue and switching to 8.8.8.8 fixed it, however I just went back and checked using the default string of DNS servers that I backed up and they are working again. Seems like the PIA DNS servers 209.222.18.222 and 209.222.18.218 were having resolution issues but are working again now.

Link to comment

hi guys ive been routing my containers such as sabnzbd ,sonaar and  radarr through binhexs deluge vpn useing PIA,  i thought id try useing privoxy for sonarr and radarr instead ive made sure im set up the same as spaceinvader ones videos , connected radarr to the home host address and  the port 8118 as shown but they wont  connect to privoxy any ideas ? im no expert at all so please forgive me 

Link to comment
I was having the same issue and switching to 8.8.8.8 fixed it, however I just went back and checked using the default string of DNS servers that I backed up and they are working again. Seems like the PIA DNS servers 209.222.18.222 and 209.222.18.218 were having resolution issues but are working again now.
The pia DNS have been flaky for years now, if you look at my readme you will see I no longer specify them

Sent from my 22021211RG using Tapatalk


Link to comment

Hey guys noob questions incoming LOL - Where do I change the name servers for DNS. I am still having issues and have not tried this yet. Thanks!

EDIT: Neverminded that was a dumb question LOL. To change the name servers it's under the docker configuration labeled NAME_SERVERS. Changed them per above posts and everything is up and running again. Thanks.

Edited by AtomZ
Link to comment

Hello, I have some problems with the configuration.

 

I use ProtonVPN with DelugeVPN. The VPN tunnel goes up well, I recover an ip well.

 

However, I cannot connect Sonarr or Radarr to DelugeVPN.

 

I tried to tweak the VPN_INPUT_PORTS and VPN_OUTPUT_PORTS but nothing worked...

All docker images are on the same Vlan (520).
I can access DelugeVPN's web interface.

 

I specify: Only DelugeVPN is mounted on the VPN, Sonarr and Raddar are on my local network (Vlan 520) and therefore not affected by the VPN.

 

I think I'm close to succeeding, but I'm missing a piece of configuration that I haven't found yet (Unraid Forum, Github, Reddit..).

I don't know if I should use Privoxy? I don't see the use of it in my case.

 

Here are some screenshots of my current conf.

 

Thank you in advance for your help.

 

Thank you Binhex for your work!

sorry for my English

conf_sonarr.png

conf_deluge.png

conf_docker_deluge.png

overview_docker.png

Link to comment

Hi all,

 

Apologies is this is clearly covered somewhere - I've been troubleshooting for days and not having a great deal of success.

 

New Unraid user here, using 6.11.5. I have installed the binhex-delugevpn container, and done my best to configure it with NordVPN; specifically I've downloaded the OpenVPN configs (I've done this with multiples, all of their listed P2P servers). I believe I have my subnet set correctly (I triple checked according to the FAQ).

 

My issue is that when I connect to the WebUI, it will be on for a short amount of time, then disconnect. It seems to just cycle through over and over, restarting every minute or so. I do have the Socks5 proxy set up with the NordVPN credentials as well.

 

My logs seem to loop through the end part of the following:

Quote

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

2023-01-01 18:48:01.599684 [info] Host is running unRAID
2023-01-01 18:48:01.638010 [info] System information Linux 557ec5626082 5.19.17-Unraid #2 SMP PREEMPT_DYNAMIC Wed Nov 2 11:54:15 PDT 2022 x86_64 GNU/Linux
2023-01-01 18:48:01.683192 [info] OS_ARCH defined as 'x86-64'
2023-01-01 18:48:01.726101 [info] PUID defined as '99'
2023-01-01 18:48:01.772813 [info] PGID defined as '100'
2023-01-01 18:48:01.843299 [info] UMASK defined as '000'
2023-01-01 18:48:01.886094 [info] Permissions already set for '/config'
2023-01-01 18:48:01.930681 [info] Deleting files in /tmp (non recursive)...
2023-01-01 18:48:01.981751 [info] VPN_ENABLED defined as 'yes'
2023-01-01 18:48:02.026317 [info] VPN_CLIENT defined as 'openvpn'
2023-01-01 18:48:02.068669 [info] VPN_PROV defined as 'custom'
2023-01-01 18:48:02.123201 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/<<<REDACTED>>>.nordvpn.com.udp.ovpn
2023-01-01 18:48:02.204762 [info] VPN remote server(s) defined as '<<<REDACTED>>>,'
2023-01-01 18:48:02.245097 [info] VPN remote port(s) defined as '1194,'
2023-01-01 18:48:02.282559 [info] VPN remote protcol(s) defined as 'udp,'
2023-01-01 18:48:02.325372 [info] VPN_DEVICE_TYPE defined as 'tun0'
2023-01-01 18:48:02.369926 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2023-01-01 18:48:02.413608 [info] LAN_NETWORK defined as '192.168.0.0/24'
2023-01-01 18:48:02.456582 [info] NAME_SERVERS defined as '84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1'
2023-01-01 18:48:02.500057 [info] VPN_USER defined as '<<<REDACTED>>>'
2023-01-01 18:48:02.543814 [info] VPN_PASS defined as '<<<REDACTED>>>'
2023-01-01 18:48:02.588332 [info] ENABLE_PRIVOXY defined as 'yes'
2023-01-01 18:48:02.635180 [info] VPN_INPUT_PORTS not defined (via -e VPN_INPUT_PORTS), skipping allow for custom incoming ports
2023-01-01 18:48:02.676991 [info] VPN_OUTPUT_PORTS not defined (via -e VPN_OUTPUT_PORTS), skipping allow for custom outgoing ports
2023-01-01 18:48:02.718975 [info] DELUGE_DAEMON_LOG_LEVEL defined as 'info'
2023-01-01 18:48:02.761916 [info] DELUGE_WEB_LOG_LEVEL defined as 'info'
2023-01-01 18:48:02.809326 [info] Starting Supervisor...
2023-01-01 18:48:03,132 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing
2023-01-01 18:48:03,133 INFO Set uid to user 0 succeeded
2023-01-01 18:48:03,135 INFO supervisord started with pid 7
2023-01-01 18:48:04,138 INFO spawned: 'start-script' with pid 176
2023-01-01 18:48:04,140 INFO spawned: 'watchdog-script' with pid 177
2023-01-01 18:48:04,141 INFO reaped unknown pid 8 (exit status 0)
2023-01-01 18:48:04,148 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2023-01-01 18:48:04,149 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2023-01-01 18:48:04,149 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2023-01-01 18:48:04,255 DEBG 'start-script' stdout output:
[info] Adding 84.200.69.80 to /etc/resolv.conf

2023-01-01 18:48:04,260 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.174 to /etc/resolv.conf

2023-01-01 18:48:04,264 DEBG 'start-script' stdout output:
[info] Adding 1.1.1.1 to /etc/resolv.conf

2023-01-01 18:48:04,268 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.177 to /etc/resolv.conf

2023-01-01 18:48:04,273 DEBG 'start-script' stdout output:
[info] Adding 84.200.70.40 to /etc/resolv.conf

2023-01-01 18:48:04,277 DEBG 'start-script' stdout output:
[info] Adding 1.0.0.1 to /etc/resolv.conf

2023-01-01 18:48:04,283 DEBG 'start-script' stdout output:
<<<REDACTED>>>

2023-01-01 18:48:04,311 DEBG 'start-script' stdout output:
[info] Default route for container is 172.17.0.1

2023-01-01 18:48:04,331 DEBG 'start-script' stdout output:
[info] Docker network defined as    172.17.0.0/16

2023-01-01 18:48:04,336 DEBG 'start-script' stdout output:
[info] Adding 192.168.0.0/24 as route via docker eth0

2023-01-01 18:48:04,337 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2023-01-01 18:48:04,339 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.0.0/24 via 172.17.0.1 dev eth0 
local 127.0.0.0/8 dev lo table local proto kernel scope host src 127.0.0.1 
local 127.0.0.1 dev lo table local proto kernel scope host src 127.0.0.1 
broadcast 127.255.255.255 dev lo table local proto kernel scope link src 127.0.0.1 

2023-01-01 18:48:04,339 DEBG 'start-script' stdout output:
local 172.17.0.2 dev eth0 table local proto kernel scope host src 172.17.0.2 
broadcast 172.17.255.255 dev eth0 table local proto kernel scope link src 172.17.0.2 
--------------------

2023-01-01 18:48:04,344 DEBG 'start-script' stdout output:
iptable_mangle         16384  1
ip_tables              28672  3 iptable_filter,iptable_nat,iptable_mangle
x_tables               45056  16 ip6table_filter,xt_conntrack,iptable_filter,ip6table_nat,xt_tcpudp,xt_addrtype,xt_CHECKSUM,xt_nat,ip6_tables,ipt_REJECT,ip_tables,iptable_nat,ip6table_mangle,xt_MASQUERADE,iptable_mangle,xt_mark

2023-01-01 18:48:04,345 DEBG 'start-script' stdout output:
[info] iptable_mangle support detected, adding fwmark for tables

2023-01-01 18:48:04,402 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2023-01-01 18:48:04,404 DEBG 'start-script' stdout output:
-P INPUT DROP
-P FORWARD DROP
-P OUTPUT DROP
-A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A INPUT -s <<<REDACTED>>>/32 -i eth0 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 8112 -j ACCEPT
-A INPUT -i eth0 -p udp -m udp --dport 8112 -j ACCEPT
-A INPUT -s 192.168.0.0/24 -d 172.17.0.0/16 -i eth0 -p tcp -m tcp --dport 58846 -j ACCEPT
-A INPUT -s 192.168.0.0/24 -d 172.17.0.0/16 -i eth0 -p tcp -m tcp --dport 8118 -j ACCEPT
-A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -i tun0 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A OUTPUT -d <<<REDACTED>>>/32 -o eth0 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 8112 -j ACCEPT
-A OUTPUT -o eth0 -p udp -m udp --sport 8112 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 192.168.0.0/24 -o eth0 -p tcp -m tcp --sport 58846 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 192.168.0.0/24 -o eth0 -p tcp -m tcp --sport 8118 -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

2023-01-01 18:48:04,405 DEBG 'start-script' stdout output:
--------------------

2023-01-01 18:48:04,406 DEBG 'start-script' stdout output:
[info] Starting OpenVPN (non daemonised)...

2023-01-01 18:48:04,416 DEBG 'start-script' stdout output:
2023-01-01 18:48:04 DEPRECATED OPTION: --cipher set to 'AES-256-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'AES-256-CBC' to --data-ciphers or change --cipher 'AES-256-CBC' to --data-ciphers-fallback 'AES-256-CBC' to silence this warning.

2023-01-01 18:48:04,416 DEBG 'start-script' stdout output:
2023-01-01 18:48:04 WARNING: file 'credentials.conf' is group or others accessible

2023-01-01 18:48:04,417 DEBG 'start-script' stdout output:
2023-01-01 18:48:04 OpenVPN 2.5.7 [git:makepkg/a0f9a3e9404c8321+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on May 31 2022
2023-01-01 18:48:04 library versions: OpenSSL 1.1.1q  5 Jul 2022, LZO 2.10

2023-01-01 18:48:04,417 DEBG 'start-script' stdout output:
2023-01-01 18:48:04 WARNING: --ping should normally be used with --ping-restart or --ping-exit
2023-01-01 18:48:04 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2023-01-01 18:48:04,418 DEBG 'start-script' stdout output:
2023-01-01 18:48:04 Outgoing Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
2023-01-01 18:48:04 Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication

2023-01-01 18:48:04,418 DEBG 'start-script' stdout output:
2023-01-01 18:48:04 TCP/UDP: Preserving recently used remote address: [AF_INET]185.187.243.11:1194
2023-01-01 18:48:04 Socket Buffers: R=[212992->212992] S=[212992->212992]
2023-01-01 18:48:04 UDP link local: (not bound)
2023-01-01 18:48:04 UDP link remote: [AF_INET]<<<REDACTED>>>:1194

2023-01-01 18:48:04,439 DEBG 'start-script' stdout output:
2023-01-01 18:48:04 TLS: Initial packet from [AF_INET]<<<REDACTED>>>:1194, sid=3d484d12 09a43288

2023-01-01 18:48:04,482 DEBG 'start-script' stdout output:
2023-01-01 18:48:04 VERIFY OK: depth=2, C=PA, O=NordVPN, CN=NordVPN Root CA

2023-01-01 18:48:04,483 DEBG 'start-script' stdout output:
2023-01-01 18:48:04 VERIFY OK: depth=1, C=PA, O=NordVPN, CN=NordVPN CA7

2023-01-01 18:48:04,483 DEBG 'start-script' stdout output:
2023-01-01 18:48:04 VERIFY KU OK
2023-01-01 18:48:04 Validating certificate extended key usage
2023-01-01 18:48:04 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
2023-01-01 18:48:04 VERIFY EKU OK
2023-01-01 18:48:04 VERIFY X509NAME OK: CN=<<<REDACTED>>>.nordvpn.com

2023-01-01 18:48:04,484 DEBG 'start-script' stdout output:
2023-01-01 18:48:04 VERIFY OK: depth=0, CN=<<<REDACTED>>>.nordvpn.com

2023-01-01 18:48:04,505 DEBG 'start-script' stdout output:
2023-01-01 18:48:04 Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, peer certificate: 4096 bit RSA, signature: RSA-SHA512
2023-01-01 18:48:04 [<<<REDACTED>>>.nordvpn.com] Peer Connection Initiated with [AF_INET]185.187.243.11:1194

2023-01-01 18:48:05,635 DEBG 'start-script' stdout output:
2023-01-01 18:48:05 SENT CONTROL [<<<REDACTED>>>.nordvpn.com]: 'PUSH_REQUEST' (status=1)

2023-01-01 18:48:05,635 DEBG 'start-script' stdout output:
2023-01-01 18:48:05 PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1,dhcp-option DNS 103.86.96.100,dhcp-option DNS 103.86.99.100,sndbuf 524288,rcvbuf 524288,explicit-exit-notify,comp-lzo no,route-gateway 10.8.0.1,topology subnet,ping 60,ping-restart 180,ifconfig 10.8.0.7 255.255.255.0,peer-id 5,cipher AES-256-GCM'
2023-01-01 18:48:05 OPTIONS IMPORT: timers and/or timeouts modified
2023-01-01 18:48:05 OPTIONS IMPORT: explicit notify parm(s) modified
2023-01-01 18:48:05 OPTIONS IMPORT: compression parms modified
2023-01-01 18:48:05 OPTIONS IMPORT: --sndbuf/--rcvbuf options modified
2023-01-01 18:48:05 Socket Buffers: R=[212992->1048576] S=[212992->1048576]
2023-01-01 18:48:05 OPTIONS IMPORT: --ifconfig/up options modified
2023-01-01 18:48:05 OPTIONS IMPORT: route options modified
2023-01-01 18:48:05 OPTIONS IMPORT: route-related options modified
2023-01-01 18:48:05 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
2023-01-01 18:48:05 OPTIONS IMPORT: peer-id set
2023-01-01 18:48:05 OPTIONS IMPORT: adjusting link_mtu to 1657
2023-01-01 18:48:05 OPTIONS IMPORT: data channel crypto options modified
2023-01-01 18:48:05 Data Channel: using negotiated cipher 'AES-256-GCM'
2023-01-01 18:48:05 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
2023-01-01 18:48:05 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
2023-01-01 18:48:05 net_route_v4_best_gw query: dst 0.0.0.0
2023-01-01 18:48:05 net_route_v4_best_gw result: via 172.17.0.1 dev eth0
2023-01-01 18:48:05 ROUTE_GATEWAY 172.17.0.1/255.255.0.0 IFACE=eth0 HWADDR=02:42:ac:11:00:02

2023-01-01 18:48:05,636 DEBG 'start-script' stdout output:
2023-01-01 18:48:05 TUN/TAP device tun0 opened
2023-01-01 18:48:05 net_iface_mtu_set: mtu 1500 for tun0
2023-01-01 18:48:05 net_iface_up: set tun0 up
2023-01-01 18:48:05 net_addr_v4_add: 10.8.0.7/24 dev tun0
2023-01-01 18:48:05 /root/openvpnup.sh tun0 1500 1585 10.8.0.7 255.255.255.0 init

2023-01-01 18:48:05,638 DEBG 'start-script' stdout output:
2023-01-01 18:48:05 net_route_v4_add: <<<REDACTED>>>/32 via 172.17.0.1 dev [NULL] table 0 metric -1

2023-01-01 18:48:05,639 DEBG 'start-script' stdout output:
2023-01-01 18:48:05 net_route_v4_add: 0.0.0.0/1 via 10.8.0.1 dev [NULL] table 0 metric -1
2023-01-01 18:48:05 net_route_v4_add: 128.0.0.0/1 via 10.8.0.1 dev [NULL] table 0 metric -1
2023-01-01 18:48:05 Initialization Sequence Completed

2023-01-01 18:48:05,643 DEBG 'start-script' stdout output:
egrep: warning: egrep is obsolescent; using grep -E

2023-01-01 18:48:06,653 DEBG 'start-script' stdout output:
egrep: warning: egrep is obsolescent; using grep -E

2023-01-01 18:48:06,662 DEBG 'start-script' stdout output:
egrep: warning: egrep is obsolescent; using grep -E

2023-01-01 18:48:06,706 DEBG 'start-script' stdout output:
[info] Attempting to get external IP using 'http://checkip.amazonaws.com'...

2023-01-01 18:48:14,821 DEBG 'start-script' stdout output:
egrep: warning: egrep is obsolescent; using grep -E

2023-01-01 18:48:14,828 DEBG 'start-script' stdout output:
[info] Successfully retrieved external IP address <<<REDACTED>>>

2023-01-01 18:48:14,832 DEBG 'start-script' stdout output:
[info] Application does not require port forwarding or VPN provider is != pia, skipping incoming port assignment

2023-01-01 18:48:14,876 DEBG 'watchdog-script' stdout output:
[info] Deluge listening interface IP 0.0.0.0 and VPN provider IP 10.8.0.7 different, marking for reconfigure

2023-01-01 18:48:14,882 DEBG 'watchdog-script' stdout output:
[info] Deluge not running

2023-01-01 18:48:14,887 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI not running

2023-01-01 18:48:14,892 DEBG 'watchdog-script' stdout output:
[info] Privoxy not running

2023-01-01 18:48:14,892 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Deluge...
[info] Removing deluge pid file (if it exists)...

2023-01-01 18:48:15,474 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'listen_interface' currently has a value of '10.8.3.2'
[info] Deluge key 'listen_interface' will have a new value '10.8.0.7'
[info] Writing changes to Deluge config file '/config/core.conf'...

2023-01-01 18:48:15,907 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'outgoing_interface' currently has a value of 'tun0'
[info] Deluge key 'outgoing_interface' will have a new value 'tun0'
[info] Writing changes to Deluge config file '/config/core.conf'...

2023-01-01 18:48:16,313 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'default_daemon' currently has a value of 'bcd43c63afb448d29bbca6a202b9ba19'
[info] Deluge key 'default_daemon' will have a new value 'bcd43c63afb448d29bbca6a202b9ba19'
[info] Writing changes to Deluge config file '/config/web.conf'...

2023-01-01 18:48:16,958 DEBG 'watchdog-script' stdout output:
[info] Deluge process started
[info] Waiting for Deluge process to start listening on port 58846...

2023-01-01 18:48:17,284 DEBG 'watchdog-script' stdout output:
[info] Deluge process listening on port 58846

2023-01-01 18:48:21,776 DEBG 'watchdog-script' stderr output:
<Deferred at 0x14e09d88e4d0 current result: None>

2023-01-01 18:48:21,879 DEBG 'watchdog-script' stdout output:
[info] No torrents with state 'Error' found

2023-01-01 18:48:21,879 DEBG 'watchdog-script' stdout output:
[info] Starting Deluge Web UI...

2023-01-01 18:48:21,879 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI started

2023-01-01 18:48:21,881 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Privoxy...

2023-01-01 18:48:22,889 DEBG 'watchdog-script' stdout output:
[info] Privoxy process started
[info] Waiting for Privoxy process to start listening on port 8118...

2023-01-01 18:48:22,894 DEBG 'watchdog-script' stdout output:
[info] Privoxy process listening on port 8118

2023-01-01 18:49:07,958 DEBG 'watchdog-script' stdout output:
[info] Deluge not running

2023-01-01 18:49:07,969 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Deluge...
[info] Removing deluge pid file (if it exists)...

2023-01-01 18:49:08,332 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'listen_interface' currently has a value of '10.8.0.7'
[info] Deluge key 'listen_interface' will have a new value '10.8.0.7'
[info] Writing changes to Deluge config file '/config/core.conf'...

2023-01-01 18:49:08,729 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'outgoing_interface' currently has a value of 'tun0'
[info] Deluge key 'outgoing_interface' will have a new value 'tun0'
[info] Writing changes to Deluge config file '/config/core.conf'...

2023-01-01 18:49:09,142 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'default_daemon' currently has a value of 'bcd43c63afb448d29bbca6a202b9ba19'
[info] Deluge key 'default_daemon' will have a new value 'bcd43c63afb448d29bbca6a202b9ba19'
[info] Writing changes to Deluge config file '/config/web.conf'...

2023-01-01 18:49:09,796 DEBG 'watchdog-script' stdout output:
[info] Deluge process started
[info] Waiting for Deluge process to start listening on port 58846...

2023-01-01 18:49:10,129 DEBG 'watchdog-script' stdout output:
[info] Deluge process listening on port 58846

2023-01-01 18:49:14,618 DEBG 'watchdog-script' stderr output:
<Deferred at 0x14b2d707e6b0 current result: None>

2023-01-01 18:49:14,720 DEBG 'watchdog-script' stdout output:
[info] No torrents with state 'Error' found

2023-01-01 18:49:44,769 DEBG 'watchdog-script' stdout output:
[info] Deluge not running

2023-01-01 18:49:44,780 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Deluge...
[info] Removing deluge pid file (if it exists)...

2023-01-01 18:49:45,138 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'listen_interface' currently has a value of '10.8.0.7'
[info] Deluge key 'listen_interface' will have a new value '10.8.0.7'
[info] Writing changes to Deluge config file '/config/core.conf'...

2023-01-01 18:49:45,545 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'outgoing_interface' currently has a value of 'tun0'
[info] Deluge key 'outgoing_interface' will have a new value 'tun0'
[info] Writing changes to Deluge config file '/config/core.conf'...

2023-01-01 18:49:45,957 DEBG 'watchdog-script' stdout output:
[info] Deluge key 'default_daemon' currently has a value of 'bcd43c63afb448d29bbca6a202b9ba19'
[info] Deluge key 'default_daemon' will have a new value 'bcd43c63afb448d29bbca6a202b9ba19'
[info] Writing changes to Deluge config file '/config/web.conf'...

2023-01-01 18:49:46,640 DEBG 'watchdog-script' stdout output:
[info] Deluge process started
[info] Waiting for Deluge process to start listening on port 58846...

2023-01-01 18:49:46,966 DEBG 'watchdog-script' stdout output:
[info] Deluge process listening on port 58846

2023-01-01 18:49:51,456 DEBG 'watchdog-script' stderr output:
<Deferred at 0x151c2dc32080 current result: None>

2023-01-01 18:49:51,559 DEBG 'watchdog-script' stdout output:
[info] No torrents with state 'Error' found

2023-01-01 18:51:06,770 DEBG 'watchdog-script' stdout output:
[info] Deluge not running

Any guidance would be much appreciated.

 

Link to comment
On 12/31/2022 at 11:21 AM, Knh68 said:

hi guys ive been routing my containers such as sabnzbd ,sonaar and  radarr through binhexs deluge vpn useing PIA,  i thought id try useing privoxy for sonarr and radarr instead ive made sure im set up the same as spaceinvader ones videos , connected radarr to the home host address and  the port 8118 as shown but they wont  connect to privoxy any ideas ? im no expert at all so please forgive me 

I'm having an idential issue but have nordvpn. Did you find a fix?

 

I move the dns server list to have 1.1.1.1 as the first option

image.thumb.png.eb9287a2a33a84fa8864000b7f8b3cf6.png

Edited by Tom90
fixed for me
Link to comment

Hi everyone, had a quick search on the forum but couldn't see anything. 

I've just made a change to my network resulting in a new static ip for my server. My delugevpn container and associated *arrs will now no longer connect to the internet. All my other dockers that don't go through the deluge vpn container are now working.

 

Is there something I've missed that needs changing within the delugevpn docker container? For example on my Plex docker I had to go in to the preferences.xml file and change the ip address in there. 

Link to comment

I dont see where the name parameters is located. Someone above posted a screenshot but I dont have that option. I am on the following repository:

 

binhex/arch-delugevpn:test

 

and I figure my version doesnt have this. Can someone post the respository I should be in to see this name_server option. Thanks again

Link to comment

Hi, I'm wondering if I can get some help, I'm trying to get Privoxy to work and in reading the forum I saw that PIA (what I was using) is being flaky so I replaced it with AirVPN. I set up a forwarded port and generated .crt/.key/.key and /.ovpn files and put them in openvpn (removing the PIA files) and when I change the ports to the ones I specified in AirVPN I get this error when I try to save the docker container:

 

docker: Error response from daemon: driver failed programming external connectivity on endpoint binhex-delugevpn (0ce07624958ca487d10d58fa71eadc16fe5c26b4d69ab7cbcb26546bcc3a61c9): Bind for 0.0.0.0:28312 failed: port is already allocated.

 

Goes without saying but I also can't start the container. Any ideas what I'm doing wrong?

Link to comment
25 minutes ago, severanced said:

when I change the ports to the ones I specified in AirVPN I get this error when I try to save the docker container:

Where exactly did you do this? You're not supposed to put the forwarded port in the container settings. You put it in deluge settings  for incoming port in the webui when the container has started.

Edited by strike
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.