16 minutes ago, PSteward said:

Hello!

 

I tried using this container as a network for another however it appears the it blocks the LAN network (can ping items but not get to them). For example I put Lidarr  to use the container as it's network (which works) but now Lidarr cannot access the local clients. I tried "curl http://LAN_address:port" and it times out - is this normal?

 

Thanks!

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

 

In particular Q24 and 25, but the whole document is worth reading.

Yep that was it, Q24-27 are on point.
I used localhost to access the qbitorrent hosting the VPN for this docker and then added the ports for my external qbittorrent (on a different machine).

 

Thanks!

Edited November 11, 20232 yr by PSteward

I'm having a few issues and not sure where else to look.. i've had it working fine and recently have gone through an ISP and router/firewall change.

 

My current situation is i cannot get the VPN to work on my city fibre based connection, over LTE it is working fine. I have both connections configured in sdwan and simply enabling a rule that steers traffic originating from my unraid server to the VPN servers IP over LTE, makes the VPN and client download correctly. Disabling this rule on my firewall so that it takes the default connection (city fibre) results in the docker starting up but items are forever stalled. No changes made to the docker settings between working and not working besides enabling/disabling the rule. The tunnels seem both up and connected as far as i can see through the interfaces although when its not working i get alot of TX dropped. Attached the log when its not working on city fibre. Any help or pointers greatly apprieciated.

When running on LTE and working normally

sh-5.1# ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 172.17.0.3  netmask 255.255.0.0  broadcast 172.17.255.255
        ether 02:42:ac:11:00:03  txqueuelen 0  (Ethernet)
        RX packets 22264  bytes 3781648 (3.6 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 22869  bytes 27389758 (26.1 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 1004  bytes 145782 (142.3 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1004  bytes 145782 (142.3 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

tun0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST>  mtu 1500
        inet 10.7.2.5  netmask 255.255.255.0  destination 10.7.2.5
        unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  txqueuelen 500  (UNSPEC)
        RX packets 21061  bytes 1730496 (1.6 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 39657  bytes 24770884 (23.6 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

 

When running on city fibre and not working

sh-5.1# ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 172.17.0.3  netmask 255.255.0.0  broadcast 172.17.255.255
        ether 02:42:ac:11:00:03  txqueuelen 0  (Ethernet)
        RX packets 926  bytes 270200 (263.8 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 871  bytes 127203 (124.2 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 9  bytes 1235 (1.2 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 9  bytes 1235 (1.2 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

tun0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST>  mtu 1500
        inet 10.7.2.5  netmask 255.255.255.0  destination 10.7.2.5
        unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  txqueuelen 500  (UNSPEC)
        RX packets 723  bytes 161632 (157.8 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 980  bytes 73342 (71.6 KiB)
        TX errors 0  dropped 2089 overruns 0  carrier 0  collisions 0

 

 

 

cityfibre log.txt

Edited November 12, 20232 yr by Gammawolf

Invalid User or Password (even though I changed nothing overnight). Is there a way to recover (or change) the password within Unraid/Maybe a txt file?

3 minutes ago, MadMan204 said:

Invalid User or Password (even though I changed nothing overnight). Is there a way to recover (or change) the password within Unraid/Maybe a txt file?

looks relevant

1 hour ago, MadMan204 said:

Invalid User or Password (even though I changed nothing overnight). Is there a way to recover (or change) the password within Unraid/Maybe a txt file?

I downgraded back to the previous version to get it working immediately, which was successful.

To be clear, from qbittorrent news post:-

 

Quote

qBittorrent v4.6.1 was released.
The most important change has to do with WebUI. It affects users that haven't set their own credentials and are use the default ones. Those will not be accepted now and qBittorrent will generate a random password and output it in the console for you to use. Then you can login and configure a password.

so if adminadmin doesnt work then you know the reason why, check supervisrod.log file and use the randomised password, or better yet stop using the default password and set one.

2 hours ago, binhex said:

To be clear, from qbittorrent news post:-

 

so if adminadmin doesnt work then you know the reason why, check supervisrod.log file and use the randomised password, or better yet stop using the default password and set one.

Does not show up in supervisrod.log file for me... ill have to downgrade and fix creds, then update again. also, i just seem to get a white page on dockerhub... what tag should i downgrade to fix this temporarily?

Edited November 22, 20232 yr by lavavex
added context/question

54 minutes ago, lavavex said:

what tag should i downgrade to fix this temporarily?

Looks like 4.6.0-1-01 was the most recent previous version.

I tried to search through thread but couldn't find a match. Is 'torrent creator' removed from qbittorentvpn or am I just blind? I'm trying to upload some stuff to a private torrent group but can't create anything.

6 hours ago, SmoothBrain said:

I tried to search through thread but couldn't find a match. Is 'torrent creator' removed from qbittorentvpn or am I just blind? I'm trying to upload some stuff to a private torrent group but can't create anything.

it doesnt exist in qbittorrent-nox (web ui) only the gui version of qbittorrent has the creator

Man, first the Problem with the password, which i got fixed through downgrading back to 4.6.0-1-01. Changed to my own authentication, updated and now Sonarr and Radarr say they got no authority through neither the new nor the old authentication. Even deleted the client settings in sonarr and set it up new, didn'Ät workt either. Downgrading back and Sonarr and Radarr works just fine with the new Authentication. Anyone1 who had the same problem and knows how to get the newest Qbit Version running with Sonarr/Radarr?

35 minutes ago, Badtz2 said:

Man, first the Problem with the password, which i got fixed through downgrading back to 4.6.0-1-01. Changed to my own authentication, updated and now Sonarr and Radarr say they got no authority through neither the new nor the old authentication. Even deleted the client settings in sonarr and set it up new, didn'Ät workt either. Downgrading back and Sonarr and Radarr works just fine with the new Authentication. Anyone1 who had the same problem and knows how to get the newest Qbit Version running with Sonarr/Radarr?

For me radarr and sonarr picked up my changed password no problem.

The steps I took were:
-Edited the binhex/arch-qbittorrentvpn container: Changed the Repository field to binhex/arch-qbittorrentvpn:4.6.0-1-01 and applied the changes.
-Successfully downloaded and started the older version.
-Logged in using 'admin' and 'adminadmin'. In Settings > WebUI, added a new user, replacing the admin account, and saved the changes.
-Edited the binhex/arch-qbittorrentvpn container again: Changed the Repository field back to binhex/arch-qbittorrentvpn and applied the changes.
-Updated Sonarr and Radarr with the new username and password accordingly.

Another option would be to whitelist 172.17.0.0/24 if you're comfortable with that.

Edited November 22, 20232 yr by cloudyb

21 minutes ago, Badtz2 said:

Anyone1 who had the same problem and knows how to get the newest Qbit Version running with Sonarr/Radarr?

Yeah, I checked mine after I saw your post and had the same issue. I was able to get mine working by whitelisting the local network in the qbittorrent settings>webui. This avoids authentication.

Same issue. Thanks to @cloudyb and the instructions I was able to get back to a working state. 

Hi,

 

I am new to Unraid and having trying to install qBittorrentvpn using ProtonVPN's wireguard config but I can't seem to be able to get it to work. 

 

Initially I had filled out the username and password sections/values and selected ProntonVPN from the providers list but it gave me the same results when I leave them blank.

 

I figured the information would be grabbed from the provided config file I downloaded from Pronton's site. 

 

Here is the log I am getting (I removed the date+time info):

-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A OUTPUT -o lo -j ACCEPT
-A OUTPUT -o wg0 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A OUTPUT -d 138.199.7.129/32 -o eth0 -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 wg0 -j ACCEPT

xxxxxxxxxxxxxxxx:35,660 DEBG 'start-script' stdout output:
--------------------

xxxxxxxxxxxxxxxx:35,660 DEBG 'start-script' stdout output:
[info] Attempting to bring WireGuard interface 'up'...

xxxxxxxxxxxxxxxx:35,664 DEBG 'start-script' stderr output:
Warning: `/config/wireguard/wg0.conf' is world accessible

xxxxxxxxxxxxxxxx:35,668 DEBG 'start-script' stderr output:
[#] ip link add wg0 type wireguard

xxxxxxxxxxxxxxxx:35,669 DEBG 'start-script' stderr output:
[#] wg setconf wg0 /dev/fd/63

xxxxxxxxxxxxxxxx:35,670 DEBG 'start-script' stderr output:
[#] ip -4 address add 10.2.0.2/32 dev wg0

xxxxxxxxxxxxxxxx:35,673 DEBG 'start-script' stderr output:
[#] ip link set mtu 1420 up dev wg0

xxxxxxxxxxxxxxxx:35,674 DEBG 'start-script' stderr output:
[#] resolvconf -a wg0 -m 0 -x

xxxxxxxxxxxxxxxx:35,679 DEBG 'start-script' stderr output:
could not detect a useable init system

xxxxxxxxxxxxxxxx:35,697 DEBG 'start-script' stderr output:
[#] wg set wg0 fwmark 51820

xxxxxxxxxxxxxxxx:35,697 DEBG 'start-script' stderr output:
[#] ip -4 route add 0.0.0.0/0 dev wg0 table 51820

xxxxxxxxxxxxxxxx:35,698 DEBG 'start-script' stderr output:
[#] ip -4 rule add not fwmark 51820 table 51820

xxxxxxxxxxxxxxxx:35,699 DEBG 'start-script' stderr output:
[#] ip -4 rule add table main suppress_prefixlength 0

xxxxxxxxxxxxxxxx:35,701 DEBG 'start-script' stderr output:
[#] sysctl -q net.ipv4.conf.all.src_valid_mark=1

xxxxxxxxxxxxxxxx:35,701 DEBG 'start-script' stderr output:
[#] iptables-restore -n

xxxxxxxxxxxxxxxx:35,703 DEBG 'start-script' stderr output:
[#] '/root/wireguardup.sh'

xxxxxxxxxxxxxxxx:42,997 DEBG 'start-script' stdout output:
[info] Attempting to get external IP using 'http://checkip.amazonaws.com'...

xxxxxxxxxxxxxxxx:43,436 DEBG 'start-script' stdout output:
[info] Successfully retrieved external IP address 138.199.7.130

xxxxxxxxxxxxxxxx:43,437 DEBG 'start-script' stdout output:
[info] WireGuard interface 'up'

xxxxxxxxxxxxxxxx:43,437 DEBG 'start-script' stdout output:
[info] Script started to assign incoming port for 'protonvpn'

xxxxxxxxxxxxxxxx:45,448 DEBG 'start-script' stdout output:
[info] ProtonVPN username 'vpn username' does not contain the suffix '+pmp' and therefore is not enabled for port forwarding, skipping port forward assignment...
[info] Script finished to assign incoming port

xxxxxxxxxxxxxxxx:45,449 DEBG 'start-script' stderr output:
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]

 

Any help getting this fixed would be highly appreciated.

6 hours ago, cloudyb said:

For me radarr and sonarr picked up my changed password no problem.

The steps I took were:
-Edited the binhex/arch-qbittorrentvpn container: Changed the Repository field to binhex/arch-qbittorrentvpn:4.6.0-1-01 and applied the changes.
-Successfully downloaded and started the older version.
-Logged in using 'admin' and 'adminadmin'. In Settings > WebUI, added a new user, replacing the admin account, and saved the changes.
-Edited the binhex/arch-qbittorrentvpn container again: Changed the Repository field back to binhex/arch-qbittorrentvpn and applied the changes.
-Updated Sonarr and Radarr with the new username and password accordingly.

Another option would be to whitelist 172.17.0.0/24 if you're comfortable with that.

 

Did the exact same steps, but i got into the problem... But we wouldn't have UnRaid builds if we wouldn't like tinkering, right? x) 

 

6 hours ago, wgstarks said:

Yeah, I checked mine after I saw your post and had the same issue. I was able to get mine working by whitelisting the local network in the qbittorrent settings>webui. This avoids authentication.

Thanks both of you! Guess i'll be whitelisting then or i'll just stay on 4.6.0 for now, not sure yet.

2 hours ago, iZChae said:

Any help getting this fixed would be highly appreciated.

Edit your docker config and add ‘+pmp’ to your email. 
eg [email protected] becomes [email protected]

 

supervisord.logIm going insane here

 

- Subnet added 

- 10.0.0.0

 

-VPN added mullvad with wireguard

-files are in 

 

- Clean install 

Can reach UI without VPN but not with. 

 

Any Suggestions? 

 

-------------------------

 

Solved it by adding the IPtable from 

documentation/docker/faq/vpn.md at master · binhex/documentation · GitHub

Edited November 22, 20232 yr by hefty-denunciation2920

1 hour ago, hefty-denunciation2920 said:

- Subnet added 

- 10.0.0.0

Wrong format. It should be 10.0.0.0/24 or whatever is correct for the network you are logging in from. If it's for radarr/sonarr you can grab it from their settings.

1 hour ago, SmoothBrain said:

Edit your docker config and add ‘+pmp’ to your email. 
eg [email protected] becomes [email protected]

 

Wow, I would've never thought that something that simple would be the solution. It is working now but when I try to login with the default username/password for qBittorrent, I am getting an error saying the username/password is incorrect. Any solutions for that?

 

Thank you in advance for all the help.

 

2 hours ago, iZChae said:

Wow, I would've never thought that something that simple would be the solution. It is working now but when I try to login with the default username/password for qBittorrent, I am getting an error saying the username/password is incorrect. Any solutions for that?

 

Thank you in advance for all the help.

 

 

10 hours ago, cloudyb said:

For me radarr and sonarr picked up my changed password no problem.

The steps I took were:
-Edited the binhex/arch-qbittorrentvpn container: Changed the Repository field to binhex/arch-qbittorrentvpn:4.6.0-1-01 and applied the changes.
-Successfully downloaded and started the older version.
-Logged in using 'admin' and 'adminadmin'. In Settings > WebUI, added a new user, replacing the admin account, and saved the changes.
-Edited the binhex/arch-qbittorrentvpn container again: Changed the Repository field back to binhex/arch-qbittorrentvpn and applied the changes.
-Updated Sonarr and Radarr with the new username and password accordingly.

Another option would be to whitelist 172.17.0.0/24 if you're comfortable with that.

 

1 hour ago, wgstarks said:

 

 

Thank you! 🖤

FYI regards no password shown in the log, its a qbittorrent bug - https://github.com/binhex/arch-qbittorrentvpn/issues/208#issuecomment-1824091412

stupid me for not checking this site first... I nuked my docker thinking I changed my password and forgot, only then I decided to look here...