2 hours ago, BusterBrawls said:

Recently logged errors:

"2020-11-09 07:35:11,796 DEBG 'start-script' stderr output:
parse error: Invalid numeric literal at line 4, column 0"

cosmetic issue caused by pia putting crap in their json

 

2 hours ago, BusterBrawls said:

"2020-11-09 02:32:47,909 DEBG 'watchdog-script' stdout output:
[warn] Incoming port site 'https://portchecker.co/' failed to web scrape, marking as failed"

known issue, need to fix up due to change on website - again non issue.

 

2 hours ago, BusterBrawls said:

I can't keep qbittorrent open for a couple of days before it will eventually close on it's own.

can you explain in more detail what you mean by the above, close what, webui?, vpn?, incoming port?

At least three times in less than 2 weeks I have woken up in the morning and found that the Docker container had stopped. The last collection of logs (supervisord.log) before I restarted the container is here:

 

2020-11-09 02:54:30,752 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '44976'

2020-11-09 03:00:07,108 WARN received SIGTERM indicating exit request
2020-11-09 03:00:07,108 DEBG killing watchdog-script (pid 155) with signal SIGTERM
2020-11-09 03:00:07,108 INFO waiting for start-script, watchdog-script to die
2020-11-09 03:00:08,109 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 22428397286640 for <Subprocess at 22428394042608 with name watchdog-script in state STOPPING> (stdout)>
2020-11-09 03:00:08,109 DEBG fd 15 closed, stopped monitoring <POutputDispatcher at 22428397335984 for <Subprocess at 22428394042608 with name watchdog-script in state STOPPING> (stderr)>
2020-11-09 03:00:08,110 INFO stopped: watchdog-script (terminated by SIGTERM)
2020-11-09 03:00:08,110 DEBG received SIGCHLD indicating a child quit
2020-11-09 03:00:08,110 DEBG killing start-script (pid 154) with signal SIGTERM
2020-11-09 03:00:09,111 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22428393173920 for <Subprocess at 22428393173968 with name start-script in state STOPPING> (stdout)>
2020-11-09 03:00:09,111 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22428394041936 for <Subprocess at 22428393173968 with name start-script in state STOPPING> (stderr)>
2020-11-09 03:00:09,111 INFO stopped: start-script (terminated by SIGTERM)
2020-11-09 03:00:09,112 DEBG received SIGCHLD indicating a child quit

I would be happy to provide (or capture) any other logs necessary. 

Edited November 9, 20205 yr by BusterBrawls
added the name of the log file

2 minutes ago, BusterBrawls said:

03:00:07

interesting time for it to stop, got a CA backup going at 3am by any chance?.

In fact, I do have a CA backup that starts at 3AM Monday mornings (Weekly). The containers usually restart after the backup and all others restart as expected. 

 

I'd be willing to believe this is responsible for one or two of the shutdowns. I'd also be willing to believe the switch to wireguard caused a couple issues until I got that updated. 

 

Looks like the issues are probably mine. The lack of restart is odd, but not necessarily a problem with the Docker image.

im using synology docker, how can i update to 4.2.5-1-12 without losing anything? my older version seems to not connect anymore

 

someone mentions docker pull, is that safe will i lose anything? what exactly is the command if i want version 4.2.5-1-12 , since im running sonnarr

 

-A INPUT -i lo -j ACCEPT
-A OUTPUT -o tun0 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A OUTPUT -o eth0 -p udp -m udp --dport 1198 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --dport 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 172.17.0.0/16 -d 192.168.1.0/24 -o eth0 -p tcp -j ACCEPT
-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A OUTPUT -o lo -j ACCEPT
2020-11-14 09:49:36,687 DEBG 'start-script' stdout output:
--------------------
2020-11-14 09:49:36,690 DEBG 'start-script' stdout output:
[info] Starting OpenVPN...
2020-11-14 09:49:36,884 DEBG 'start-script' stdout output:
Sat Nov 14 09:49:36 2020 WARNING: file 'credentials.conf' is group or others accessible
Sat Nov 14 09:49:36 2020 OpenVPN 2.4.6 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Apr 24 2018
Sat Nov 14 09:49:36 2020 library versions: OpenSSL 1.1.1a  20 Nov 2018, LZO 2.10
2020-11-14 09:49:36,885 DEBG 'start-script' stdout output:
[info] OpenVPN started
Sat Nov 14 09:49:36 2020 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
2020-11-14 09:49:36,886 DEBG 'start-script' stdout output:
Sat Nov 14 09:49:36 2020 TCP/UDP: Preserving recently used remote address: [AF_INET]66.115.145.199:1198
Sat Nov 14 09:49:36 2020 UDP link local: (not bound)
Sat Nov 14 09:49:36 2020 UDP link remote: [AF_INET]66.115.145.199:1198
2020-11-14 09:50:36,666 DEBG 'start-script' stdout output:
Sat Nov 14 09:50:36 2020 [UNDEF] Inactivity timeout (--ping-restart), restarting
2020-11-14 09:50:36,667 DEBG 'start-script' stdout output:
Sat Nov 14 09:50:36 2020 SIGHUP[soft,ping-restart] received, process restarting
Sat Nov 14 09:50:36 2020 WARNING: file 'credentials.conf' is group or others accessible
Sat Nov 14 09:50:36 2020 OpenVPN 2.4.6 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Apr 24 2018
Sat Nov 14 09:50:36 2020 library versions: OpenSSL 1.1.1a  20 Nov 2018, LZO 2.10
2020-11-14 09:50:41,667 DEBG 'start-script' stdout output:
Sat Nov 14 09:50:41 2020 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
2020-11-14 09:50:41,669 DEBG 'start-script' stdout output:
Sat Nov 14 09:50:41 2020 TCP/UDP: Preserving recently used remote address: [AF_INET]172.98.92.194:1198
Sat Nov 14 09:50:41 2020 UDP link local: (not bound)
Sat Nov 14 09:50:41 2020 UDP link remote: [AF_INET]172.98.92.194:1198

 

Edited November 14, 20205 yr by d3funct

I'm getting the same problem as @d3funct mentioned

How do I enable wireguard? My speeds with OVPN have been really slow every since around the time the nextgen servers came online.

 

The documentation says

Quote

If you wish to use WireGuard (defined via 'VPN_CLIENT' env var value )

 

But I do not have a VPN_CLIENT variable in the options?

 

It also does not tell me what I need to put into the variable if I made it manually?

 

Nor is there a place to put the server that I can see?

 

Is the wireguard version a different version then the normal container?

Edited November 15, 20205 yr by TexasUnraid

40 minutes ago, TexasUnraid said:

How do I enable wireguard? My speeds with OVPN have been really slow every since around the time the nextgen servers came online.

 

The documentation says

 

But I do not have a VPN_CLIENT variable in the options?

 

It also does not tell me what I need to put into the variable if I made it manually?

 

Nor is there a place to put the server that I can see?

 

Is the wireguard version a different version then the normal container?

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

 

Scroll down to Q21.

12 minutes ago, wgstarks said:

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

 

Scroll down to Q21.

Thanks, I looked at both the dockerhub and github pages linked from unraid and could not find that FAQ.

27 minutes ago, TexasUnraid said:

Thanks, I looked at both the dockerhub and github pages linked from unraid and could not find that FAQ.

It’s linked in the first post of this thread (sort of).

9 minutes ago, wgstarks said:

It’s linked in the first post of this thread (sort of).

Where?

 

I click the documentation link and then the qbittorrent and this is all that comes up, this is what I found before.

 

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

Edited November 15, 20205 yr by TexasUnraid

I got wireguard working, although I am wondering if it is possible to check that a port is open? I don't seem to be getting as many connections as I did with OVPN for some reason but I would need to do more back to back testing tomorrow to know for sure.

29 minutes ago, TexasUnraid said:

Where?

 

I click the documentation link and then the qbittorrent and this is all that comes up, this is what I found before.

 

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

It’s not the qbittorrent link. It’s the vpn docker link.

about my message, I did the changes using the questions 21 suggestions and everything back to work.

 

thanks

10 hours ago, wgstarks said:

It’s not the qbittorrent link. It’s the vpn docker link.

Good to know.

 

Still need to do some back to back testing but does wireguard have a lot higher overhead then OVPN?

 

With OVPN when it was working properly I would generally be able to get around 30-35MB/s on my 400-450mbit internet. In Netdata it would show I was using the full 400-450mbit for internet traffic so the differnce was the ovpn overhead.

 

With wireguard the overhead seems to be much higher, I see ~200-250mbit internet usage (which is better then the 150-200 I saw before) but qbittorrent was only showing around ~10-12MB download (about the same as before).

 

I will do some proper testing later with some torrents with more seeds so I know that seeds are not the bottleneck but the overhead is strange.

i did  a sudo docker pull binhex/arch-qbittorrentvpn:4.2.5-1-12
4.2.5-1-12: Pulling from binhex/arch-qbittorrentvpn
 

i copied the new certs and opvn config file from the openvpn-nextgen.vpn

 

im still getting this auth failed error all of a sudden now, i had this working for years before everything got updated 

 

i attached the log

 

 

supervisord.log

4 minutes ago, d3funct said:

im still getting this auth failed error all of a sudden now, i had this working for years before everything got updated 

Are you using the same credentials that you use to login to the PIA website? User name should start with a p.

You also need to insure that the password is less than 99 characters and alpha numeric.

im using the same login i have the past 4+ years ?

10 minutes ago, d3funct said:

im using the same login i have the past 4+ years ?

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

 

scroll down to Q16

i looked at that, everything looked ok, i restarted i switched to netherlands.ovpn, it connected but now it wont curl the port forwarding.. so then i switched back to berlin and it says auth failed.. now im restarting again..

attaching a new log

 

how do i know what version of the docker image my container is running? i pulled the 4.2.5 version but now under images its showing both... 

supervisord (1).log

Just wanted to say that I did some back to back speed testing via the privoxy and wireguard is indeed working and quite impressively I might say. Only seeing a ~10% overhead using speedtest.net vs no proxy.

 

Going to try a few linux ISO's in qbittorrent now to make sure it sees the speeds it should.

 

I wish there was an nzbget with VPN.

Edited November 15, 20205 yr by TexasUnraid

so i ran a new container and it worked right away.. lol i guess it was still running the old version? this new container i specified 4.2.5. at the bottom

 

 

docker run -d \
    --cap-add=NET_ADMIN \
    -p 6881:6881 \
    -p 6881:6881/udp \
    -p 8080:8080 \
    -p 8118:8118 \
    --name=qbittorrentvpn1 \
    -v /volume1/Torrents:/Torrents \
    -v /volume1/docker/data:/data \
    -v /volume1/docker/config:/config \
    -v /etc/localtime:/etc/localtime:ro \
    -e VPN_ENABLED=yes \
    -e VPN_USER=xxxx \
    -e VPN_PASS=xxxx \
    -e VPN_PROV=pia \
    -e VPN_CLIENT=openvpn \
    -e STRICT_PORT_FORWARD=yes \
    -e ENABLE_PRIVOXY=yes \
    -e LAN_NETWORK=192.168.1.0/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=1234 \
    -e DEBUG=false \
    -e WEBUI_PORT=8080 \
    -e UMASK=000 \
    -e PUID=1026 \
    -e PGID=100 \
    binhex/arch-qbittorrentvpn:4.2.5-1-12

 

Just an FYI to everyone if it's not here already.

 

I've tested the most recent version of radarr 3.0.0.4071 - aka ":nightly" (there probably is newer but on Saturday that was the version) and bittorrent 4.3.x aka ":latest" and the problems with importing are fixed.

 

This does NOT apply to radarr 0.2 which apparently will not be fixed for qbittorrent 4.3.x

You must stick with qbittorrent 4.2.5 if you are still on radarr 0.2

I assume, but haven't checked that this is also fixed on sonarr since they were both experiencing it and probably pulling the same code fix.

Edited November 16, 20205 yr by mooky
typink is hrad

I am on qbittorrent 4.3 and radarr 0.2.0.1504. Imports work perfectly. Nzbget on the other hand takes forever to import.

 

Is there a way to update to radarr v3? I am running the binhex container, I already updated to the V3 sonarr and it is much nicer but heard radarr is not ready yet?