[Support] binhex - qBittorrentVPN


binhex

Recommended Posts

I am having an issue where if my unraid server improperly shuts off or resets, the qbittorrent settings revert back to default. Not the docker config, but the in application settings. I've set the qbittorrent.conf file to read only by all users/grps, but it still reverts to default. Anyone experience this and found a solution? Thanks.

Link to comment

Hey, got everything working. The only Problem I have is that the container keeps reconnecting.

Iam on Unraid with a custom setup.

That is quite disturbing because the torrents wont get quite to speed.

Testet deluge aswell there it seems to be working.

After every restart the speeds are great but then it starts to reset and they drop.

Here is the log.

 

2020-12-10 13:22:47,116 DEBG 'watchdog-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2020-12-10 13:23:02,157 DEBG 'watchdog-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com' to address '142.250.74.196'

2020-12-10 13:23:02,157 DEBG 'watchdog-script' stdout output:
[debug] Waiting for iptables chain policies to be in place...

2020-12-10 13:23:02,165 DEBG 'watchdog-script' stdout output:
[debug] iptables chain policies are in place

2020-12-10 13:23:02,168 DEBG 'watchdog-script' stdout output:
[debug] VPN incoming port is 51796
[debug] qBittorrent incoming port is 51796
[debug] VPN IP is 10.2.228.71

2020-12-10 13:23:02,168 DEBG 'watchdog-script' stdout output:
[debug] qBittorrent IP is 10.2.228.71

2020-12-10 13:23:32,173 DEBG 'watchdog-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2020-12-10 13:23:32,271 DEBG 'watchdog-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com' to address '172.217.12.164'

2020-12-10 13:23:32,272 DEBG 'watchdog-script' stdout output:
[debug] Waiting for iptables chain policies to be in place...

2020-12-10 13:23:32,279 DEBG 'watchdog-script' stdout output:
[debug] iptables chain policies are in place

2020-12-10 13:23:32,283 DEBG 'watchdog-script' stdout output:
[debug] VPN incoming port is 51796
[debug] qBittorrent incoming port is 51796
[debug] VPN IP is 10.2.228.71

2020-12-10 13:23:32,283 DEBG 'watchdog-script' stdout output:
[debug] qBittorrent IP is 10.2.228.71

2020-12-10 13:24:02,288 DEBG 'watchdog-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2020-12-10 13:24:02,390 DEBG 'watchdog-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com' to address '172.217.12.164'

2020-12-10 13:24:02,391 DEBG 'watchdog-script' stdout output:
[debug] Waiting for iptables chain policies to be in place...

2020-12-10 13:24:02,398 DEBG 'watchdog-script' stdout output:
[debug] iptables chain policies are in place

2020-12-10 13:24:02,401 DEBG 'watchdog-script' stdout output:
[debug] VPN incoming port is 51796
[debug] qBittorrent incoming port is 51796
[debug] VPN IP is 10.2.228.71

2020-12-10 13:24:02,402 DEBG 'watchdog-script' stdout output:
[debug] qBittorrent IP is 10.2.228.71

2020-12-10 13:24:20,259 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '51796'

2020-12-10 13:24:32,407 DEBG 'watchdog-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2020-12-10 13:24:32,426 DEBG 'watchdog-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com' to address '216.58.214.4'

2020-12-10 13:24:32,426 DEBG 'watchdog-script' stdout output:
[debug] Waiting for iptables chain policies to be in place...

2020-12-10 13:24:32,434 DEBG 'watchdog-script' stdout output:
[debug] iptables chain policies are in place

2020-12-10 13:24:32,437 DEBG 'watchdog-script' stdout output:
[debug] VPN incoming port is 51796
[debug] qBittorrent incoming port is 51796
[debug] VPN IP is 10.2.228.71

2020-12-10 13:24:32,437 DEBG 'watchdog-script' stdout output:
[debug] qBittorrent IP is 10.2.228.71

2020-12-10 13:25:02,442 DEBG 'watchdog-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2020-12-10 13:25:02,541 DEBG 'watchdog-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com' to address '172.217.12.164'

2020-12-10 13:25:02,542 DEBG 'watchdog-script' stdout output:
[debug] Waiting for iptables chain policies to be in place...

2020-12-10 13:25:02,549 DEBG 'watchdog-script' stdout output:
[debug] iptables chain policies are in place

2020-12-10 13:25:02,553 DEBG 'watchdog-script' stdout output:
[debug] VPN incoming port is 51796
[debug] qBittorrent incoming port is 51796
[debug] VPN IP is 10.2.228.71

2020-12-10 13:25:02,553 DEBG 'watchdog-script' stdout output:
[debug] qBittorrent IP is 10.2.228.71

2020-12-10 13:25:32,558 DEBG 'watchdog-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2020-12-10 13:25:32,669 DEBG 'watchdog-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com' to address '172.217.12.164'

2020-12-10 13:25:32,669 DEBG 'watchdog-script' stdout output:
[debug] Waiting for iptables chain policies to be in place...

2020-12-10 13:25:32,677 DEBG 'watchdog-script' stdout output:
[debug] iptables chain policies are in place

2020-12-10 13:25:32,680 DEBG 'watchdog-script' stdout output:
[debug] VPN incoming port is 51796
[debug] qBittorrent incoming port is 51796
[debug] VPN IP is 10.2.228.71

2020-12-10 13:25:32,680 DEBG 'watchdog-script' stdout output:
[debug] qBittorrent IP is 10.2.228.71

Help is appreciated.

Edited by Seraph91P
Link to comment
19 minutes ago, binhex said:

there is no sign of reconnection in your log snippet, what makes you think its reconnecting?

The Ip keeps changing as you can see here.

[debug] DNS operational, we can resolve name 'www.google.com' to address '142.250.74.196'

2020-12-10 13:23:02,157 DEBG 'watchdog-script' stdout output:
[debug] Waiting for iptables chain policies to be in place...

2020-12-10 13:23:02,165 DEBG 'watchdog-script' stdout output:
[debug] iptables chain policies are in place

2020-12-10 13:23:02,168 DEBG 'watchdog-script' stdout output:
[debug] VPN incoming port is 51796
[debug] qBittorrent incoming port is 51796
[debug] VPN IP is 10.2.228.71

2020-12-10 13:23:02,168 DEBG 'watchdog-script' stdout output:
[debug] qBittorrent IP is 10.2.228.71

2020-12-10 13:23:32,173 DEBG 'watchdog-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2020-12-10 13:23:32,271 DEBG 'watchdog-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com' to address '172.217.12.164'

 

Link to comment
3 minutes ago, Seraph91P said:

The Ip keeps changing as you can see here.

if you mean the following lines then that is perfectly normal and does not indicate a restart/reconnection, its simply round robin load balancing returning different ip's for a name server lookup of www.google.com:-

 

5 minutes ago, Seraph91P said:

[debug] DNS operational, we can resolve name 'www.google.com' to address '142.250.74.196'

 

5 minutes ago, Seraph91P said:

[debug] DNS operational, we can resolve name 'www.google.com' to address '172.217.12.164'

 

Link to comment
41 minutes ago, Seraph91P said:

The Ip keeps changing as you can see here.


[debug] DNS operational, we can resolve name 'www.google.com' to address '142.250.74.196'

2020-12-10 13:23:02,157 DEBG 'watchdog-script' stdout output:
[debug] Waiting for iptables chain policies to be in place...

2020-12-10 13:23:02,165 DEBG 'watchdog-script' stdout output:
[debug] iptables chain policies are in place

2020-12-10 13:23:02,168 DEBG 'watchdog-script' stdout output:
[debug] VPN incoming port is 51796
[debug] qBittorrent incoming port is 51796
[debug] VPN IP is 10.2.228.71

2020-12-10 13:23:02,168 DEBG 'watchdog-script' stdout output:
[debug] qBittorrent IP is 10.2.228.71

2020-12-10 13:23:32,173 DEBG 'watchdog-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2020-12-10 13:23:32,271 DEBG 'watchdog-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com' to address '172.217.12.164'

 

 

 

35 minutes ago, binhex said:

if you mean the following lines then that is perfectly normal and does not indicate a restart/reconnection, its simply round robin load balancing returning different ip's for a name server lookup of www.google.com:-

 

 

 

Ok forget what I said just saw it myself this is just the dns the ip stays the same.

But still my speeds are like all over the place from 10kbs to 10mbs and keep bouncing around is this normal? 

After the start of the container its like super fast and stays there but after some time it crashes to kbs.

Like 7kbs after I had 14mbs before?

Am Downloading to the cache drive.

Because if I try the same torrent without vpn its more steady.

Edited by Seraph91P
Link to comment

I'm having an issue with wireguard on both the qBittorrent and Deluge containers.  When I connect the container to the default bridge network, it works fine.  If I connect it to a different network or to an additional network (for reverse proxy purposes--I'm using cloudbox on Ubuntu, so the "cloudbox" network in this case), I get this error when the container starts:

 

[crit] PIA VPN server info JSON cannot be downloaded from URL 'https://serverlist.piaservers.net/vpninfo/servers/v4' exit code from curl is '0', exiting...

 

This only happens when using wireguard and only when the container is connected to something besides the default bridge network.  It works fine with wireguard on the default bridge network, and it works fine with OpenVPN in all cases.  

 

Any idea what I'm doing wrong?

 

 

Link to comment

I'm having issues with write cache overload / high IO wait.

I used to own a seedbox, but then moved to a place with a gigabit line, so decided to bring everything in-house.

I'm running on an array of 5x 4TB disks (~< 1 year old), with a 500GB SSD cache sitting on top. The server itself is an 8c/16t xeon with 64GB of ram.

 

For some reason now, when I'm downloading large files, it'll hit max speed for a bit, then drop down to ~40MBs, and unraid UI will lock up. If I SSH in, top says my wait is 40-50, at the same time, qbt is reporting around 80% write cache overload.

None of this seems particularly normal to me, and I would assume that any downloads go straight to the cache (considering that's where my docker image sits), so there should be no huge wait times there.

 

I've tried different combinations of pre-allocating or not, playing with the IO threads and cache lifetime values, but I can't seem to figure out what the problem is here. 

 

If anyone has any idea where I can start looking, that would be amazing, thanks.

Link to comment

I experience much the same thing but not just with QBT but with general file activity.

 

If you install netdata you can watch the iowait and other factors but what I have noticed in particular is that the ram dirty writes seem to be the issue.

 

Basically the cache will fill up and then it will decide it needs to flush it to disk, the entire server will become non responsive until it finished flushing to disk. It seems to be a bug with unraid itself.

 

Reducing the dirty writes using the tips and tweaks plugin down to ~2-3% seems to help in the sense that it can flush the data much faster and the lock up is short lived but this also defeats the purpose of the cache and wastes the ram. Also causes the hard drives to trash more.

 

So I just live with the lockups.

 

This and the dismally slow performance with small files over SMB are the only real complaints I have had with unraid.

 

Being that these drives appear to just be used for seeding, it is possible you could reduce the downtime by moving them into a BTRFS cache pool (6.9 beta allows for multiple pools) and use a raid5 setup so that the speed is greatly increased and it can flush the data faster.

 

Plus it keeps these drives out of the array, I like to only have drives with my personal important data in the array and drives I don't care about in separate pools.

Edited by TexasUnraid
Link to comment

Full disclaimer, I'm very new to this, just finished my first Unraid build last week and really trying to get it up and running now, so this very well could be user error. Early in the week I was using QBittorrent and was getting fantastic downloads. Then suddenly they stopped with no changes to settings. Looking at the Q&A-

 

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

 

Question 22 I believe applies, I get this error from the logs-

 

2020-12-11 23:15:07 DEPRECATED OPTION: --cipher set to 'aes-256-gcm' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'aes-256-gcm' to --data-ciphers or change --cipher 'aes-256-gcm' to --data-ciphers-fallback 'aes-256-gcm' to silence this warning.

 

I followed the directions the answer 22 and have had no change. I've tried a couple different endpoints, all the same results. 

Am I just missing sometime or doing something wrong? At this point I'm open to signing up with a new VPN if that would solve it, I know PIA seems to be a mess right now. 

 

 

Edit- Please disregard. It very much was user error and me not entering my save paths correctly. 

Edited by Matt0925
Link to comment

Sorry, i couldn't find the steps using search and this is my first go-around with unraid. 

 

How can I change the webui port from 8080 to something like 8090? 8080 is taken by my Unifi controller. Changing the Host Port 3 and WEBUI_PORT didn't seem to do the trick. 

 

Edited by bakab
Link to comment
6 hours ago, bakab said:

Sorry, i couldn't find the steps using search and this is my first go-around with unraid. 

 

How can I change the webui port from 8080 to something like 8090? 8080 is taken by my Unifi controller. Changing the Host Port 3 and WEBUI_PORT didn't seem to do the trick. 

 

Quote from the GitHub/docker hub readme-

Quote

Due to issues with CSRF and port mapping, should you require to alter the port for the webui you need to change both sides of the -p 8080 switch AND set the WEBUI_PORT variable to the new port.

For example, to set the port to 8090 you need to set -p 8090:8090 and -e WEBUI_PORT=8090

 

  • Thanks 1
Link to comment

First of all, thank you for your amazing work Binhex!

 

I'm doing some testing with qBit, Sonarr and Jacket (all Binhex). When downloading a torrent (<100%) and then choosing to delete it and have qBit also delete the files on the hard disk, it deletes the whole /data/incomplete folder. The folder will be recreated by qBit when I start a new torrent. Strange behaviour, I have the same settings on my desktop qBit and that keeps the /incomplete folder. Ideas?

 

587272548_Skarmavbild2020-12-22kl_16_42_56.png.5e0003d6d4daf6019501829bc47ca098.png

 

 

Also, I'm using this script in qBit:

Quote

unrar x "%F/.r" "%F/"

to automatically unpack .rar files that is being picked up on a private tracker by Sonarr/Radarr. It works, but after the seeding limits are met and Sonarr is deleting the files it doesn't delete the unpacked file. Anyone have any idea on how to modify the script to delete the unpacked file after Sonarr have copied it to the array?

Link to comment

Hi,

 

I'm having issues reassigning the WebUI port to avoid the conflict with my Ubiquiti Console Docker. I read the ReadMe on GitHub as well as some posts on here and such have reassigned both the WebGui port as well as both sides of the port allocation in the Docker settings. I stil don't get anything when I connect the the set port. My docker install command results are below (vpn credentials edited)

 

Quote

 

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='binhex-qbittorrentvpn' --net='bridge' --privileged=true -e TZ="America/New_York" -e HOST_OS="Unraid" -e 'VPN_ENABLED'='yes' -e 'VPN_USER'='*******' -e 'VPN_PASS'='********' -e 'VPN_PROV'='pia' -e 'VPN_CLIENT'='openvpn' -e 'VPN_OPTIONS'='' -e 'STRICT_PORT_FORWARD'='yes' -e 'ENABLE_PRIVOXY'='no' -e 'WEBUI_PORT'='8088' -e 'LAN_NETWORK'='192.168.2.1/24' -e 'NAME_SERVERS'='209.222.18.222,84.200.69.80,37.235.1.174,1.1.1.1,209.222.18.218,37.235.1.177,84.200.70.40,1.0.0.1' -e 'ADDITIONAL_PORTS'='' -e 'DEBUG'='false' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -p '6881:6881/tcp' -p '6881:6881/udp' -p '9119:8118/tcp' -p '8088:8088/tcp' -v '/mnt/user/appdata/data':'/data':'rw' -v '/mnt/user/appdata/binhex-qbittorrentvpn':'/config':'rw' --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'binhex/arch-qbittorrentvpn'


The command finished successfully!

 

 

From what I can understand I have successfully edited -p '8088:8088/tcp' as well as -e 'WEBUI_PORT'='8088'

The only detail where I might have gone wrong is to change the -p setting I had to delete "Host Path 3" in the image settings and create a new "Host Path 3" BTW I set privoxy to 9119 but that was the case before and didn't cause any issues previously.

Link to comment
Quote

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

2020-12-23 13:40:24.823363 [info] System information Linux 18242c6a6041 4.19.107-Unraid #1 SMP Thu Mar 5 13:55:57 PST 2020 x86_64 GNU/Linux
2020-12-23 13:40:24.870496 [info] OS_ARCH defined as 'x86-64'
2020-12-23 13:40:24.902733 [info] PUID defined as '99'
2020-12-23 13:40:24.938007 [info] PGID defined as '100'
2020-12-23 13:40:25.037953 [info] UMASK defined as '000'
2020-12-23 13:40:25.068462 [info] Permissions already set for volume mappings
2020-12-23 13:40:25.101351 [info] Deleting files in /tmp (non recursive)...
2020-12-23 13:40:25.139890 [info] VPN_ENABLED defined as 'yes'
2020-12-23 13:40:25.176281 [info] VPN_CLIENT defined as 'wireguard'
2020-12-23 13:40:25.204938 [info] VPN_PROV defined as 'pia'
2020-12-23 13:40:25.816438 [info] WireGuard config file (conf extension) is located at /config/wireguard/wg0.conf
2020-12-23 13:40:25.868489 [info] VPN_REMOTE_SERVER defined as 'ca-toronto.privacy.network'
2020-12-23 13:40:25.928723 [info] VPN_REMOTE_PORT defined as '1337'
2020-12-23 13:40:25.956248 [info] VPN_DEVICE_TYPE defined as 'wg0'
2020-12-23 13:40:25.987615 [info] VPN_REMOTE_PROTOCOL defined as 'udp'
2020-12-23 13:40:26.019172 [info] LAN_NETWORK defined as '192.168.2.1/24'
2020-12-23 13:40:26.052560 [info] NAME_SERVERS defined as '209.222.18.222,84.200.69.80,37.235.1.174,1.1.1.1,209.222.18.218,37.235.1.177,84.200.70.40,1.0.0.1'
2020-12-23 13:40:26.084462 [info] VPN_USER defined as ***********
2020-12-23 13:40:26.118218 [info] VPN_PASS defined as ************
2020-12-23 13:40:26.149898 [info] STRICT_PORT_FORWARD defined as 'yes'
2020-12-23 13:40:26.184504 [info] ENABLE_PRIVOXY defined as 'no'
2020-12-23 13:40:26.220492 [info] ADDITIONAL_PORTS not defined (via -e ADDITIONAL_PORTS), skipping allow for custom incoming ports
2020-12-23 13:40:26.252616 [info] WEBUI_PORT defined as '8088'
2020-12-23 13:40:26.283490 [info] Starting Supervisor...
2020-12-23 13:40:26,463 INFO Included extra file "/etc/supervisor/conf.d/qbittorrent.conf" during parsing
2020-12-23 13:40:26,464 INFO Set uid to user 0 succeeded
2020-12-23 13:40:26,467 INFO supervisord started with pid 6
2020-12-23 13:40:27,470 INFO spawned: 'start-script' with pid 145
2020-12-23 13:40:27,472 INFO spawned: 'watchdog-script' with pid 146
2020-12-23 13:40:27,473 INFO reaped unknown pid 7 (exit status 0)
2020-12-23 13:40:27,479 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2020-12-23 13:40:27,479 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2020-12-23 13:40:27,479 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2020-12-23 13:40:27,480 DEBG 'watchdog-script' stdout output:
[info] qBittorrent config file already exists, skipping copy

2020-12-23 13:40:27,480 DEBG 'watchdog-script' stdout output:
[info] Removing session lock file (if it exists)...

2020-12-23 13:40:27,482 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.222 to /etc/resolv.conf

2020-12-23 13:40:27,487 DEBG 'start-script' stdout output:
[info] Adding 84.200.69.80 to /etc/resolv.conf

2020-12-23 13:40:27,490 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.174 to /etc/resolv.conf

2020-12-23 13:40:27,495 DEBG 'start-script' stdout output:
[info] Adding 1.1.1.1 to /etc/resolv.conf

2020-12-23 13:40:27,500 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.218 to /etc/resolv.conf

2020-12-23 13:40:27,503 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.177 to /etc/resolv.conf

2020-12-23 13:40:27,507 DEBG 'start-script' stdout output:
[info] Adding 84.200.70.40 to /etc/resolv.conf

2020-12-23 13:40:27,510 DEBG 'start-script' stdout output:
[info] Adding 1.0.0.1 to /etc/resolv.conf

2020-12-23 13:40:48,365 DEBG 'start-script' stderr output:
parse error: Invalid numeric literal at line 4, column 0

2020-12-23 13:40:48,565 DEBG 'start-script' stdout output:
[info] Trying to connect to the PIA WireGuard API on 'ca-toronto.privacy.network'...

2020-12-23 13:40:48,782 DEBG 'start-script' stdout output:
[info] Default route for container is 172.17.0.1

2020-12-23 13:40:48,797 DEBG 'start-script' stdout output:
[info] Docker network defined as    172.17.0.0/16

2020-12-23 13:40:48,802 DEBG 'start-script' stdout output:
[info] Adding 192.168.2.1/24 as route via docker eth0

2020-12-23 13:40:48,804 DEBG 'start-script' stderr output:
Error: Invalid prefix for given prefix length.

2020-12-23 13:40:48,804 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2020-12-23 13:40:48,805 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.5

2020-12-23 13:40:48,805 DEBG 'start-script' stdout output:
--------------------

2020-12-23 13:40:48,810 DEBG 'start-script' stdout output:
iptable_mangle         16384  12
ip_tables              24576  26 iptable_filter,iptable_raw,iptable_nat,iptable_mangle

2020-12-23 13:40:48,810 DEBG 'start-script' stdout output:
[info] iptable_mangle support detected, adding fwmark for tables

2020-12-23 13:40:48,883 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2020-12-23 13:40:48,885 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 -i eth0 -p tcp -m tcp --sport 1337 -j ACCEPT
-A INPUT -i eth0 -p udp -m udp --sport 1337 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 8088 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --sport 8088 -j ACCEPT
-A INPUT -s 192.168.2.0/24 -i eth0 -p tcp -m tcp --dport 8088 -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 -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --dport 1337 -j ACCEPT
-A OUTPUT -o eth0 -p udp -m udp --dport 1337 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --dport 8088 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 8088 -j ACCEPT
-A OUTPUT -d 192.168.2.0/24 -o eth0 -p tcp -m tcp --sport 8088 -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

2020-12-23 13:40:48,886 DEBG 'start-script' stdout output:
--------------------

2020-12-23 13:40:48,889 DEBG 'start-script' stdout output:
[info] Attempting to bring WireGuard interface 'up'...

2020-12-23 13:40:48,899 DEBG 'start-script' stderr output:
Warning: `/config/wireguard/wg0.conf' is world accessible

2020-12-23 13:40:48,905 DEBG 'start-script' stderr output:
[#] ip link add wg0 type wireguard

2020-12-23 13:40:48,907 DEBG 'start-script' stderr output:
[#] wg setconf wg0 /dev/fd/63

2020-12-23 13:40:48,915 DEBG 'start-script' stderr output:
[#] ip -4 address add 10.56.240.113 dev wg0

2020-12-23 13:40:48,920 DEBG 'start-script' stderr output:
[#] ip link set mtu 1420 up dev wg0

2020-12-23 13:40:48,938 DEBG 'start-script' stderr output:
[#] wg set wg0 fwmark 51820

2020-12-23 13:40:48,939 DEBG 'start-script' stderr output:
[#] ip -4 route add 0.0.0.0/0 dev wg0 table 51820

2020-12-23 13:40:48,940 DEBG 'start-script' stderr output:
[#] ip -4 rule add not fwmark 51820 table 51820

2020-12-23 13:40:48,942 DEBG 'start-script' stderr output:
[#] ip -4 rule add table main suppress_prefixlength 0

2020-12-23 13:40:48,946 DEBG 'start-script' stderr output:
[#] sysctl -q net.ipv4.conf.all.src_valid_mark=1

2020-12-23 13:40:48,947 DEBG 'start-script' stderr output:
[#] iptables-restore -n

2020-12-23 13:40:48,950 DEBG 'start-script' stderr output:
[#] '/root/wireguardup.sh'

2020-12-23 13:40:50,244 DEBG 'start-script' stdout output:
[info] Attempting to get external IP using 'http://checkip.amazonaws.com'...

2020-12-23 13:40:50,392 DEBG 'start-script' stdout output:
[info] Successfully retrieved external IP address 66.115.142.122

2020-12-23 13:40:50,393 DEBG 'start-script' stdout output:
[info] WireGuard interface 'up'

2020-12-23 13:40:50,393 DEBG 'start-script' stdout output:
[info] Script started to assign incoming port
[info] Port forwarding is enabled
[info] Checking endpoint 'ca-toronto.privacy.network' is port forward enabled...

2020-12-23 13:40:50,902 DEBG 'start-script' stdout output:
[info] PIA endpoint 'ca-toronto.privacy.network' is in the list of endpoints that support port forwarding

2020-12-23 13:40:50,903 DEBG 'start-script' stdout output:
[info] List of PIA endpoints that support port forwarding:-
[info] al.privacy.network
[info] ad.privacy.network
[info] austria.privacy.network
[info] brussels.privacy.network
[info] ba.privacy.network
[info] sofia.privacy.network
[info] czech.privacy.network
[info] denmark.privacy.network
[info] ee.privacy.network
[info] fi.privacy.network
[info] france.privacy.network
[info] de-frankfurt.privacy.network
[info] de-berlin.privacy.network
[info] gr.privacy.network
[info] hungary.privacy.network
[info] is.privacy.network
[info] ireland.privacy.network
[info] man.privacy.network
[info] italy.privacy.network
[info] lv.privacy.network
[info] liechtenstein.privacy.network
[info] lt.privacy.network
[info] lu.privacy.network
[info] mk.privacy.network
[info] malta.privacy.network
[info] md.privacy.network
[info] monaco.privacy.network
[info] montenegro.privacy.network
[info] nl-amsterdam.privacy.network
[info] no.privacy.network
[info] poland.privacy.network

2020-12-23 13:40:50,903 DEBG 'start-script' stdout output:
[info] pt.privacy.network
[info] ro.privacy.network
[info] rs.privacy.network
[info] sk.privacy.network
[info] spain.privacy.network
[info] sweden.privacy.network
[info] swiss.privacy.network
[info] ua.privacy.network
[info] uk-london.privacy.network
[info] uk-southampton.privacy.network
[info] uk-manchester.privacy.network
[info] uk-bbc.privacy.network
[info] bahamas.privacy.network
[info] ca-montreal.privacy.network
[info] ca-toronto.privacy.network
[info] ca-ontario.privacy.network
[info] ca-vancouver.privacy.network
[info] greenland.privacy.network
[info] mexico.privacy.network
[info] panama.privacy.network
[info] ar.privacy.network
[info] br.privacy.network
[info] venezuela.privacy.network
[info] yerevan.privacy.network
[info] bangladesh.privacy.network
[info] cambodia.privacy.network
[info] china.privacy.network
[info] cyprus.privacy.network
[info] georgia.privacy.network
[info] hk.privacy.network
[info] in.privacy.network
[info] israel.privacy.network
[info] japan.privacy.network
[info] kazakhstan.privacy.network
[info] macau.privacy.network
[info] mongolia.privacy.network
[info] philippines.privacy.network
[info] qatar.privacy.network
[info] saudiarabia.privacy.network
[info] sg.privacy.network
[info] srilanka.privacy.network
[info] taiwan.privacy.network
[info] tr.privacy.network
[info] ae.privacy.network
[info] vietnam.privacy.network
[info] aus-perth.privacy.network
[info] au-sydney.privacy.network
[info] aus-melbourne.privacy.network
[info] nz.privacy.network
[info] dz.privacy.network
[info] egypt.privacy.network
[info] morocco.privacy.network
[info] nigeria.privacy.network
[info] za.privacy.network

2020-12-23 13:40:52,572 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '43857'

2020-12-23 13:40:53,053 DEBG 'watchdog-script' stdout output:
[info] qBittorrent listening interface IP 0.0.0.0 and VPN provider IP 10.56.240.113 different, marking for reconfigure

2020-12-23 13:40:53,058 DEBG 'watchdog-script' stdout output:
[info] qBittorrent not running

2020-12-23 13:40:53,058 DEBG 'watchdog-script' stdout output:
[info] qBittorrent incoming port 6881 and VPN incoming port 43857 different, marking for reconfigure

2020-12-23 13:40:53,059 DEBG 'watchdog-script' stdout output:
[info] Removing session lock file (if it exists)...

2020-12-23 13:40:53,061 DEBG 'watchdog-script' stdout output:
[info] Attempting to start qBittorrent...

2020-12-23 13:40:53,077 DEBG 'watchdog-script' stdout output:
[info] qBittorrent process started
[info] Waiting for qBittorrent process to start listening on port 8088...

2020-12-23 13:40:53,194 DEBG 'watchdog-script' stdout output:
[info] qBittorrent process listening on port 8088

 

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.