Jump to content
binhex

[Support] binhex - qBittorrentVPN

104 posts in this topic Last Reply

Recommended Posts

9 minutes ago, privateer said:

Every time I restart the container while files are actively downloading it goes through and checks every one of them. Is this supposed to happen? Is there any way to disable this?

The integrity of torrents requires the application to know the files haven't changed. 

Share this post


Link to post
5 hours ago, trurl said:

The integrity of torrents requires the application to know the files haven't changed. 

There's no way to safely shutdown to prevent this? If I have hundreds of files running this effectively takes me offline for doing something as simple as updating the container. I'll note that binhex's ruTorrent doesn't do this step either.

Share this post


Link to post
10 hours ago, privateer said:

There's no way to safely shutdown to prevent this? If I have hundreds of files running this effectively takes me offline for doing something as simple as updating the container. I'll note that binhex's ruTorrent doesn't do this step either.

looking at the link below, it looks like qbittorrent has an issue shutting down cleanly, it seems to affect both windows and linux, this is most probably the cause of the re-hashing taking place on startup due to unclean shutdown:-

 

https://github.com/qbittorrent/qBittorrent/issues/5097

Share this post


Link to post

Hi just like too be sure if I like too setup Socks5  https://nordvpn.com/da/tutorials/socks5/ 
are it just put the option in there say port 1080 do I need to change some of the port on the docker for that don't know what the all are for  . 
It for with out Nordvpn give problem with upload 

Share this post


Link to post

I've read the thread but coudn't find a solution to my problem, maybe you can help me. I keep getting the message "[info] Waiting for qBittorrent process to start listening on port 911..." but the webpage is never accessible.

qb1.jpg

qb2.jpg

Share this post


Link to post
2 hours ago, MonkyCasual said:

I've read the thread but coudn't find a solution to my problem, maybe you can help me. I keep getting the message "[info] Waiting for qBittorrent process to start listening on port 911..." but the webpage is never accessible.

are you running the container 'privileged', if not then qbittorrent will not start.

  • Upvote 1

Share this post


Link to post

Yes, basically the first check translates as "run the container with high permissions" and the second ticked checkmark is to automatically restart the container

qb3.jpg

Share this post


Link to post
1 hour ago, MonkyCasual said:

Yes, basically the first check translates as "run the container with high permissions" and the second ticked checkmark is to automatically restart the container

qb3.jpg

hmm ok, i would double check with synology support/forum that that checkbox really does equate to the 'privileged' flag for docker, as if its anything less than that then you will see the exact symptoms you are describing.

 

one other thing to check, what happens if you set VPN_ENABLED to no, can you access the web ui then?.

Share this post


Link to post
17 minutes ago, binhex said:

hmm ok, i would double check with synology support/forum that that checkbox really does equate to the 'privileged' flag for docker, as if its anything less than that then you will see the exact symptoms you are describing.

 

one other thing to check, what happens if you set VPN_ENABLED to no, can you access the web ui then?.

As per synology's website it is execute with high privilege, ive used that for multiple instances as well, including your (binhex) delugevpn. But pia told me to use qbittorrent instead as it would be better for speeds.

 

Ive tried multiple changes among vpn_enabled to no but no different out ome unfortunately.

 

I thought it had something to do with VPN port forwarding but that would be weird as I should still be able to access the we ui even when VPN is off

Share this post


Link to post
1 minute ago, MonkyCasual said:

As per synology's website it is execute with high privilege, ive used that for multiple instances as well, including your (binhex) delugevpn

delugevpn does not require privileged elevation, it is set like that for unraid users only because there is no simple way to set '--cap-add=NET_ADMIN' which is what is actually required (other than extra args which is ugly). so i know you are saying this is 'high privilege' but i have to ask, is that the same as 'docker run <rest of command> --privileged=true <rest of command>', can you actually see what synology executes as a command line?.

 

4 minutes ago, MonkyCasual said:

I thought it had something to do with VPN port forwarding but that would be weird as I should still be able to access the we ui even when VPN is off

if you cant access the ui when the vpn is disabled then the issue is not related to port forwarding, openvpn config or account credentials, its got to be permissions related, thats my guess, is there nobody else you can talk to on the synology forum that has this running?, it probably would be much quicker as they know what hoops (if any) need to he jumped through in order to get this running on a synology appliance.

Share this post


Link to post
1 minute ago, binhex said:

delugevpn does not require privileged elevation, it is set like that for unraid users only because there is no simple way to set '--cap-add=NET_ADMIN' which is what is actually required (other than extra args which is ugly). so i know you are saying this is 'high privilege' but i have to ask, is that the same as 'docker run <rest of command> --privileged=true <rest of command>', can you actually see what synology executes as a command line?.

 

if you cant access the ui when the vpn is disabled then the issue is not related to port forwarding, openvpn config or account credentials, its got to be permissions related, thats my guess, is there nobody else you can talk to on the synology forum that has this running?, it probably would be much quicker as they know what hoops (if any) need to he jumped through in order to get this running on a synology appliance.

Thanks for the help so far! I'll try to find something on the web in a few minutes and let you know!

Share this post


Link to post

Hi all. Firstly thanks for supplying this image. It's pretty much exactly what I'm looking for! I just have 2 issues I'm hoping the community can help with. I've Googled both extensively - so I hope they aren't stupid problems. this is my 1st Docker container - so I'm a complete newbie! I'm running Docker Desktop on W10 for now (until my Pi arrives :))

 

So I have got the container to run fine and everything seems to work - Privoxy, VPN and QT. Except QT won't start automatically when the container starts. If I run /usr/bin/qbittorrent-nox it starts fine - and works fine. I thought I might be able to add the application to startup, but I thought it wuld be better to try and understand why it is not running first. Could you perhaps point in to where QT should be starting up automatically so I can maybe try and work out why it is not?

 

Secondly, I want to save torrents to a SAMBA share (an old NAS). So I want to try and install and configure cifs-utils on the container. However, if I bash into the container and run pacman to download the package (or any package) it times out - specifically on the extra package. The core installs fine, but when pacman goes to download the extra package, the speed slows right down about 40% through and I eventually get the message "Operation too slow. Less than 1 bytes/sec transferred the last 10 seconds". This even happens when I run pacman -Syy... I have made sure my Windows host firewall is off etc. The Torrents themselves download fine at a decent speed - so I assume the networking is good. I have tried changing DNS for that container and using different mirrors for pacman.

 

Google has told me to try and use wget for pacman. But wget is not installed by default - and of course I can't download it either! So I was wondering if maybe this had to do with pacman going through the VPN or something? Has anyone else experienced this?

 

Thanks for any advice in advance. Apologies for the newbie questions!

Edited by TheSpook
update

Share this post


Link to post
10 hours ago, TheSpook said:

Privoxy, VPN and QT. Except QT won't start automatically when the container starts. If I run /usr/bin/qbittorrent-nox it starts fine - and works fine.

so if qbittorrent isnt starting then the vpn tunnel is not operational, manually starting qbittorrent could result in ip leakage so dont do that, better to find out why te vpn isnt operational, please follow the instructions linked below:-

 

https://forums.unraid.net/topic/44108-support-binhex-general/?do=findComment&amp;comment=435831

 

10 hours ago, TheSpook said:

Secondly, I want to save torrents to a SAMBA share (an old NAS). So I want to try and install and configure cifs-utils on the container.

you are going about this the wrong way, what you should be doing is mounting the smb share on your host machine NOT the container, then you create a docker volume mount to that mount point, so example like:-

 

-v <path to my mount point on the host>:/smb

 

obviously you then finally configure the application (in this case qbittorrent) to use /smb to read/write to - be aware writing to a remote share MAY result in yo-yo dl/ul speeds, ideally i would recommend writing only to local drives on your host.

Edited by binhex
  • Like 1

Share this post


Link to post
14 hours ago, binhex said:

so if qbittorrent isnt starting then the vpn tunnel is not operational, manually starting qbittorrent could result in ip leakage so dont do that, better to find out why te vpn isnt operational, please follow the instructions linked below:-

 

https://forums.unraid.net/topic/44108-support-binhex-general/?do=findComment&amp;comment=435831

 

you are going about this the wrong way, what you should be doing is mounting the smb share on your host machine NOT the container, then you create a docker volume mount to that mount point, so example like:-

 

-v <path to my mount point on the host>:/smb

 

obviously you then finally configure the application (in this case qbittorrent) to use /smb to read/write to - be aware writing to a remote share MAY result in yo-yo dl/ul speeds, ideally i would recommend writing only to local drives on your host.

Awesome and thanks so much for replying! Your second point makes total sense. Stupid thing is I did read about that when I was doing my Docker crash course - then I completely didn't think to use it in this instance! I'm sure that will work perfectly.

 

Re your 1st point. The strange thing is, the VPN seems to be up and running fine. If I set the browser on my host to use Privoxy and go to somewhere like "whatismyipaddress.com" I get a PIA IP address. I double-checked and confirmed that the IP tables also seem to be working as intended (ie if the VPN is down, there is no Internet access). For example, if I run a command to terminate the OpenVPN tunnel in the container (killall openvpn), I can't get out to the Internet at all (DNS doesn't resolve and pings don't work). So I'm pretty sure the VPN is AOK. Could it be that the VPN is taking too long to connect so QBT tries to start before it is established?

Share this post


Link to post
16 hours ago, TheSpook said:

Could it be that the VPN is taking too long to connect so QBT tries to start before it is established?

nope, absolutely not, there is code in place to explicitly prevent this, otherwise you could get into a situation where you have ip leakage, so qbittorrent will not start until the tunnel is established and running.

Share this post


Link to post

Ah ok makes sense. Can you point me possibly in the direction I should look? Where is the config to start QBT automatically? OR are there any logs? I have tried to run the container twice - (with different DNS servers just in case) and had the same situation both times.

Share this post


Link to post
Ah ok makes sense. Can you point me possibly in the direction I should look? Where is the config to start QBT automatically? OR are there any logs? I have tried to run the container twice - (with different DNS servers just in case) and had the same situation both times.
See the link in my post 2 days ago follow that procedure and attach the log

Sent from my EML-L29 using Tapatalk

Share this post


Link to post

I believe I have the container configured correctly. I am moving from your deluge vpn container and setup was about the same. I am using AirVPN. The VPN connects and qbittorrent starts. I can download fine, but I cannot upload anything. Here is my supervisor.log with debug: https://pastebin.com/pKpjbmtU

 

Could it be related to these errors?

2019-02-08 15:01:46,694 DEBG 'start-script' stdout output:
[debug] Attempting to get external IP using Name Server 'ns1.google.com'...

2019-02-08 15:01:46,698 DEBG 'start-script' stdout output:
Error: could not find any address for the name: `ns1.google.com'

2019-02-08 15:01:46,704 DEBG 'start-script' stdout output:
[debug] Failed to get external IP using Name Server 'ns1.google.com', trying 'resolver1.opendns.com'...

2019-02-08 15:01:46,709 DEBG 'start-script' stdout output:
Error: could not find any address for the name: `resolver1.opendns.com'

2019-02-08 15:01:46,715 DEBG 'start-script' stdout output:
[debug] Failed to get external IP using Name Server 'resolver1.opendns.com', trying 'http://checkip.amazonaws.com'...

2019-02-08 15:01:46,739 DEBG 'start-script' stdout output:
[debug] Failed to get external IP using Web Server 'http://checkip.amazonaws.com', trying 'http://whatismyip.akamai.com'...

2019-02-08 15:01:46,756 DEBG 'start-script' stdout output:
[debug] Failed to get external IP using Web Server 'http://whatismyip.akamai.com', trying 'https://showextip.azurewebsites.net'...

2019-02-08 15:01:46,774 DEBG 'start-script' stdout output:
[debug] Failed to get external IP using Web Server 'https://showextip.azurewebsites.net'
[warn] Cannot determine external IP address, exhausted retries setting to tunnel IP '10.30.140.62'

 

Share this post


Link to post

im also not been able to login using admin and adminadmin

i cant test further as I need to head to bed so turned it off and went back to deluge.

Any hints?

Share this post


Link to post
9 hours ago, nekromantik said:

im also not been able to login using admin and adminadmin

i cant test further as I need to head to bed so turned it off and went back to deluge.

Any hints?

guessing here (no log so i cant tell for sure), but i would think you dont have --privileged=true set

Share this post


Link to post
7 hours ago, binhex said:

guessing here (no log so i cant tell for sure), but i would think you dont have --privileged=true set

here is log, privledge mode is on

 

Quote

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

2019-02-11 17:58:14.258073 [info] System information Linux f0d202f63a06 4.19.20-Unraid #1 SMP Sat Feb 9 12:34:16 PST 2019 x86_64 GNU/Linux
2019-02-11 17:58:14.280604 [info] PUID defined as '99'
2019-02-11 17:58:14.380543 [info] PGID defined as '100'
2019-02-11 17:58:14.527336 [info] UMASK defined as '000'
2019-02-11 17:58:14.548747 [info] Permissions already set for volume mappings
2019-02-11 17:58:14.573978 [info] VPN_ENABLED defined as 'yes'
2019-02-11 17:58:14.600536 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/mullvad_cz.ovpn
dos2unix: converting file /config/openvpn/mullvad_cz.ovpn to Unix format...
2019-02-11 17:58:14.633699 [info] VPN remote line defined as 'remote cz.mullvad.net 1301'
2019-02-11 17:58:14.656239 [info] VPN_REMOTE defined as 'cz.mullvad.net'
2019-02-11 17:58:14.678235 [info] VPN_PORT defined as '1301'
2019-02-11 17:58:14.703664 [info] VPN_PROTOCOL defined as 'udp'
2019-02-11 17:58:14.725581 [info] VPN_DEVICE_TYPE defined as 'tun0'
2019-02-11 17:58:14.747224 [info] VPN_PROV defined as 'custom'
2019-02-11 17:58:14.768902 [info] LAN_NETWORK defined as '192.168.1.0/24, 192.168.10.0/24, 192.168.20.0/24'
2019-02-11 17:58:14.790439 [info] NAME_SERVERS defined as '209.222.18.222,37.235.1.174,1.1.1.1,8.8.8.8,209.222.18.218,37.235.1.177,1.0.0.1,8.8.4.4'
2019-02-11 17:58:14.811871 [info] VPN_USER defined as 'x'
2019-02-11 17:58:14.833512 [info] VPN_PASS defined as 'x'
2019-02-11 17:58:14.855026 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2019-02-11 17:58:14.876855 [info] ENABLE_PRIVOXY defined as 'yes'
2019-02-11 17:58:14.898631 [info] WEBUI_PORT defined as '8080'
2019-02-11 17:58:14.925377 [info] Starting Supervisor...
2019-02-11 17:58:15,202 INFO Included extra file "/etc/supervisor/conf.d/qbittorrent.conf" during parsing
2019-02-11 17:58:15,202 INFO Set uid to user 0 succeeded
2019-02-11 17:58:15,204 INFO supervisord started with pid 6
2019-02-11 17:58:16,206 INFO spawned: 'start-script' with pid 141
2019-02-11 17:58:16,207 INFO spawned: 'watchdog-script' with pid 142
2019-02-11 17:58:16,208 INFO spawned: 'privoxy-script' with pid 143
2019-02-11 17:58:16,208 INFO reaped unknown pid 7
2019-02-11 17:58:16,212 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2019-02-11 17:58:16,212 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2019-02-11 17:58:16,212 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2019-02-11 17:58:16,212 INFO success: privoxy-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2019-02-11 17:58:16,213 DEBG 'watchdog-script' stdout output:
[info] qBittorrent config file already exists, skipping copy
[info] Removing session lock file (if it exists)...

2019-02-11 17:58:16,215 DEBG 'watchdog-script' stderr output:
dos2unix: converting file /config/qBittorrent/config/qBittorrent.conf to Unix format...

2019-02-11 17:58:16,258 DEBG 'start-script' stdout output:
[info] Default route for container is 192.168.1.1

2019-02-11 17:58:16,261 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.222 to /etc/resolv.conf

2019-02-11 17:58:16,263 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.174 to /etc/resolv.conf

2019-02-11 17:58:16,266 DEBG 'start-script' stdout output:
[info] Adding 1.1.1.1 to /etc/resolv.conf

2019-02-11 17:58:16,268 DEBG 'start-script' stdout output:
[info] Adding 8.8.8.8 to /etc/resolv.conf

2019-02-11 17:58:16,270 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.218 to /etc/resolv.conf

2019-02-11 17:58:16,273 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.177 to /etc/resolv.conf

2019-02-11 17:58:16,275 DEBG 'start-script' stdout output:
[info] Adding 1.0.0.1 to /etc/resolv.conf

2019-02-11 17:58:16,278 DEBG 'start-script' stdout output:
[info] Adding 8.8.4.4 to /etc/resolv.conf

2019-02-11 17:58:16,497 DEBG 'start-script' stdout output:
[info] Attempting to load iptable_mangle module...

2019-02-11 17:58:16,498 DEBG 'start-script' stderr output:
modprobe: FATAL: Module iptable_mangle not found in directory /lib/modules/4.19.20-Unraid

2019-02-11 17:58:16,498 DEBG 'start-script' stdout output:
[warn] Unable to load iptable_mangle module using modprobe, trying insmod...

2019-02-11 17:58:16,498 DEBG 'start-script' stderr output:
insmod: ERROR: could not load module /lib/modules/iptable_mangle.ko: No such file or directory

2019-02-11 17:58:16,498 DEBG 'start-script' stdout output:
[warn] Unable to load iptable_mangle module, you will not be able to connect to the applications Web UI or Privoxy outside of your LAN
[info] unRAID/Ubuntu users: Please attempt to load the module by executing the following on your host: '/sbin/modprobe iptable_mangle'
[info] Synology users: Please attempt to load the module by executing the following on your host: 'insmod /lib/modules/iptable_mangle.ko'

2019-02-11 17:58:16,512 DEBG 'start-script' stdout output:
[info] Docker network defined as 192.168.1.0/24

2019-02-11 17:58:16,514 DEBG 'start-script' stdout output:
[info] Adding 192.168.1.0/24 as route via docker lan interface

2019-02-11 17:58:16,515 DEBG 'start-script' stderr output:
RTNETLINK answers: File exists

2019-02-11 17:58:16,518 DEBG 'start-script' stdout output:
[info] Adding 192.168.10.0/24 as route via docker lan interface

2019-02-11 17:58:16,521 DEBG 'start-script' stdout output:
[info] Adding 192.168.20.0/24 as route via docker lan interface

2019-02-11 17:58:16,522 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2019-02-11 17:58:16,522 DEBG 'start-script' stdout output:
default via 192.168.1.1 dev eth0
192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.71
192.168.10.0/24 via 192.168.1.1 dev eth0
192.168.20.0/24 via 192.168.1.1 dev eth0

2019-02-11 17:58:16,522 DEBG 'start-script' stdout output:
--------------------

2019-02-11 17:58:16,567 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2019-02-11 17:58:16,568 DEBG 'start-script' stdout output:
-P INPUT DROP
-P FORWARD ACCEPT
-P OUTPUT DROP
-A INPUT -i tun0 -j ACCEPT
-A INPUT -s 192.168.1.0/24 -d 192.168.1.0/24 -j ACCEPT
-A INPUT -i eth0 -p udp -m udp --sport 1301 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 8080 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --sport 8080 -j ACCEPT
-A INPUT -s 192.168.1.0/24 -i eth0 -p tcp -m tcp --dport 8080 -j ACCEPT
-A INPUT -s 192.168.1.0/24 -d 192.168.1.0/24 -i eth0 -p tcp -j ACCEPT
-A INPUT -s 192.168.10.0/24 -i eth0 -p tcp -m tcp --dport 8080 -j ACCEPT
-A INPUT -s 192.168.10.0/24 -d 192.168.1.0/24 -i eth0 -p tcp -j ACCEPT
-A INPUT -s 192.168.20.0/24 -i eth0 -p tcp -m tcp --dport 8080 -j ACCEPT
-A INPUT -s 192.168.20.0/24 -d 192.168.1.0/24 -i eth0 -p tcp -j ACCEPT
-A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A OUTPUT -o tun0 -j ACCEPT
-A OUTPUT -s 192.168.1.0/24 -d 192.168.1.0/24 -j ACCEPT
-A OUTPUT -o eth0 -p udp -m udp --dport 1301 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --dport 8080 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 8080 -j ACCEPT
-A OUTPUT -d 192.168.1.0/24 -o eth0 -p tcp -m tcp --sport 8080 -j ACCEPT
-A OUTPUT -s 192.168.1.0/24 -d 192.168.1.0/24 -o eth0 -p tcp -j ACCEPT
-A OUTPUT -d 192.168.10.0/24 -o eth0 -p tcp -m tcp --sport 8080 -j ACCEPT
-A OUTPUT -s 192.168.1.0/24 -d 192.168.10.0/24 -o eth0 -p tcp -j ACCEPT
-A OUTPUT -d 192.168.20.0/24 -o eth0 -p tcp -m tcp --sport 8080 -j ACCEPT
-A OUTPUT -s 192.168.1.0/24 -d 192.168.20.0/24 -o eth0 -p tcp -j ACCEPT
-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A OUTPUT -o lo -j ACCEPT

2019-02-11 17:58:16,568 DEBG 'start-script' stdout output:
--------------------

2019-02-11 17:58:16,569 DEBG 'start-script' stdout output:
[info] Starting OpenVPN...

2019-02-11 17:58:16,585 DEBG 'start-script' stdout output:
Mon Feb 11 17:58:16 2019 WARNING: file 'credentials.conf' is group or others accessible
Mon Feb 11 17:58:16 2019 OpenVPN 2.4.6 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Apr 24 2018
Mon Feb 11 17:58:16 2019 library versions: OpenSSL 1.1.1a 20 Nov 2018, LZO 2.10

2019-02-11 17:58:16,586 DEBG 'start-script' stdout output:
[info] OpenVPN started

2019-02-11 17:58:16,586 DEBG 'start-script' stdout output:
Mon Feb 11 17:58:16 2019 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2019-02-11 17:58:16,586 DEBG 'start-script' stdout output:
Mon Feb 11 17:58:16 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]xx
Mon Feb 11 17:58:16 2019 Socket Buffers: R=[212992->1048576] S=[212992->1048576]
Mon Feb 11 17:58:16 2019 UDP link local: (not bound)

2019-02-11 17:58:16,587 DEBG 'start-script' stdout output:
Mon Feb 11 17:58:16 2019 UDP link remote: [AF_INET]185.156.174.170:1301

2019-02-11 17:58:16,622 DEBG 'start-script' stdout output:
Mon Feb 11 17:58:16 2019 TLS: Initial packet from [AF_INET]185.156.174.170:1301, sid=bc491c1d 48695aa9

2019-02-11 17:58:16,732 DEBG 'start-script' stdout output:
Mon Feb 11 17:58:16 2019 VERIFY OK: depth=2, C=SE, ST=Gotaland, L=Gothenburg, O=Amagicom AB, OU=Mullvad, CN=Mullvad Root CA v2, emailAddress=security@mullvad.net

2019-02-11 17:58:16,732 DEBG 'start-script' stdout output:
Mon Feb 11 17:58:16 2019 VERIFY OK: depth=1, C=SE, ST=Gotaland, O=Amagicom AB, OU=Mullvad, CN=Mullvad Transition-Intermediate CA v1, emailAddress=security@mullvad.net

2019-02-11 17:58:16,732 DEBG 'start-script' stdout output:
Mon Feb 11 17:58:16 2019 VERIFY KU OK
Mon Feb 11 17:58:16 2019 Validating certificate extended key usage
Mon Feb 11 17:58:16 2019 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
Mon Feb 11 17:58:16 2019 VERIFY EKU OK
Mon Feb 11 17:58:16 2019 VERIFY OK: depth=0, C=SE, ST=Gotaland, O=Amagicom AB, OU=Mullvad, CN=cz-prg-002.mullvad.net, emailAddress=security@mullvad.net

2019-02-11 17:58:16,885 DEBG 'start-script' stdout output:
Mon Feb 11 17:58:16 2019 WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1557', remote='link-mtu 1558'
Mon Feb 11 17:58:16 2019 WARNING: 'comp-lzo' is present in remote config but missing in local config, remote='comp-lzo'

2019-02-11 17:58:16,886 DEBG 'start-script' stdout output:
Mon Feb 11 17:58:16 2019 Control Channel: TLSv1.2, cipher TLSv1.2 DHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
Mon Feb 11 17:58:16 2019 [cz-prg-002.mullvad.net] Peer Connection Initiated with [AF_INET]185.156.174.170:1301

2019-02-11 17:58:17,988 DEBG 'start-script' stdout output:
Mon Feb 11 17:58:17 2019 SENT CONTROL [cz-prg-002.mullvad.net]: 'PUSH_REQUEST' (status=1)

2019-02-11 17:58:22,130 DEBG 'start-script' stdout output:
Mon Feb 11 17:58:22 2019 SENT CONTROL [cz-prg-002.mullvad.net]: 'PUSH_REQUEST' (status=1)

2019-02-11 17:58:22,166 DEBG 'start-script' stdout output:
Mon Feb 11 17:58:22 2019 PUSH: Received control message: 'PUSH_REPLY,dhcp-option DNS xx redirect-gateway def1 bypass-dhcp,route-ipv6 0000::/2,route-ipv6 4000::/2,route-ipv6 8000::/2,route-ipv6 C000::/2,comp-lzo no,route-gateway xx,topology subnet,socket-flags TCP_NODELAY,ifconfig-ipv6 fdda:d0d0:cafe:1301::1007/64 fdda:d0d0:cafe:1301::,ifconfig xx 255.255.0.0,peer-id 7,cipher AES-256-GCM'
Mon Feb 11 17:58:22 2019 Pushed option removed by filter: 'route-ipv6 0000::/2'
Mon Feb 11 17:58:22 2019 Pushed option removed by filter: 'route-ipv6 4000::/2'
Mon Feb 11 17:58:22 2019 Pushed option removed by filter: 'route-ipv6 8000::/2'
Mon Feb 11 17:58:22 2019 Pushed option removed by filter: 'route-ipv6 C000::/2'

2019-02-11 17:58:22,166 DEBG 'start-script' stdout output:
Mon Feb 11 17:58:22 2019 Pushed option removed by filter: 'ifconfig-ipv6 fdda:d0d0:cafe:1301::1007/64 fdda:d0d0:cafe:1301::'
Mon Feb 11 17:58:22 2019 OPTIONS IMPORT: compression parms modified
Mon Feb 11 17:58:22 2019 OPTIONS IMPORT: --socket-flags option modified
Mon Feb 11 17:58:22 2019 NOTE: setsockopt TCP_NODELAY=1 failed
Mon Feb 11 17:58:22 2019 OPTIONS IMPORT: --ifconfig/up options modified
Mon Feb 11 17:58:22 2019 OPTIONS IMPORT: route options modified
Mon Feb 11 17:58:22 2019 OPTIONS IMPORT: route-related options modified
Mon Feb 11 17:58:22 2019 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Mon Feb 11 17:58:22 2019 OPTIONS IMPORT: peer-id set
Mon Feb 11 17:58:22 2019 OPTIONS IMPORT: adjusting link_mtu to 1624
Mon Feb 11 17:58:22 2019 OPTIONS IMPORT: data channel crypto options modified
Mon Feb 11 17:58:22 2019 Data Channel: using negotiated cipher 'AES-256-GCM'
Mon Feb 11 17:58:22 2019 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Mon Feb 11 17:58:22 2019 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Mon Feb 11 17:58:22 2019 ROUTE_GATEWAY 192.168.1.1/255.255.255.0 IFACE=eth0 HWADDR=02:42:c0:a8:01:47

2019-02-11 17:58:22,166 DEBG 'start-script' stdout output:
Mon Feb 11 17:58:22 2019 TUN/TAP device tun0 opened
Mon Feb 11 17:58:22 2019 TUN/TAP TX queue length set to 100
Mon Feb 11 17:58:22 2019 do_ifconfig, tt->did_ifconfig_ipv6_setup=0
Mon Feb 11 17:58:22 2019 /usr/bin/ip link set dev tun0 up mtu 1500

2019-02-11 17:58:22,167 DEBG 'start-script' stdout output:
Mon Feb 11 17:58:22 2019 /usr/bin/ip addr add dev tun0 xx/16 broadcast xx

2019-02-11 17:58:22,168 DEBG 'start-script' stdout output:
Mon Feb 11 17:58:22 2019 /root/openvpnup.sh tun0 1500 1552 xx  255.255.0.0 init

2019-02-11 17:58:22,169 DEBG 'start-script' stdout output:
Mon Feb 11 17:58:22 2019 /usr/bin/ip route add xx via 192.168.1.1

2019-02-11 17:58:22,170 DEBG 'start-script' stdout output:
Mon Feb 11 17:58:22 2019 /usr/bin/ip route add 0.0.0.0/1 via xx

2019-02-11 17:58:22,171 DEBG 'start-script' stdout output:
Mon Feb 11 17:58:22 2019 /usr/bin/ip route add 128.0.0.0/1 via xx

2019-02-11 17:58:22,172 DEBG 'start-script' stdout output:
Mon Feb 11 17:58:22 2019 Initialization Sequence Completed

2019-02-11 17:58:22,267 DEBG 'privoxy-script' stdout output:
[info] Configuring Privoxy...

2019-02-11 17:58:22,273 DEBG 'watchdog-script' stdout output:
[info] qBittorrent listening interface IP 0.0.0.0 and VPN provider IP xx different, marking for reconfigure

2019-02-11 17:58:22,276 DEBG 'watchdog-script' stdout output:
[info] qBittorrent not running

2019-02-11 17:58:22,350 DEBG 'privoxy-script' stdout output:
[info] All checks complete, starting Privoxy...

2019-02-11 17:58:22,359 DEBG 'privoxy-script' stderr output:
2019-02-11 17:58:22.359 1469b8052100 Info: Privoxy version 3.0.26
2019-02-11 17:58:22.359 1469b8052100 Info: Program name: /usr/bin/privoxy

2019-02-11 17:58:22,466 DEBG 'start-script' stdout output:
[info] Successfully retrieved external IP address xx
xx
xx
xx

2019-02-11 17:58:22,466 DEBG 'start-script' stdout output:
/root/getvpnextip.sh: line 58: 216.239.34.10: command not found

2019-02-11 17:58:22,467 DEBG 'start-script' stdout output:
/root/getvpnextip.sh: line 59: 216.239.36.10: command not found

2019-02-11 17:58:22,467 DEBG 'start-script' stdout output:
/root/getvpnextip.sh: line 60: 216.239.38.10: command not found

2019-02-11 17:58:22,479 DEBG 'watchdog-script' stdout output:
[info] Removing session lock file (if it exists)...

2019-02-11 17:58:22,479 DEBG 'watchdog-script' stdout output:
[info] Attempting to start qBittorrent...

2019-02-11 17:58:23,062 DEBG 'watchdog-script' stdout output:
[info] qBittorrent process started
[info] Waiting for qBittorrent process to start listening on port 8080...

2019-02-11 17:58:23,062 DEBG 'watchdog-script' stdout output:
[info] qBittorrent process started
[info] Waiting for qBittorrent process to start listening on port 8080..

 

Share this post


Link to post

How do i use an ovpn config file from my VPN provider? I do not use PIA or any other that are listed and will have to use custom. Will I have to use something like this https://ronnieroller.com/unraid#setup-notes_vpn-setup? I have been using a windows machine with the VPN app but would like to move everything over to docker. Thanks.

Share this post


Link to post
2 minutes ago, TristBella said:

How do i use an ovpn config file from my VPN provider? I do not use PIA or any other that are listed and will have to use custom. Will I have to use something like this https://ronnieroller.com/unraid#setup-notes_vpn-setup? I have been using a windows machine with the VPN app but would like to move everything over to docker. Thanks.

see the newbie vpn guide heading in the following link:-
 

https://forums.unraid.net/topic/44108-support-binhex-general/

 

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now