[Support] binhex - qBittorrentVPN


Recommended Posts

On 4/8/2023 at 11:00 PM, klavinsd said:

Hi, I'm having 2 issues with my setup. I'm on Windows 11, running this with Docker-Desktop. I'm starting the docker image from Ubuntu WSL. Launching using the following config:

 

docker run -d \
    --memory=100MB \
    --cpus="0.1" \
    --cap-add=NET_ADMIN \
    -p 6881:6881 \
    -p 6881:6881/udp \
    -p 8080:8080 \
    -p 8118:8118 \
    --name=qbittorrentvpn \
    -v /mnt/e:/data \
    -v /mnt/e/qBittorrentDocker:/config \
    -v /etc/localtime:/etc/localtime:ro \
    -e VPN_ENABLED=yes \
    -e VPN_PROV=custom \
    -e VPN_CLIENT=openvpn \
    -e STRICT_PORT_FORWARD=no \
    -e ENABLE_PRIVOXY=no \
    -e DEBUG=false \
    -e WEBUI_PORT=8080 \
    -e UMASK=000 \
    -e UID=1000 \
    -e PID=1000 \
    binhex/arch-qbittorrentvpn

UID 1000 is my Ubuntu WSL user

 

Problem 1: sed: preserving permissions for ‘/config/qBittorrent/config/sedzRuF7u’: Operation not permitted

The config folder is located is located in an external drive connected to my PC, and using -v /mnt/e/config:config

All of the files within /config/qBittorrent/config/ folder have rwxrwxrwx permissions with group and owner being 1000

I have also granted Full Access permissions for the folder for Users user from Windows side of the drive (not sure how what kind of user Windows interprets the WSL Ubuntu as)

 

 

Problem 2:

When restarting the container, all of the torrent files get re-checked, which takes quite some time even for few torrents.

Download location for the torrents is in the -v /mnt/e:/data \ directory. Why is qBittorrent re-checking torrents every time the container restarts? The same behaviour doesn't happen if I was running qBittorrent on a PC and restarted it. How can I fix this?

Bump

Link to comment
On 4/11/2023 at 5:26 AM, binhex said:

this is a vpn provider related issue, the openvpn config file supplied by your provider is not compatible with the latest release of openvpn, the vpn provider needs to sort this out i would encourage you to reach out to them and report what you are seeing.

 

That was the issue. I used their config builder to create a new config file and it worked with the latest image. 

 

I left in the line "comp-lzo adaptive" and it seems to work, in spite of an earlier post saying that the comp-lzo line had to be removed. 

 

Link to comment
22 hours ago, sonofdbn said:

I've done that a few times and the ports have always matched. Thanks for checking the log file.

 

But there's some other weirdness going on that I've just noticed. Getting late here, will post later.

In the GUI only a few torrents were listed, but I have many more that should have been seeding, and on the docker page the container was showing some percentage of CPU activity (2%-3%), not consistent with no/minimal activity.


Anyway, getting a bit desperate, I tried installing the libtorrentv1 version as a new container. I started the new container but

although I had changed the GUI port I didn't get any login screen. Then I realised that the original container (4.3.9-2-01) was still running, and perhaps illogically thought that might be the problem. So I stopped it and went looking for differences in the appdata folders.

 

There I found that I had messed up because although I changed the container name for the new version, I had forgotten to change the appdata folder; so it used the same appdata folder as my current problematic container. So I stopped the new container, gave it a new appdata folder and restarted. Same problem, couldn't get to the GUI. So stopped it, and started the old container to see what had been damaged by installing into the same folder.

 

But miraculously the old container was now working! So problem solved, but no idea what fixed it. I realise there's zero interest in this from anyone else, but I leave this here in case it helps @binhex in some way.

Link to comment

I am routing another containers Internet traffic through the VPN Connection of QbittorrentVPN and expose two ports (14444 and 31000) of this Container to my ISPs IP Adress to reach these ports from remote. The two ports are mapped in qbittorrentvpn docker to the Unraid's server local IP adress. I set up port forwarding for these ports in my router accordingly, however the ports are not reachable. Any ideas how to investigate?

Link to comment
12 minutes ago, JonathanM said:

I believe you would need to add the remote WAN addresses you wish to access from into the LAN network container entry.

 

To be honest, I don't understand what you mean.

 

Let me give an example: I am routing nzbget through the qbittorrentvpn container to secure usenet downloads through VPN tunneling. Everything is working on local network meaning I can access the WebUI from NZBget.

However, when I try to access the nzbget Web-UI on port 6789 from anywhere else using my dyndns account I cannot access it.

How to achieve that? 

Link to comment
47 minutes ago, unn4m3d said:

To be honest, I don't understand what you mean.

https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

See Q4.

Binhex's VPN containers are locked down, you must add exceptions for each IP that will be allowed to access the webui.

48 minutes ago, unn4m3d said:

How to achieve that?

Either list each network you are going to be accessing it from as above, or set up a reverse proxy where the container sees the accesses as local.

  • Thanks 1
Link to comment

I've had some success w/ SpaceInvaderOne's tutorial using binhex-deluge-vpn w/ binhex-radarr & sonarr. But constantly struggling with indexers for a long time now.

Recently was able to get a very clear tutorial incorporating prowlarr & qBittorrent. Works great, except does not have vpn instructions included.

https://flemmingss.com/a-minimal-configuration-step-by-step-guide-to-media-automation-in-unraid-using-radarr-sonarr-prowlarr-jellyfin-jellyseerr-and-qbittorrent/

What I'd like is some help w/ a clear tutorial getting prowlarr set up w/ binhex-docker apps, including deluge-vpn OR getting qBitorrent from the more flemming's tutorial behind a vpn.

I've tried to add bihhex-qbittorrentvpn w/ similar configurations, but it fails to start.

i'm lost when it comes to changing ports or troubleshooting w/o a clear tutorial. 
What is best way to get prowlarr integration, w/ vpn (pia) for torrents?

 

Link to comment

I'm trying to get privoxy working with prowlarr but having some problems. I've enabled it in qbittorrent and the log shows it starting. 

 

When I try to enable it in prowlarr I get this error

 

Failed to test proxy: An error occurred while sending the request.

 

Am I missing something? I use airvpn (with openvpn), not really sure what I need to do with the forwarded port.

Link to comment

When i was using the BINHEX rtorrent vpn docker it could auto unpack/extract pretty much any zip or rar file that the client downloaded. ive moved to qbittorent now and im starting to regret it based upon this feature not being preasant. does anyone know how to get this docker container to unzip/unpack all different rar zip archives after downloads have finished :?

Link to comment
6 hours ago, fujitsubo said:

When i was using the BINHEX rtorrent vpn docker it could auto unpack/extract pretty much any zip or rar file that the client downloaded. ive moved to qbittorent now and im starting to regret it based upon this feature not being preasant. does anyone know how to get this docker container to unzip/unpack all different rar zip archives after downloads have finished :?

I use the Unpackerr docker for this.

Link to comment

SOLVED!: For future reference,I just had to generate a new wg0.conf. I should have tried that from the start lol.

 

Hello!  As of a docker restart today, I am unable to access the webui.  The reason for the docker restart is that I've noticed the past few weeks my downloads/uploads will randomly stall out, and restarting the docker always fixes this.  The only warning I see in the logs is "Warning: `/config/wireguard/wg0.conf' is world accessible", but to my knowledge, it's been like that since day 1.  I'm using Mullvad wireguard config.  I'm fairly new to Unraid in general, but it's been running great for the past 2-3 months that I've had it, minus the little hiccups of stalling out on this docker.

 

Any ideas?  I can provide logs.

 

EDIT 1: After about 10-15 minutes the webui will come back up, but logs show

"Couldn't download IP geolocation database file. Reason: The remote host name was not found (invalid hostname)".  I unchecked the peer resolve in advanced settings, no change.

 

I can add torrents, but they start at stalled and never actually begin downloading. 

 

EDIT 2: Rebooted the server about...20 minutes ago, docker is started but no WebUI again. No logs since I added my last torrent maybe 30 minutes ago.

 

EDIT 3: Something wacky def going on, Web UI finally came back up, yet still nothing will download.  No errors that I am seeing.

 

EDIT 4: Looks DNS related, nothing has changed on my end. 

2023-04-25 15:51:28,036 DEBG 'watchdog-script' stdout output:
[info] DNS failure, creating file '/tmp/dnsfailure' to indicate failure...

2023-04-25 15:51:28,919 DEBG 'start-script' stdout output:
[info] DNS failure, creating file '/tmp/dnsfailure' to indicate failure...

2023-04-25 15:51:28,920 DEBG 'start-script' stdout output:
[info] Attempting to get external IP using 'http://checkip.amazonaws.com'...

2023-04-25 15:51:38,923 DEBG 'start-script' stdout output:
[info] Failed on last attempt, attempting to get external IP using 'http://whatismyip.akamai.com'...

2023-04-25 15:51:48,927 DEBG 'start-script' stdout output:
[info] Failed on last attempt, attempting to get external IP using 'https://ifconfig.co/ip'...

2023-04-25 15:51:58,930 DEBG 'start-script' stdout output:
[info] Failed on last attempt, attempting to get external IP using 'https://showextip.azurewebsites.net'...

Edited by Roncore
Link to comment
1 hour ago, fujitsubo said:

 

that will only work if you are trying to unpack things that radarr sonarr etc grabbed with qbittorent. im trying to unpack just manual torrents ive downloaded

I believe it will unpack any file it detects in the download location. Haven’t tested this though.

Link to comment

Things are working well, but I had a quick question. With the default qbittorrent Connection options, "Use UPnP / NAT-PMP port forwarding from my router" was checked. In the past I have seen it recommended to uncheck this when using a VPN. Downloading torrents seems to work fine either way. I'm using port forwarding with PIA.

 

Is there a reason it was checked on? Does it even matter, since the port forwarding is being handled by the VPN?

Thanks.

Link to comment
7 hours ago, cthog said:

Anyone else recently lose access to the webui?  I had an issue back in January due to my settings, but got it working well.  Haven't changed settings, but now my webui times out.

Attach the contents of supervisord.log (in your appdata folder) to your next post. Be sure to redact users and passwords.

Link to comment
18 hours ago, wgstarks said:

Attach the contents of supervisord.log (in your appdata folder) to your next post. Be sure to redact users and passwords.

Thanks for taking a look, here's today's log:

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

2023-04-28 04:34:32.185076 [info] System information Linux 7ef720cc5ef1 5.15.0-71-generic #78-Ubuntu SMP Tue Apr 18 09:00:29 UTC 2023 x86_64 GNU/Linux
2023-04-28 04:34:32.257982 [info] OS_ARCH defined as 'x86-64'
2023-04-28 04:34:32.318559 [info] PUID defined as '1000'
2023-04-28 04:34:32.385269 [info] PGID defined as '1000'
2023-04-28 04:34:32.470249 [info] UMASK defined as '000'
2023-04-28 04:34:32.521585 [info] Permissions already set for '/config'
2023-04-28 04:34:32.598543 [info] Deleting files in /tmp (non recursive)...
2023-04-28 04:34:32.652932 [info] VPN_ENABLED defined as 'yes'
2023-04-28 04:34:32.692235 [info] VPN_CLIENT defined as 'wireguard'
2023-04-28 04:34:32.731073 [info] VPN_PROV defined as 'pia'
2023-04-28 04:34:32.798825 [info] WireGuard config file (conf extension) is located at /config/wireguard/wg0.conf
2023-04-28 04:34:32.867298 [info] VPN_REMOTE_SERVER defined as 'nl-amsterdam.privacy.network'
2023-04-28 04:34:32.924918 [info] VPN_REMOTE_PORT defined as '1337'
2023-04-28 04:34:32.959046 [info] VPN_DEVICE_TYPE defined as 'wg0'
2023-04-28 04:34:32.989168 [info] VPN_REMOTE_PROTOCOL defined as 'udp'
modprobe: FATAL: Module ip6_tables not found in directory /lib/modules/5.15.0-71-generic
ip6tables v1.8.9 (legacy): can't initialize ip6tables table `filter': Table does not exist (do you need to insmod?)
Perhaps ip6tables or your kernel needs to be upgraded.
2023-04-28 04:34:33.564674 [warn] ip6tables default policies not available, skipping ip6tables drops
2023-04-28 04:34:33.740587 [info] LAN_NETWORK defined as '192.168.0.0/24'
2023-04-28 04:34:33.783770 [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-04-28 04:34:33.834974 [info] VPN_USER defined as 'pxxxxxxxxx'
2023-04-28 04:34:33.876378 [info] VPN_PASS defined as 'xxxxxxxxxx'
2023-04-28 04:34:33.920518 [info] STRICT_PORT_FORWARD defined as 'yes'
2023-04-28 04:34:33.970296 [info] ENABLE_PRIVOXY defined as 'yes'
2023-04-28 04:34:34.020579 [info] VPN_INPUT_PORTS defined as '1234'
2023-04-28 04:34:34.073507 [info] VPN_OUTPUT_PORTS defined as '5678'
2023-04-28 04:34:34.129953 [info] WEBUI_PORT defined as '7070'
2023-04-28 04:34:34.194653 [info] Starting Supervisor...
2023-04-28 04:34:35,380 INFO Included extra file "/etc/supervisor/conf.d/qbittorrent.conf" during parsing
2023-04-28 04:34:35,380 INFO Set uid to user 0 succeeded
2023-04-28 04:34:35,391 INFO supervisord started with pid 7
2023-04-28 04:34:36,395 INFO spawned: 'start-script' with pid 267
2023-04-28 04:34:36,398 INFO spawned: 'watchdog-script' with pid 268
2023-04-28 04:34:36,398 INFO reaped unknown pid 8 (exit status 0)
2023-04-28 04:34:36,407 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

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

2023-04-28 04:34:36,416 DEBG 'watchdog-script' stdout output:
[info] qBittorrent config file already exists, skipping copy
[info] Removing session lock file (if it exists)...

2023-04-28 04:34:36,416 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.174 to /etc/resolv.conf

2023-04-28 04:34:36,423 DEBG 'start-script' stdout output:
[info] Adding 1.1.1.1 to /etc/resolv.conf

2023-04-28 04:34:36,428 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.177 to /etc/resolv.conf

2023-04-28 04:34:36,432 DEBG 'start-script' stdout output:
[info] Adding 84.200.70.40 to /etc/resolv.conf

2023-04-28 04:34:36,436 DEBG 'start-script' stdout output:
[info] Adding 1.0.0.1 to /etc/resolv.conf

2023-04-28 04:34:36,734 DEBG 'start-script' stdout output:
[info] Token generated for PIA wireguard authentication

2023-04-28 04:34:36,779 DEBG 'start-script' stdout output:
[info] Trying to connect to the PIA WireGuard API on 'nl-amsterdam.privacy.network'...

2023-04-28 04:34:37,399 DEBG 'start-script' stdout output:
[info] Default route for container is 172.17.0.1

2023-04-28 04:34:37,703 DEBG 'start-script' stdout output:
[info] Docker network defined as    172.17.0.0/16

2023-04-28 04:34:37,708 DEBG 'start-script' stdout output:
[info] Adding 192.168.0.0/24 as route via docker eth0

2023-04-28 04:34:37,710 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2023-04-28 04:34:37,718 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.19 
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 
local 172.17.0.19 dev eth0 table local proto kernel scope host src 172.17.0.19 
broadcast 172.17.255.255 dev eth0 table local proto kernel scope link src 172.17.0.19 

2023-04-28 04:34:37,718 DEBG 'start-script' stdout output:
--------------------

2023-04-28 04:34:37,725 DEBG 'start-script' stdout output:
iptable_mangle         16384  0
ip_tables              32768  2 iptable_filter,iptable_mangle
x_tables               53248  9 xt_conntrack,iptable_filter,nft_compat,xt_tcpudp,xt_addrtype,xt_nat,ip_tables,xt_MASQUERADE,iptable_mangle

2023-04-28 04:34:37,726 DEBG 'start-script' stdout output:
[info] iptable_mangle support detected, adding fwmark for tables

2023-04-28 04:34:37,804 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2023-04-28 04:34:37,805 DEBG 'start-script' stdout output:
-P INPUT DROP
-P FORWARD DROP
-P OUTPUT DROP
-A INPUT -s 181.214.206.51/32 -i eth0 -j ACCEPT
-A INPUT -s 181.214.206.110/32 -i eth0 -j ACCEPT
-A INPUT -s 212.102.35.157/32 -i eth0 -j ACCEPT
-A INPUT -s 104.18.14.49/32 -i eth0 -j ACCEPT
-A INPUT -s 104.18.15.49/32 -i eth0 -j ACCEPT
-A INPUT -s 104.17.107.63/32 -i eth0 -j ACCEPT
-A INPUT -s 104.17.108.63/32 -i eth0 -j ACCEPT
-A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 7070 -j ACCEPT
-A INPUT -i eth0 -p udp -m udp --dport 7070 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 1234 -j ACCEPT
-A INPUT -i eth0 -p udp -m udp --dport 1234 -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 -s 192.168.0.0/24 -d 172.17.0.0/16 -i eth0 -p tcp -m tcp --sport 5678 -j ACCEPT
-A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -i wg0 -j ACCEPT
-A OUTPUT -d 181.214.206.51/32 -o eth0 -j ACCEPT
-A OUTPUT -d 181.214.206.110/32 -o eth0 -j ACCEPT
-A OUTPUT -d 212.102.35.157/32 -o eth0 -j ACCEPT
-A OUTPUT -d 104.18.14.49/32 -o eth0 -j ACCEPT
-A OUTPUT -d 104.18.15.49/32 -o eth0 -j ACCEPT
-A OUTPUT -d 104.17.107.63/32 -o eth0 -j ACCEPT
-A OUTPUT -d 104.17.108.63/32 -o eth0 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 7070 -j ACCEPT
-A OUTPUT -o eth0 -p udp -m udp --sport 7070 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 1234 -j ACCEPT
-A OUTPUT -o eth0 -p udp -m udp --sport 1234 -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 -s 172.17.0.0/16 -d 192.168.0.0/24 -o eth0 -p tcp -m tcp --dport 5678 -j ACCEPT
-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A OUTPUT -o lo -j ACCEPT
-A OUTPUT -o wg0 -j ACCEPT

2023-04-28 04:34:37,807 DEBG 'start-script' stdout output:
--------------------

2023-04-28 04:34:37,810 DEBG 'start-script' stdout output:
[info] Attempting to bring WireGuard interface 'up'...

2023-04-28 04:34:37,826 DEBG 'start-script' stderr output:
Warning: `/config/wireguard/wg0.conf' is world accessible

2023-04-28 04:34:37,833 DEBG 'start-script' stderr output:
[#] ip link add wg0 type wireguard

2023-04-28 04:34:37,836 DEBG 'start-script' stderr output:
[#] wg setconf wg0 /dev/fd/63

2023-04-28 04:34:37,838 DEBG 'start-script' stderr output:
[#] ip -4 address add 10.4.169.6 dev wg0

2023-04-28 04:34:37,847 DEBG 'start-script' stderr output:
[#] ip link set mtu 1420 up dev wg0

2023-04-28 04:34:37,987 DEBG 'start-script' stderr output:
[#] wg set wg0 fwmark 51820

2023-04-28 04:34:37,989 DEBG 'start-script' stderr output:
[#] ip -4 route add 0.0.0.0/0 dev wg0 table 51820

2023-04-28 04:34:37,991 DEBG 'start-script' stderr output:
[#] ip -4 rule add not fwmark 51820 table 51820

2023-04-28 04:34:37,993 DEBG 'start-script' stderr output:
[#] ip -4 rule add table main suppress_prefixlength 0

2023-04-28 04:34:37,998 DEBG 'start-script' stderr output:
[#] sysctl -q net.ipv4.conf.all.src_valid_mark=1

2023-04-28 04:34:38,009 DEBG 'start-script' stderr output:
[#] iptables-restore -n

2023-04-28 04:34:38,035 DEBG 'start-script' stderr output:
[#] '/root/wireguardup.sh'

2023-04-28 04:34:39,258 DEBG 'start-script' stdout output:
[info] Attempting to get external IP using 'http://checkip.amazonaws.com'...

2023-04-28 04:34:39,579 DEBG 'start-script' stdout output:
[info] Successfully retrieved external IP address 181.214.206.51

2023-04-28 04:34:39,581 DEBG 'start-script' stdout output:
[info] WireGuard interface 'up'

2023-04-28 04:34:39,583 DEBG 'start-script' stdout output:
[info] Script started to assign incoming port

2023-04-28 04:34:39,583 DEBG 'start-script' stdout output:
[info] Port forwarding is enabled
[info] Checking endpoint 'nl-amsterdam.privacy.network' is port forward enabled...

2023-04-28 04:34:40,131 DEBG 'start-script' stdout output:
[info] PIA endpoint 'nl-amsterdam.privacy.network' is in the list of endpoints that support port forwarding

2023-04-28 04:34:40,133 DEBG 'start-script' stdout output:
[info] List of PIA endpoints that support port forwarding:-

2023-04-28 04:34:40,133 DEBG 'start-script' stdout output:
[info] japan-2.privacy.network
[info] hungary.privacy.network

2023-04-28 04:34:40,133 DEBG 'start-script' stdout output:
[info] rs.privacy.network
[info] japan.privacy.network
[info] austria.privacy.network
[info] tr.privacy.network
[info] in.privacy.network
[info] panama.privacy.network
[info] sofia.privacy.network
[info] mongolia.privacy.network
[info] br.privacy.network
[info] brussels.privacy.network
[info] zagreb.privacy.network
[info] uk-manchester.privacy.network
[info] greenland.privacy.network
[info] ua.privacy.network
[info] macau.privacy.network

2023-04-28 04:34:40,133 DEBG 'start-script' stdout output:
[info] ar.privacy.network
[info] es-valencia.privacy.network
[info] israel.privacy.network
[info] sg.privacy.network
[info] saudiarabia.privacy.network
[info] ee.privacy.network
[info] ro.privacy.network
[info] lu.privacy.network
[info] au-sydney.privacy.network
[info] pt.privacy.network
[info] sweden.privacy.network
[info] venezuela.privacy.network
[info] nigeria.privacy.network
[info] mexico.privacy.network
[info] uk-southampton.privacy.network
[info] denmark.privacy.network
[info] de-frankfurt.privacy.network

2023-04-28 04:34:40,133 DEBG 'start-script' stdout output:
[info] fi-2.privacy.network
[info] taiwan.privacy.network
[info] gr.privacy.network
[info] morocco.privacy.network
[info] bahamas.privacy.network
[info] philippines.privacy.network
[info] de-berlin.privacy.network
[info] mk.privacy.network
[info] china.privacy.network
[info] santiago.privacy.network
[info] italy.privacy.network
[info] ca-ontario.privacy.network
[info] ireland.privacy.network
[info] italy-2.privacy.network
[info] georgia.privacy.network
[info] malta.privacy.network
[info] aus-melbourne.privacy.network

2023-04-28 04:34:40,133 DEBG 'start-script' stdout output:
[info] al.privacy.network
[info] srilanka.privacy.network
[info] sanjose.privacy.network
[info] sk.privacy.network
[info] lt.privacy.network
[info] ca-vancouver.privacy.network
[info] au-brisbane-pf.privacy.network
[info] sweden-2.privacy.network
[info] vietnam.privacy.network
[info] cambodia.privacy.network
[info] no.privacy.network
[info] lv.privacy.network
[info] aus-perth.privacy.network
[info] liechtenstein.privacy.network
[info] france.privacy.network

2023-04-28 04:34:40,134 DEBG 'start-script' stdout output:
[info] spain.privacy.network
[info] uk-2.privacy.network
[info] fi.privacy.network
[info] nz.privacy.network
[info] swiss.privacy.network
[info] uk-london.privacy.network
[info] md.privacy.network
[info] kazakhstan.privacy.network
[info] jakarta.privacy.network
[info] ba.privacy.network
[info] denmark-2.privacy.network
[info] monaco.privacy.network
[info] bangladesh.privacy.network
[info] is.privacy.network
[info] au-adelaide-pf.privacy.network
[info] yerevan.privacy.network

2023-04-28 04:34:40,134 DEBG 'start-script' stdout output:
[info] bogota.privacy.network
[info] ae.privacy.network
[info] man.privacy.network
[info] kualalumpur.privacy.network
[info] egypt.privacy.network
[info] dz.privacy.network
[info] cyprus.privacy.network
[info] za.privacy.network
[info] czech.privacy.network
[info] qatar.privacy.network
[info] ad.privacy.network
[info] montenegro.privacy.network
[info] ca-toronto.privacy.network
[info] ca-montreal.privacy.network
[info] au-australia-so.privacy.network

2023-04-28 04:34:40,134 DEBG 'start-script' stdout output:
[info] nl-amsterdam.privacy.network
[info] slovenia.privacy.network
[info] hk.privacy.network
[info] poland.privacy.network

2023-04-28 04:34:43,173 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 04:34:43,204 DEBG 'watchdog-script' stdout output:
[info] qBittorrent listening interface IP 0.0.0.0 and VPN provider IP 10.4.169.6 different, marking for reconfigure

2023-04-28 04:34:43,221 DEBG 'watchdog-script' stdout output:
[info] qBittorrent not running

2023-04-28 04:34:43,228 DEBG 'watchdog-script' stdout output:
[info] Privoxy not running
[info] qBittorrent incoming port 6881 and VPN incoming port 22764 different, marking for reconfigure

2023-04-28 04:34:43,230 DEBG 'watchdog-script' stdout output:
[info] Removing session lock file (if it exists)...

2023-04-28 04:34:43,240 DEBG 'watchdog-script' stdout output:
[info] Attempting to start qBittorrent...

2023-04-28 04:34:43,389 DEBG 'watchdog-script' stdout output:
[info] qBittorrent process started
[info] Waiting for qBittorrent process to start listening on port 7070...

2023-04-28 04:34:43,633 DEBG 'watchdog-script' stdout output:
[info] qBittorrent process listening on port 7070

2023-04-28 04:34:43,671 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Privoxy...

2023-04-28 04:34:44,684 DEBG 'watchdog-script' stdout output:
[info] Privoxy process started
[info] Waiting for Privoxy process to start listening on port 8118...

2023-04-28 04:34:44,695 DEBG 'watchdog-script' stdout output:
[info] Privoxy process listening on port 8118

2023-04-28 04:49:43,526 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 05:04:43,858 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 05:19:44,227 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 05:34:44,569 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 05:49:46,393 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 06:04:46,736 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 06:19:47,067 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 06:34:47,421 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 06:49:47,938 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 07:04:48,280 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 07:19:48,608 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 07:34:48,944 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 07:49:49,282 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 08:04:49,927 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 08:19:50,268 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 08:34:50,625 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 08:49:50,945 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 09:04:51,290 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 09:19:51,649 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 09:34:52,009 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 09:49:52,363 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 10:04:52,702 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 10:19:53,064 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 10:34:53,394 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 10:49:53,752 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 11:04:54,086 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 11:19:54,417 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 11:34:55,023 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 11:49:55,371 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 12:04:55,723 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 12:19:56,090 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 12:34:56,429 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 12:49:56,761 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 13:04:57,114 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 13:19:57,487 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 13:34:57,834 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 13:49:58,172 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 14:04:58,527 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 14:19:59,956 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 14:35:00,296 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 14:50:00,626 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 15:05:00,983 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 15:20:01,323 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 15:35:02,006 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 15:50:02,353 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 16:05:02,697 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 16:20:03,062 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 16:35:03,398 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 16:50:03,732 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 17:05:04,075 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 17:20:04,450 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 17:35:05,974 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 17:50:06,471 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 18:05:06,815 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 18:20:07,462 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 18:35:08,838 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 18:50:09,204 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 19:05:09,566 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 19:20:09,924 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 19:35:10,388 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 19:50:11,233 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 20:05:11,557 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 20:20:11,936 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 20:35:12,296 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 20:50:13,655 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 21:05:14,005 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 21:20:14,369 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 21:35:14,754 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 21:50:15,102 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 22:05:15,457 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 22:20:15,829 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 22:35:16,178 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 22:50:16,535 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 23:05:16,896 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 23:20:17,235 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 23:35:17,597 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-28 23:50:17,953 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-29 00:05:18,298 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-29 00:20:18,662 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-29 00:35:20,043 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-29 00:50:20,381 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

2023-04-29 01:05:20,741 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '22764'

 

Link to comment

Hi.

 

I have a tracker that requires the ip of the device that gets the download and downloads to be the same (Jackett and Torrent client needs to have the same IP). To get around this on Transmission_VPN, I have set the Jackett container to use the Transmission container (--net=container:Transmission_VPN) and set the port in the Transmission container.

 

Now, I want to switch to qBittorrent. I have swapped the network settings to --net=container:qbittorrentvpn (that is the name of my container) and mapped 9117 to the qbittorrent container.

 

Now, Jackett works fine, but I am unable to access the webui at http://[MachineIP]:9117/UI/Dashboard, when testing in Sonarr/Radarr/Readarr, the tests work fine, just no WebUI.

 

I do see this in the logs:

 

Content root path: /app/Jackett/Content
Now listening on: http://[::]:9117

 

Any suggestions?

Link to comment

I've been having an issue thats been preventing me from switching to Mullvad like I'd like to do. All I did was change the VPN provider to custom and put the wg0.conf file in the proper wireguard directory. I stripped out the IPv6 stuff from the config file.

 

I can access the webUI from the server's local IP and port, but whenever I try to access it via reverse proxy I get a 504 timeout error. I have Nginx Proxy Manager running on a separate machine. It all worked properly when using PIA with the generated file.

 

No log entries past "[info] qBittorrent process listening on port 8080"

Nginx Proxy Manager has this in the error log for this proxy entry:

2023/05/04 16:12:12 [error] 1913618#1913618: *139310 upstream timed out (110: Connection timed out) while connecting to upstream, client: [IP ADDRESS], server: QB.DOMAIN.COM, request: "GET / HTTP/2.0", upstream: "http://[LOCAL IP]:8080/", host: "QB.DOMAIN.COM", referrer: "https://NPM.DOMAIN.COM"

I ran curl on the local IP address from the NPM server and it comes up fine. If I run curl on the webUI's port it times out.

 

It seems I can contact the Unraid server just fine, but attempts to contact the specific port for qBittorrent fail. Any ideas on where to start?

 

UPDATE: I think I narrowed it down. I have the machines connected via Tailscale, and when I change the LAN_NETWORK variable to 100.0.0.0/8, which is what Tailscale uses, everything works, but now I can't access it from my local IP. Any better way to set this up so I can use both?

 

UPDATE 2: I just discovered I can have multiple LAN networks in the LAN_NETWORK variable separated by a comma. All is good now that I have both in there.

Edited by BitNotFound
Link to comment

Hello ! 

I'm having an issue with my installations and i did not find a solution in the documentation. I set up my qbittorrent with an openvpn vpn. To this qbittorrent is connected sonarr and radarr. I wanted to separate the networks so sonarr does not have access to radarr, anc vice-versa. 

Here is a part of my docker-compose
 

version: "3"
services:  
  sonarr:
    image: lscr.io/linuxserver/sonarr:latest
    container_name: sonarr
    networks:
      - sonarr
      - prowlarr-sonarr
      - qbittorrent-sonarr
    environment:
      - PUID=1001
      - PGID=1006
      - UMASK=007
      - TZ=Etc/UTC
    volumes:
      - /config/sonarr:/config
      - /data/media_center:/data
    restart: unless-stopped
  radarr:
    image: lscr.io/linuxserver/radarr:latest
    container_name: radarr
    networks:
      - radarr
      - prowlarr-radarr
      - qbittorrent-radarr
    environment:
      - TZ=Etc/UTC
      - PUID=1007
      - PGID=1006
      - UMASK=007
    volumes:
      - /config/radarr:/config
      - /data/media_center:/data
    restart: unless-stopped
  qbittorrent:
    image: binhex/arch-qbittorrentvpn
    container_name: qbittorrent
    networks:
      - qbittorrent
      - qbittorrent-radarr
      - qbittorrent-sonarr
    ports:
      - 8080:8080
    cap_add:
      - NET_ADMIN
    volumes:
      - /config/qbittorrent:/config
      - /data/media_center/torrents:/data/torrents
      - /etc/localtime:/etc/localtime:ro
    environment:
      - VPN_ENABLED=yes
      - VPN_USER_FILE=/run/secrets/qbittorrent_vpn_user
      - VPN_USER_FILE=/run/secrets/qbittorrent_vpn_password
      - VPN_PROV=custom
      - ENABLE_PRIVOXY=no
      - VPN_CLIENT=openvpn
      - LAN_NETWORK=192.168.1.0/24
      - DEBUG=true
      - PUID=1005
      - PGID=1006
    secrets:
      - qbittorrent_vpn_user
      - qbittorrent_vpn_password
networks:
  sonarr:
  qbittorrent:
  qbittorrent-sonarr:
  qbittorrent-radarr:
  radarr:
  prowlarr:
  prowlarr-sonarr:
  prowlarr-radarr:

 

My issue is that when the vpn is set to off, everything is working well, i can download what i want, i have access to the web ui, and sonaar/radarr have access to the qbittorrent.

But, if i activate the VPN, everything is working well, EXCEPT that sonarr/radarr don't have access to qbittorrent. Note that when i use the default docker bridge, it works. 

I tried a lot of things, try to see the difference between the default network and the defined one, but nothing, so if someone has an idea about what can be the problem, it would be very kind, thank you ! 
And here is my log file, i tried to remove everything sensible, if you see something sensible let me know, and if you need more informations, same :).
 

Spoiler

 

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

2023-05-09 21:29:23.235790 [info] System information Linux 165c90e2816b 5.15.0-67-generic #74-Ubuntu SMP Wed Feb 22 14:14:39 UTC 2023 x86_64 GNU/Linux
2023-05-09 21:29:23.254755 [info] OS_ARCH defined as 'x86-64'
2023-05-09 21:29:23.280711 [info] PUID defined as '1005'
2023-05-09 21:29:23.313012 [info] PGID defined as '1006'
2023-05-09 21:29:23.343494 [warn] UMASK not defined (via -e UMASK), defaulting to '000'
2023-05-09 21:29:23.364224 [info] Permissions already set for '/config'
2023-05-09 21:29:23.387169 [info] Deleting files in /tmp (non recursive)...
2023-05-09 21:29:23.638465 [info] VPN_ENABLED defined as 'yes'
2023-05-09 21:29:23.659951 [info] VPN_CLIENT defined as 'openvpn'
2023-05-09 21:29:23.680872 [info] VPN_PROV defined as 'custom'
2023-05-09 21:29:23.705935 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/config.ovpn
2023-05-09 21:29:23.753511 [info] VPN remote server(s) defined as 'xxx.xxx.xxx.xxx,'
2023-05-09 21:29:23.773252 [info] VPN remote port(s) defined as 'xxxx,'
2023-05-09 21:29:23.793280 [info] VPN remote protcol(s) defined as 'udp,'
2023-05-09 21:29:23.817705 [info] VPN_DEVICE_TYPE defined as 'tun0'
2023-05-09 21:29:23.839041 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
xxx.xxx.xxx.xxx
2023-05-09 21:29:23.867023 [debug] iptables default policies available, setting policy to drop...
2023-05-09 21:29:23.895183 [debug] ip6tables default policies available, setting policy to drop...
2023-05-09 21:29:23.921887 [debug] Docker interface defined as eth0
2023-05-09 21:29:23.951156 [info] LAN_NETWORK defined as '192.168.1.0/24'
2023-05-09 21:29:23.972542 [warn] NAME_SERVERS not defined (via -e NAME_SERVERS), defaulting to name servers defined in readme.md
2023-05-09 21:29:23.994651 [warn] VPN_USER not defined (via -e VPN_USER), assuming authentication via other method
2023-05-09 21:29:24.019211 [warn] VPN_PASS not defined (via -e VPN_PASS), assuming authentication via other method
2023-05-09 21:29:24.045604 [info] ENABLE_PRIVOXY defined as 'no'
2023-05-09 21:29:24.075228 [info] VPN_INPUT_PORTS not defined (via -e VPN_INPUT_PORTS), skipping allow for custom incoming ports
2023-05-09 21:29:24.097367 [info] VPN_OUTPUT_PORTS not defined (via -e VPN_OUTPUT_PORTS), skipping allow for custom outgoing ports
2023-05-09 21:29:24.118281 [warn] WEBUI_PORT not defined (via -e WEBUI_PORT), defaulting to '8080'
2023-05-09 21:29:24.189071 [info] Starting Supervisor...
2023-05-09 21:29:24,382 INFO Included extra file "/etc/supervisor/conf.d/qbittorrent.conf" during parsing
2023-05-09 21:29:24,382 INFO Set uid to user 0 succeeded
2023-05-09 21:29:24,384 INFO supervisord started with pid 7
2023-05-09 21:29:25,386 INFO spawned: 'start-script' with pid 211
2023-05-09 21:29:25,387 INFO spawned: 'watchdog-script' with pid 212
2023-05-09 21:29:25,388 INFO reaped unknown pid 8 (exit status 0)
2023-05-09 21:29:25,391 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2023-05-09 21:29:25,391 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2023-05-09 21:29:25,391 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2023-05-09 21:29:25,393 DEBG 'watchdog-script' stdout output:
[info] qBittorrent config file already exists, skipping copy
[info] Removing session lock file (if it exists)...

2023-05-09 21:29:25,419 DEBG 'start-script' stdout output:
[debug] Contents of ovpn file /config/openvpn/config.ovpn as follows...

2023-05-09 21:29:25,420 DEBG 'start-script' stdout output:
client
dev tun
proto udp
remote xxx.xxx.xxx.xxx xxx
resolv-retry infinite
remote-random
nobind
tun-mtu 1500
tun-mtu-extra 32
mssfix 1450
persist-key
ping 15
ping-restart 0
ping-timer-rem
comp-lzo no
verify-x509-name CN=openvpn

remote-cert-tls server

auth-user-pass credentials.conf
verb 3
pull
fast-io
cipher AES-256-CBC
auth SHA512
<ca>
-----BEGIN CERTIFICATE-----
xxxxx
-----END CERTIFICATE-----
</ca>
key-direction 1
<tls-auth>
#
# 2048 bit OpenVPN static key
#
-----BEGIN OpenVPN Static key V1-----
xxxxx
-----END OpenVPN Static key V1-----
</tls-auth>

2023-05-09 21:29:25,425 DEBG 'start-script' stdout output:
[debug] Environment variables defined as follows
ADDITIONAL_PORTS=
APPLICATION=qbittorrent
BASH=/bin/bash
BASHOPTS=checkwinsize:cmdhist:complete_fullquote:extquote:force_fignore:globasciiranges:hostcomplete:interactive_comments:progcomp:promptvars:sourcepath
BASH_ALIASES=()
BASH_ARGC=()
BASH_ARGV=()
BASH_CMDS=()
BASH_LINENO=([0]="0")
BASH_SOURCE=([0]="/root/start.sh")
BASH_VERSINFO=([0]="5" [1]="1" [2]="16" [3]="1" [4]="release" [5]="x86_64-pc-linux-gnu")
BASH_VERSION='5.1.16(1)-release'
DEBUG=true
DIRSTACK=()
ENABLE_PRIVOXY=no
EUID=0
GROUPS=()
HOME=/home/nobody
HOSTNAME=165c90e2816b
HOSTTYPE=x86_64
IFS=$' \t\n'
LANG=en_GB.UTF-8
LAN_NETWORK=192.168.1.0/24
MACHTYPE=x86_64-pc-linux-gnu
NAME_SERVERS=xx.xxx.xx.xx,xx.xxx.x.xxx,x.x.x.x,xx.xxx.xxx.xxx,xx.xxx.xx.xx,x.x.x.x

2023-05-09 21:29:25,425 DEBG 'start-script' stdout output:
OPTERR=1
OPTIND=1
OSTYPE=linux-gnu
OS_ARCH=x86-64
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
PGID=1006
PIPESTATUS=([0]="0")
PPID=7
PS4='+ '
PUID=1005
PWD=/
SHELL=/bin/bash
SHELLOPTS=braceexpand:hashall:interactive-comments
SHLVL=1
SUPERVISOR_ENABLED=1
SUPERVISOR_GROUP_NAME=start-script
SUPERVISOR_PROCESS_NAME=start-script
TERM=xterm
UID=0
VPN_CLIENT=openvpn
VPN_CONFIG=/config/openvpn/configdp.ovpn
VPN_DEVICE_TYPE=tun0
VPN_ENABLED=yes
VPN_INPUT_PORTS=
VPN_OPTIONS=
VPN_OUTPUT_PORTS=
VPN_PASS=
VPN_PROV=custom
VPN_REMOTE_PORT=1194,
VPN_REMOTE_PROTOCOL=udp,
VPN_REMOTE_SERVER=xxx.xxx.xxx.xxx,
VPN_USER=
VPN_USER_FILE=/run/secrets/qbittorrent_vpn_password
WEBUI_PORT=8080
_='[debug] Environment variables defined as follows'
vpn_ping='ping 15'
[debug] Directory listing of files in /config/openvpn/ as follows

2023-05-09 21:29:25,428 DEBG 'start-script' stdout output:
total 16
drwxrwxr-x 2 nobody users 4096 May  9 21:29 .
drwxrwx--- 4 nobody users 4096 May  9 21:29 ..
-rwxrwxr-x 1 nobody users   50 Apr 28 20:48 credentials.conf
-rwxrwxr-x 1 nobody users 2841 May  9 21:29 config.ovpn

2023-05-09 21:29:25,428 DEBG 'start-script' stdout output:
[debug] Contents of OpenVPN config file '/config/openvpn/config.ovpn' as follows...

2023-05-09 21:29:25,429 DEBG 'start-script' stdout output:
client
dev tun
proto udp
remote xxx.xxx.xxx.xxx xxxx
resolv-retry infinite
remote-random
nobind
tun-mtu 1500
tun-mtu-extra 32
mssfix 1450
persist-key
ping 15
ping-restart 0
ping-timer-rem
comp-lzo no
verify-x509-name CN=config.com

remote-cert-tls server

auth-user-pass credentials.conf
verb 3
pull
fast-io
cipher AES-256-CBC
auth SHA512
<ca>
-----BEGIN CERTIFICATE-----
xxxxx
-----END CERTIFICATE-----
</ca>
key-direction 1
<tls-auth>
#
# 2048 bit OpenVPN static key
#
-----BEGIN OpenVPN Static key V1-----
xxxxx
-----END OpenVPN Static key V1-----
</tls-auth>

2023-05-09 21:29:25,432 DEBG 'start-script' stdout output:
[info] Adding xxx.xxx.xxx.xxx to /etc/resolv.conf

2023-05-09 21:29:25,434 DEBG 'start-script' stdout output:
[info] Adding xxx.xxx.xxx.xxx to /etc/resolv.conf

2023-05-09 21:29:25,439 DEBG 'start-script' stdout output:
[info] Adding xxx.xxx.xxx.xxx to /etc/resolv.conf

2023-05-09 21:29:25,443 DEBG 'start-script' stdout output:
[info] Adding xxx.xxx.xxx.xxx to /etc/resolv.conf

2023-05-09 21:29:25,446 DEBG 'start-script' stdout output:
[info] Adding xxx.xxx.xxx.xxx to /etc/resolv.conf

2023-05-09 21:29:25,450 DEBG 'start-script' stdout output:
[info] Adding xxx.xxx.xxx.xxx to /etc/resolv.conf

2023-05-09 21:29:25,467 DEBG 'start-script' stdout output:
[info] Attempting to load iptable_mangle module...

2023-05-09 21:29:25,468 DEBG 'start-script' stderr output:
modprobe: FATAL: Module iptable_mangle not found in directory /lib/modules/5.15.0-67-generic

2023-05-09 21:29:25,468 DEBG 'start-script' stdout output:
[warn] Unable to load iptable_mangle module using modprobe, trying insmod...

2023-05-09 21:29:25,469 DEBG 'start-script' stderr output:
insmod: ERROR: could not load module /lib/modules/iptable_mangle.ko: No such file or directory

2023-05-09 21:29:25,469 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

2023-05-09 21:29:25,469 DEBG 'start-script' stdout output:
[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'
[debug] Show name servers defined for container

2023-05-09 21:29:25,470 DEBG 'start-script' stdout output:
nameserver xxx.xxx.xxx.xxx
nameserver xxx.xxx.xxx.xxx
nameserver xxx.xxx.xxx.xxx
nameserver xxx.xxx.xxx.xxx
nameserver xxx.xxx.xxx.xxx
nameserver xxx.xxx.xxx.xxx

2023-05-09 21:29:25,470 DEBG 'start-script' stdout output:
[debug] Show contents of hosts file

2023-05-09 21:29:25,470 DEBG 'start-script' stdout output:
127.0.0.1	localhost
::1	localhost ip6-localhost ip6-loopback
fe00::0	ip6-localnet
ff00::0	ip6-mcastprefix
ff02::1	ip6-allnodes
ff02::2	ip6-allrouters
192.168.128.2	165c90e2816b
192.168.240.2	165c90e2816b
192.168.192.3	165c90e2816b

2023-05-09 21:29:25,478 DEBG 'start-script' stdout output:
[debug] Docker interface defined as eth0

2023-05-09 21:29:25,482 DEBG 'start-script' stdout output:
[info] Default route for container is 192.168.128.1

2023-05-09 21:29:25,485 DEBG 'start-script' stdout output:
[debug] Docker IP defined as 192.168.128.2

2023-05-09 21:29:25,488 DEBG 'start-script' stdout output:
[debug] Docker netmask defined as 255.255.240.0

2023-05-09 21:29:25,597 DEBG 'start-script' stdout output:
[info] Docker network defined as    192.168.128.0/20

2023-05-09 21:29:25,600 DEBG 'start-script' stdout output:
[info] Adding 192.168.1.0/24 as route via docker eth0

2023-05-09 21:29:25,601 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2023-05-09 21:29:25,602 DEBG 'start-script' stdout output:
default via 192.168.128.1 dev eth0 
192.168.1.0/24 via 192.168.128.1 dev eth0 
192.168.128.0/20 dev eth0 proto kernel scope link src 192.168.128.2 
192.168.192.0/20 dev eth2 proto kernel scope link src 192.168.192.3 

2023-05-09 21:29:25,602 DEBG 'start-script' stdout output:
192.168.240.0/20 dev eth1 proto kernel scope link src 192.168.240.2 
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 
local 192.168.128.2 dev eth0 table local proto kernel scope host src 192.168.128.2 
broadcast 192.168.143.255 dev eth0 table local proto kernel scope link src 192.168.128.2 
local 192.168.192.3 dev eth2 table local proto kernel scope host src 192.168.192.3 
broadcast 192.168.207.255 dev eth2 table local proto kernel scope link src 192.168.192.3 
local 192.168.240.2 dev eth1 table local proto kernel scope host src 192.168.240.2 
broadcast 192.168.255.255 dev eth1 table local proto kernel scope link src 192.168.240.2 

2023-05-09 21:29:25,602 DEBG 'start-script' stdout output:
--------------------

2023-05-09 21:29:25,602 DEBG 'start-script' stdout output:
[debug] Modules currently loaded for kernel

2023-05-09 21:29:25,605 DEBG 'start-script' stdout output:
Module                  Size  Used by
ip6table_filter        16384  0
cpuid                  16384  0
iptable_nat            16384  0
iptable_filter         16384  2
bpfilter               16384  0
wireguard              94208  0
curve25519_x86_64      36864  1 wireguard
libchacha20poly1305    16384  1 wireguard
chacha_x86_64          28672  1 libchacha20poly1305
poly1305_x86_64        28672  1 libchacha20poly1305
libcurve25519_generic    49152  2 curve25519_x86_64,wireguard
libchacha              16384  1 chacha_x86_64
ip6_udp_tunnel         16384  1 wireguard
udp_tunnel             20480  1 wireguard
tcp_diag               16384  0
udp_diag               16384  0
inet_diag              24576  2 tcp_diag,udp_diag
tls                   114688  0
xt_recent              24576  0
bluetooth             704512  0
ecdh_generic           16384  1 bluetooth
ecc                    36864  1 ecdh_generic
xt_nat                 16384  66
veth                   32768  0
nft_chain_nat          16384  33
xt_MASQUERADE          20480  25
nf_nat                 49152  4 xt_nat,nft_chain_nat,iptable_nat,xt_MASQUERADE
nf_conntrack_netlink    49152  0
xfrm_user              40960  1
xfrm_algo              16384  1 xfrm_user
br_netfilter           32768  0
bridge                307200  1 br_netfilter
stp                    16384  1 bridge
llc                    16384  2 bridge,stp
overlay               151552  14
ip6t_REJECT            16384  1
nf_reject_ipv6         20480  1 ip6t_REJECT
xt_hl                  16384  22
ip6_tables             32768  53 ip6table_filter
ip6t_rt                20480  3
ipt_REJECT             16384  1
nf_reject_ipv4         16384  1 ipt_REJECT
xt_multiport           20480  2
xt_LOG                 20480  11
nf_log_syslog          20480  11
nft_limit              16384  14
xt_limit               16384  0
xt_addrtype            16384  6
xt_tcpudp              20480  127
xt_conntrack           16384  35
nf_conntrack          172032  5 xt_conntrack,nf_nat,xt_nat,nf_conntrack_netlink,xt_MASQUERADE
nf_defrag_ipv6         24576  1 nf_conntrack
nf_defrag_ipv4         16384  1 nf_conntrack
nft_compat             20480  355
nft_counter            16384  472
binfmt_misc            24576  1
nf_tables             249856  1563 nft_compat,nft_counter,nft_chain_nat,nft_limit
nfnetlink              20480  4 nft_compat,nf_conntrack_netlink,nf_tables
intel_rapl_msr         20480  0
intel_rapl_common      40960  1 intel_rapl_msr
snd_hda_codec_hdmi     77824  1
intel_tcc_cooling      16384  0
x86_pkg_temp_thermal    20480  0
intel_powerclamp       20480  0
snd_hda_codec_realtek   159744  1
coretemp               24576  0
snd_hda_codec_generic   102400  1 snd_hda_codec_realtek
ledtrig_audio          16384  1 snd_hda_codec_generic
kvm_intel             368640  0
kvm                  1028096  1 kvm_intel
snd_hda_intel          53248  0
snd_intel_dspcfg       28672  1 snd_hda_intel
snd_intel_sdw_acpi     20480  1 snd_intel_dspcfg
snd_hda_codec         163840  4 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek
snd_hda_core          110592  5 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek
mei_hdcp               24576  0
rapl                   20480  0
snd_hwdep              16384  1 snd_hda_codec
snd_pcm               143360  4 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_core
intel_cstate           20480  0
snd_timer              40960  1 snd_pcm
snd                   106496  8 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_pcm
mei_me                 40960  1
wmi_bmof               16384  0
gigabyte_wmi           20480  0
ee1004                 20480  0
mei                   135168  3 mei_hdcp,mei_me
soundcore              16384  1 snd
mac_hid                16384  0
acpi_pad              184320  0
acpi_tad               20480  0
sch_fq_codel           20480  2
dm_multipath           40960  0
scsi_dh_rdac           20480  0
scsi_dh_emc            16384  0
scsi_dh_alua           20480  0
msr
2023-05-09 21:29:25,606 DEBG 'start-script' stdout output:
                    16384  0
ramoops                32768  0
pstore_blk             16384  0
pstore_zone            32768  1 pstore_blk
reed_solomon           28672  1 ramoops
efi_pstore             16384  0
ip_tables              32768  12 iptable_filter,iptable_nat
x_tables               53248  19 ip6table_filter,xt_conntrack,iptable_filter,nft_compat,xt_LOG,xt_multiport,xt_tcpudp,xt_addrtype,xt_recent,xt_nat,ip6t_rt,ip6_tables,ipt_REJECT,ip_tables,iptable_nat,xt_limit,xt_hl,xt_MASQUERADE,ip6t_REJECT
autofs4                49152  2
btrfs                1560576  0
blake2b_generic        20480  0
zstd_compress         229376  1 btrfs
raid10                 69632  0
raid456               163840  0
async_raid6_recov      24576  1 raid456
async_memcpy           20480  2 raid456,async_raid6_recov
async_pq               24576  2 raid456,async_raid6_recov
async_xor              20480  3 async_pq,raid456,async_raid6_recov
async_tx               20480  5 async_pq,async_memcpy,async_xor,raid456,async_raid6_recov
xor                    24576  2 async_xor,btrfs
raid6_pq              122880  4 async_pq,btrfs,raid456,async_raid6_recov
libcrc32c              16384  5 nf_conntrack,nf_nat,btrfs,nf_tables,raid456
raid0                  24576  0
multipath              20480  0
linear                 20480  0
raid1                  49152  1
i915                 3104768  1
i2c_algo_bit           16384  1 i915
ttm                    86016  1 i915
drm_kms_helper        311296  1 i915
syscopyarea            16384  1 drm_kms_helper
sysfillrect            20480  1 drm_kms_helper
sysimgblt              16384  1 drm_kms_helper
fb_sys_fops            16384  1 drm_kms_helper
cec                    61440  2 drm_kms_helper,i915
crct10dif_pclmul       16384  1
crc32_pclmul           16384  0
ghash_clmulni_intel    16384  0
aesni_intel           376832  0
rc_core                65536  1 cec
crypto_simd            16384  1 aesni_intel
r8169                 102400  0
nvme                   49152  1
cryptd                 24576  2 crypto_simd,ghash_clmulni_intel
realtek                32768  1
drm                   622592  4 drm_kms_helper,i915,ttm
xhci_pci               24576  0
ahci                   45056  2
i2c_i801               36864  0
nvme_core             135168  2 nvme
i2c_smbus              20480  1 i2c_i801
libahci                45056  1 ahci
xhci_pci_renesas       20480  1 xhci_pci
wmi                    32768  2 gigabyte_wmi,wmi_bmof
video                  65536  1 i915

2023-05-09 21:29:25,628 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2023-05-09 21:29:25,629 DEBG 'start-script' stdout output:
-P INPUT DROP
-P FORWARD DROP
-P OUTPUT DROP
-A INPUT -s xxx.xxx.xxx.xxx/32 -i eth0 -j ACCEPT
-A INPUT -s 192.168.128.0/20 -d 192.168.128.0/20 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 8080 -j ACCEPT
-A INPUT -i eth0 -p udp -m udp --dport 8080 -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 -d xxx.xxx.xxx.xxx/32 -o eth0 -j ACCEPT
-A OUTPUT -s 192.168.128.0/20 -d 192.168.128.0/20 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 8080 -j ACCEPT
-A OUTPUT -o eth0 -p udp -m udp --sport 8080 -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-05-09 21:29:25,630 DEBG 'start-script' stdout output:
--------------------

2023-05-09 21:29:25,630 DEBG 'start-script' stdout output:
[debug] VPN remote configuration options as follows...
[debug] VPN remote server is defined as 'xxx.xxx.xxx.xxx'
[debug] VPN remote port is defined as '1194'

2023-05-09 21:29:25,630 DEBG 'start-script' stdout output:
[debug] VPN remote protocol is defined as 'udp'
[debug] VPN remote ip is defined as ''

2023-05-09 21:29:25,630 DEBG 'start-script' stdout output:
[debug] OpenVPN command line:- /usr/bin/openvpn --reneg-sec 0 --mute-replay-warnings --auth-nocache --setenv VPN_PROV 'custom' --setenv VPN_CLIENT 'openvpn' --setenv DEBUG 'true' --setenv VPN_DEVICE_TYPE 'tun0' --setenv VPN_ENABLED 'yes' --setenv VPN_REMOTE_SERVER 'xxx.xxx.xxx.xxx' --setenv APPLICATION 'qbittorrent' --script-security 2 --writepid /root/openvpn.pid --remap-usr1 SIGHUP --log-append /dev/stdout --pull-filter ignore 'up' --pull-filter ignore 'down' --pull-filter ignore 'route-ipv6' --pull-filter ignore 'ifconfig-ipv6' --pull-filter ignore 'tun-ipv6' --pull-filter ignore 'dhcp-option DNS6' --pull-filter ignore 'persist-tun' --pull-filter ignore 'reneg-sec' --up /root/openvpnup.sh --up-delay --up-restart --cd /config/openvpn --config '/config/openvpn/config.ovpn'
[info] Starting OpenVPN (non daemonised)...

2023-05-09 21:29:25,636 DEBG 'start-script' stdout output:
2023-05-09 21:29:25 DEPRECATED OPTION: --cipher set to 'AES-256-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305). OpenVPN ignores --cipher for cipher negotiations. 
2023-05-09 21:29:25 Note: '--allow-compression' is not set to 'no', disabling data channel offload.
2023-05-09 21:29:25 WARNING: file 'credentials.conf' is group or others accessible
2023-05-09 21:29:25 OpenVPN 2.6.2 [git:makepkg/3577442530eb7830+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] [DCO] built on Mar 24 2023
2023-05-09 21:29:25 library versions: OpenSSL 3.0.8 7 Feb 2023, LZO 2.10
2023-05-09 21:29:25 DCO version: N/A

2023-05-09 21:29:25,636 DEBG 'start-script' stdout output:
2023-05-09 21:29:25 WARNING: --ping should normally be used with --ping-restart or --ping-exit

2023-05-09 21:29:25,636 DEBG 'start-script' stdout output:
2023-05-09 21:29:25 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2023-05-09 21:29:25,638 DEBG 'start-script' stdout output:
2023-05-09 21:29:25 TCP/UDP: Preserving recently used remote address: [AF_INET]xxx.xxx.xxx.xxx:1194

2023-05-09 21:29:25,638 DEBG 'start-script' stdout output:
2023-05-09 21:29:25 Socket Buffers: R=[212992->212992] S=[212992->212992]
2023-05-09 21:29:25 UDPv4 link local: (not bound)
2023-05-09 21:29:25 UDPv4 link remote: [AF_INET]xxx.xxx.xxx.xxx:1194

2023-05-09 21:29:25,647 DEBG 'start-script' stdout output:
2023-05-09 21:29:25 TLS: Initial packet from [AF_INET]xxx.xxx.xxx.xxx:1194, sid=f61734be 3c78a3e3

2023-05-09 21:29:25,697 DEBG 'start-script' stdout output:
2023-05-09 21:29:25 VERIFY OK: depth=2, C=PA, O=VPN, CN=VPN Root CA

2023-05-09 21:29:25,697 DEBG 'start-script' stdout output:
2023-05-09 21:29:25 VERIFY OK: depth=1, O=VPN, CN=VPN CA8

2023-05-09 21:29:25,697 DEBG 'start-script' stdout output:
2023-05-09 21:29:25 VERIFY KU OK
2023-05-09 21:29:25 Validating certificate extended key usage
2023-05-09 21:29:25 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
2023-05-09 21:29:25 VERIFY EKU OK
2023-05-09 21:29:25 VERIFY X509NAME OK: CN=vpn
2023-05-09 21:29:25 VERIFY OK: depth=0, CN=vpn

2023-05-09 21:29:25,707 DEBG 'start-script' stdout output:
2023-05-09 21:29:25 Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, peer certificate: 4096 bit RSA, signature: RSA-SHA512
2023-05-09 21:29:25 [vpn] Peer Connection Initiated with [AF_INET]xxx.xxx.xxx.xxx:1194
2023-05-09 21:29:25 TLS: move_session: dest=TM_ACTIVE src=TM_INITIAL reinit_src=1
2023-05-09 21:29:25 TLS: tls_multi_process: initial untrusted session promoted to trusted

2023-05-09 21:29:26,708 DEBG 'start-script' stdout output:
2023-05-09 21:29:26 SENT CONTROL [vpn]: 'PUSH_REQUEST' (status=1)

2023-05-09 21:29:26,716 DEBG 'start-script' stdout output:
2023-05-09 21:29:26 PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1,dhcp-option DNS xxx.xxx.xxx.xxx,dhcp-option DNS xxx.xxx.xxx.xxx,explicit-exit-notify,comp-lzo no,route-gateway xxx.xxx.xxx.xxx,topology subnet,ping 60,ping-restart 180,ifconfig xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx,peer-id 8,cipher AES-256-GCM'
2023-05-09 21:29:26 OPTIONS IMPORT: --ifconfig/up options modified
2023-05-09 21:29:26 OPTIONS IMPORT: route options modified
2023-05-09 21:29:26 OPTIONS IMPORT: route-related options modified

2023-05-09 21:29:26,717 DEBG 'start-script' stdout output:
2023-05-09 21:29:26 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
2023-05-09 21:29:26 net_route_v4_best_gw query: dst xxx.xxx.xxx.xxx
2023-05-09 21:29:26 net_route_v4_best_gw result: via 192.168.128.1 dev eth0
2023-05-09 21:29:26 ROUTE_GATEWAY 192.168.128.1/xxx.xxx.xxx.xxx IFACE=eth0 HWADDR=02:42:c0:a8:80:02

2023-05-09 21:29:26,717 DEBG 'start-script' stdout output:
2023-05-09 21:29:26 TUN/TAP device tun0 opened
2023-05-09 21:29:26 net_iface_mtu_set: mtu 1500 for tun0

2023-05-09 21:29:26,717 DEBG 'start-script' stdout output:
2023-05-09 21:29:26 net_iface_up: set tun0 up
2023-05-09 21:29:26 net_addr_v4_add: xxx.xxx.xxx.xxx/24 dev tun0

2023-05-09 21:29:26,717 DEBG 'start-script' stdout output:
2023-05-09 21:29:26 /root/openvpnup.sh tun0 1500 0 xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx init

2023-05-09 21:29:26,718 DEBG 'start-script' stdout output:
2023-05-09 21:29:26 net_route_v4_add: xxx.xxx.xxx.xxx/32 via 192.168.128.1 dev [NULL] table 0 metric -1

2023-05-09 21:29:26,719 DEBG 'start-script' stdout output:
2023-05-09 21:29:26 net_route_v4_add: 0.0.0.0/1 via xxx.xxx.xxx.xxx dev [NULL] table 0 metric -1
2023-05-09 21:29:26 net_route_v4_add: xxx.xxx.xxx.xxx/1 via xxx.xxx.xxx.xxx dev [NULL] table 0 metric -1

2023-05-09 21:29:26,719 DEBG 'start-script' stdout output:
2023-05-09 21:29:26 Initialization Sequence Completed
2023-05-09 21:29:26 Data Channel: cipher 'AES-256-GCM', peer-id: 8, compression: 'stub'
2023-05-09 21:29:26 Timers: ping 60, ping-restart 180
2023-05-09 21:29:26 Protocol options: explicit-exit-notify 1

2023-05-09 21:29:26,719 DEBG 'start-script' stdout output:
[debug] Waiting for valid local and gateway IP addresses from tunnel...

2023-05-09 21:29:27,726 DEBG 'start-script' stdout output:
[debug] Valid local IP address from tunnel acquired 'xxx.xxx.xxx.xxx'

2023-05-09 21:29:27,726 DEBG 'start-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2023-05-09 21:29:27,728 DEBG 'watchdog-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2023-05-09 21:29:27,741 DEBG 'start-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com' to address 'xxx.xxx.xxx.xxx'

2023-05-09 21:29:27,741 DEBG 'start-script' stdout output:
[info] Attempting to get external IP using 'http://checkip.amazonaws.com'...

2023-05-09 21:29:27,741 DEBG 'watchdog-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com' to address 'xxx.xxx.xxx.xxx'

2023-05-09 21:29:27,819 DEBG 'start-script' stdout output:
[info] Successfully retrieved external IP address xxx.xxx.xxx.xxx

2023-05-09 21:29:27,820 DEBG 'start-script' stdout output:
[info] Application does not require port forwarding or VPN provider is != pia, skipping incoming port assignment

2023-05-09 21:29:27,843 DEBG 'watchdog-script' stdout output:
[debug] Waiting for iptables chain policies to be in place...

2023-05-09 21:29:27,848 DEBG 'watchdog-script' stdout output:
[debug] iptables chain policies are in place
[info] qBittorrent listening interface IP 0.0.0.0 and VPN provider IP xxx.xxx.xxx.xxx different, marking for reconfigure

2023-05-09 21:29:27,851 DEBG 'watchdog-script' stdout output:
[info] qBittorrent not running

2023-05-09 21:29:27,851 DEBG 'watchdog-script' stdout output:
[info] Removing session lock file (if it exists)...

2023-05-09 21:29:27,855 DEBG 'watchdog-script' stdout output:
[info] Attempting to start qBittorrent...

2023-05-09 21:29:27,865 DEBG 'watchdog-script' stdout output:
[info] qBittorrent process started
[info] Waiting for qBittorrent process to start listening on port 8080...

2023-05-09 21:29:27,971 DEBG 'watchdog-script' stdout output:
[info] qBittorrent process listening on port 8080

2023-05-09 21:29:27,971 DEBG 'watchdog-script' stdout output:
[debug] VPN IP is xxx.xxx.xxx.xxx
[debug] qBittorrent IP is xxx.xxx.xxx.xxx

2023-05-09 21:29:57,984 DEBG 'watchdog-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2023-05-09 21:30:13,031 DEBG 'watchdog-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com' to address 'xxx.xxx.xxx.xxx'

2023-05-09 21:30:13,031 DEBG 'watchdog-script' stdout output:
[debug] Waiting for iptables chain policies to be in place...

2023-05-09 21:30:13,038 DEBG 'watchdog-script' stdout output:
[debug] iptables chain policies are in place

2023-05-09 21:30:13,040 DEBG 'watchdog-script' stdout output:
[debug] VPN IP is xxx.xxx.xxx.xxx
[debug] qBittorrent IP is xxx.xxx.xxx.xxx

2023-05-09 21:30:43,055 DEBG 'watchdog-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2023-05-09 21:30:43,096 DEBG 'watchdog-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com' to address 'xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx'

2023-05-09 21:30:43,097 DEBG 'watchdog-script' stdout output:
[debug] Waiting for iptables chain policies to be in place...

2023-05-09 21:30:43,105 DEBG 'watchdog-script' stdout output:
[debug] iptables chain policies are in place

2023-05-09 21:30:43,108 DEBG 'watchdog-script' stdout output:
[debug] VPN IP is xxx.xxx.xxx.xxx
[debug] qBittorrent IP is xxx.xxx.xxx.xxx

2023-05-09 21:31:13,112 DEBG 'watchdog-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2023-05-09 21:31:13,135 DEBG 'watchdog-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com' to address 'xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx'

2023-05-09 21:31:13,136 DEBG 'watchdog-script' stdout output:
[debug] Waiting for iptables chain policies to be in place...

2023-05-09 21:31:13,142 DEBG 'watchdog-script' stdout output:
[debug] iptables chain policies are in place

2023-05-09 21:31:13,146 DEBG 'watchdog-script' stdout output:
[debug] VPN IP is xxx.xxx.xxx.xxx
[debug] qBittorrent IP is xxx.xxx.xxx.xxx

2023-05-09 21:31:43,152 DEBG 'watchdog-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2023-05-09 21:31:43,171 DEBG 'watchdog-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com' to address 'xxx.xxx.xxx.xxx'

2023-05-09 21:31:43,172 DEBG 'watchdog-script' stdout output:
[debug] Waiting for iptables chain policies to be in place...

2023-05-09 21:31:43,184 DEBG 'watchdog-script' stdout output:
[debug] iptables chain policies are in place

2023-05-09 21:31:43,190 DEBG 'watchdog-script' stdout output:
[debug] VPN IP is xxx.xxx.xxx.xxx
[debug] qBittorrent IP is xxx.xxx.xxx.xxx

2023-05-09 21:32:13,195 DEBG 'watchdog-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2023-05-09 21:32:13,221 DEBG 'watchdog-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com' to address 'xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx'

2023-05-09 21:32:13,222 DEBG 'watchdog-script' stdout output:
[debug] Waiting for iptables chain policies to be in place...

2023-05-09 21:32:13,231 DEBG 'watchdog-script' stdout output:
[debug] iptables chain policies are in place

2023-05-09 21:32:13,236 DEBG 'watchdog-script' stdout output:
[debug] VPN IP is xxx.xxx.xxx.xxx
[debug] qBittorrent IP is xxx.xxx.xxx.xxx

2023-05-09 21:32:43,240 DEBG 'watchdog-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2023-05-09 21:32:58,267 DEBG 'watchdog-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com' to address 'xxx.xxx.xxx.xxx'

2023-05-09 21:32:58,267 DEBG 'watchdog-script' stdout output:
[debug] Waiting for iptables chain policies to be in place...

2023-05-09 21:32:58,274 DEBG 'watchdog-script' stdout output:
[debug] iptables chain policies are in place

2023-05-09 21:32:58,277 DEBG 'watchdog-script' stdout output:
[debug] VPN IP is xxx.xxx.xxx.xxx
[debug] qBittorrent IP is xxx.xxx.xxx.xxx

2023-05-09 21:33:28,282 DEBG 'watchdog-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2023-05-09 21:33:28,323 DEBG 'watchdog-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com' to address 'xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx'

2023-05-09 21:33:28,323 DEBG 'watchdog-script' stdout output:
[debug] Waiting for iptables chain policies to be in place...

2023-05-09 21:33:28,332 DEBG 'watchdog-script' stdout output:
[debug] iptables chain policies are in place

2023-05-09 21:33:28,336 DEBG 'watchdog-script' stdout output:
[debug] VPN IP is xxx.xxx.xxx.xxx
[debug] qBittorrent IP is xxx.xxx.xxx.xxx

2023-05-09 21:33:58,340 DEBG 'watchdog-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2023-05-09 21:34:13,366 DEBG 'watchdog-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com' to address 'xxx.xxx.xxx.xxx'

2023-05-09 21:34:13,368 DEBG 'watchdog-script' stdout output:
[debug] Waiting for iptables chain policies to be in place...

2023-05-09 21:34:13,383 DEBG 'watchdog-script' stdout output:
[debug] iptables chain policies are in place

2023-05-09 21:34:13,389 DEBG 'watchdog-script' stdout output:
[debug] VPN IP is xxx.xxx.xxx.xxx
[debug] qBittorrent IP is xxx.xxx.xxx.xxx

2023-05-09 21:34:43,392 DEBG 'watchdog-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2023-05-09 21:34:43,407 DEBG 'watchdog-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com' to address 'xxx.xxx.xxx.xxx'

2023-05-09 21:34:43,407 DEBG 'watchdog-script' stdout output:
[debug] Waiting for iptables chain policies to be in place...

2023-05-09 21:34:43,413 DEBG 'watchdog-script' stdout output:
[debug] iptables chain policies are in place

2023-05-09 21:34:43,416 DEBG 'watchdog-script' stdout output:
[debug] VPN IP is xxx.xxx.xxx.xxx
[debug] qBittorrent IP is xxx.xxx.xxx.xxx

2023-05-09 21:35:13,424 DEBG 'watchdog-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2023-05-09 21:35:28,459 DEBG 'watchdog-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com' to address 'xxx.xxx.xxx.xxx'

2023-05-09 21:35:28,460 DEBG 'watchdog-script' stdout output:
[debug] Waiting for iptables chain policies to be in place...

2023-05-09 21:35:28,467 DEBG 'watchdog-script' stdout output:
[debug] iptables chain policies are in place

2023-05-09 21:35:28,470 DEBG 'watchdog-script' stdout output:
[debug] VPN IP is xxx.xxx.xxx.xxx
[debug] qBittorrent IP is xxx.xxx.xxx.xxx

2023-05-09 21:35:58,475 DEBG 'watchdog-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2023-05-09 21:35:58,489 DEBG 'watchdog-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com' to address 'xxx.xxx.xxx.xxx'

2023-05-09 21:35:58,489 DEBG 'watchdog-script' stdout output:
[debug] Waiting for iptables chain policies to be in place...

2023-05-09 21:35:58,497 DEBG 'watchdog-script' stdout output:
[debug] iptables chain policies are in place

2023-05-09 21:35:58,501 DEBG 'watchdog-script' stdout output:
[debug] VPN IP is xxx.xxx.xxx.xxx
[debug] qBittorrent IP is xxx.xxx.xxx.xxx

2023-05-09 21:36:28,504 DEBG 'watchdog-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2023-05-09 21:36:28,517 DEBG 'watchdog-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com' to address 'xxx.xxx.xxx.xxx'

2023-05-09 21:36:28,517 DEBG 'watchdog-script' stdout output:
[debug] Waiting for iptables chain policies to be in place...

2023-05-09 21:36:28,524 DEBG 'watchdog-script' stdout output:
[debug] iptables chain policies are in place

2023-05-09 21:36:28,527 DEBG 'watchdog-script' stdout output:
[debug] VPN IP is xxx.xxx.xxx.xxx
[debug] qBittorrent IP is xxx.xxx.xxx.xxx

2023-05-09 21:37:43,570 DEBG 'watchdog-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2023-05-09 21:37:43,593 DEBG 'watchdog-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com' to address 'xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx'

2023-05-09 21:37:43,594 DEBG 'watchdog-script' stdout output:
[debug] Waiting for iptables chain policies to be in place...

2023-05-09 21:37:43,604 DEBG 'watchdog-script' stdout output:
[debug] iptables chain policies are in place

2023-05-09 21:37:43,608 DEBG 'watchdog-script' stdout output:
[debug] VPN IP is xxx.xxx.xxx.xxx
[debug] qBittorrent IP is xxx.xxx.xxx.xxx

2023-05-09 21:39:43,730 DEBG 'watchdog-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2023-05-09 21:41:13,826 DEBG 'watchdog-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2023-05-09 21:41:13,855 DEBG 'watchdog-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com' to address 'xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx'

2023-05-09 21:41:13,856 DEBG 'watchdog-script' stdout output:
[debug] Waiting for iptables chain policies to be in place...

2023-05-09 21:41:13,862 DEBG 'watchdog-script' stdout output:
[debug] iptables chain policies are in place

2023-05-09 21:41:13,865 DEBG 'watchdog-script' stdout output:
[debug] VPN IP is xxx.xxx.xxx.xxx
[debug] qBittorrent IP is xxx.xxx.xxx.xxx

2023-05-09 21:41:24,877 WARN received SIGTERM indicating exit request
2023-05-09 21:41:24,877 DEBG killing watchdog-script (pid 212) with signal SIGTERM
2023-05-09 21:41:24,877 INFO waiting for start-script, watchdog-script to die
2023-05-09 21:41:24,877 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 139820704260992 for <Subprocess at 139820704256624 with name watchdog-script in state STOPPING> (stdout)>
2023-05-09 21:41:24,877 DEBG fd 15 closed, stopped monitoring <POutputDispatcher at 139820704261040 for <Subprocess at 139820704256624 with name watchdog-script in state STOPPING> (stderr)>
2023-05-09 21:41:24,878 WARN stopped: watchdog-script (exit status 143)
2023-05-09 21:41:24,878 DEBG received SIGCHLD indicating a child quit
2023-05-09 21:41:24,878 DEBG killing start-script (pid 211) with signal SIGTERM
2023-05-09 21:41:25,879 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 139820704259936 for <Subprocess at 139820704255760 with name start-script in state STOPPING> (stdout)>
2023-05-09 21:41:25,879 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 139820704253264 for <Subprocess at 139820704255760 with name start-script in state STOPPING> (stderr)>
2023-05-09 21:41:25,879 WARN stopped: start-script (terminated by SIGTERM)
2023-05-09 21:41:25,879 DEBG received SIGCHLD indicating a child quit

 

Link to comment

Somehow it seems that via PIA my Wireguard configuration is not properly obtained. The Address and Public Key is missing in the config file when obtained and therefore the Wireguard instance fails to connect properly. Erroring out on those lines missing.

Address =
PrivateKey = *************************************
PostUp = '/root/wireguardup.sh'
PostDown = '/root/wireguarddown.sh'

[Peer]
PublicKey =
AllowedIPs = 0.0.0.0/0
Endpoint = ************************************

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.