1 hour ago, emkab said:

I just finished setting it up with nordvpn, but i cant access the webui with vpn on.

 

Just had this issue also. Upon checking the supervisord log file as mentioned above by @JonathanM my error was.

 

FATAL: Module iptable_mangle not found in directory

 

The fix for me was this. 

 

[info] unRAID/Ubuntu users: Please attempt to load the module by executing the following on your host: '/sbin/modprobe iptable_mangle' within unraid terminal.

 

Thank you for directing me to supervisord log file I was only checking the Docker container logs.

 

26 minutes ago, RichardA said:

 

Just had this issue also. Upon checking the supervisord log file as mentioned above by @JonathanM my error was.

 

FATAL: Module iptable_mangle not found in directory

 

The fix for me was this. 

 

[info] unRAID/Ubuntu users: Please attempt to load the module by executing the following on your host: '/sbin/modprobe iptable_mangle' within unraid terminal.

 

Thank you for directing me to supervisord log file I was only checking the Docker container logs.

 

didn't work, but i don't think anything will as i just found out nordvpn does not support port forwarding.. whoop.

I cant get rutorrent-vpn or qbittorrent-vpn to run with the vpn enabled anymore. Rtorrent worked for a few days then all of a sudden stopped. Can I get some help please?

Log

https://pastebin.com/nimf2EqN

Edited May 12, 20224 yr by mason1171

I have qBittorrent run a script upon download completion, so it runs from within the container. In this script I can `curl http://<server ip>:<container port>` of one container without issues, but for another one, it fails to connect and times out. If I replace `<server ip>` (e.g. 10.0.1.2) with `<internal container ip>` (e.g. 172.19.0.3) it works fine for both containers.

Does anyone know why that is? All containers are on the same custom Docker network.

 

Also, `curl http://<container name>:<container port>` works from within all containers except binhex-qbittorrentvpn, where I get `Could not resolve host: <container name>`. Any way to get container name resolution working?

On 4/20/2022 at 8:37 AM, veri745 said:

 

Have you been able to get RSS feeds to load?  I just installed  this docker image and I've been searching for why RSS feeds are not loading.  I haven't done anything with nginx yet

Yes, it works. 
In nginx, in network type , I put none and in additional parameters: --net=container:binhex-qbittorrentvpn

12 hours ago, intensitydriver said:

Hi folks

 

I am trying to install NordVPN docker with Qbittorrent.

When deploying stack (using swarm mode,3) it deploys without problems but looking through the logs shows this:

"iptables v1.8.2 (legacy): can't initialize iptables table `filter': Permission denied (you must be root)

Perhaps iptables or your kernel needs to be upgraded."

The VPN service cannot connect because of this problem.

My OMV5 is all updated and runnign without errors.

 

 

Anyone has a clue what this is about? I have found a similiar problem on various other distros but not a solution on OMV5 (if it differs).

Thanks!

no idea how you do this with OMV5 or swarm mode,3, but you need to specify the following additional permission:-
 

    --cap-add=NET_ADMIN

 

Hi everyone,

 

I've been using this docker for a few months, works like a charm but I have one issue that I've been trying to fix ever since I installed it.

 

My issue is pretty simple, after a system reboot I always need to reapply my settings in the web ui, so changing the username/password, allowed ips, etc.

 

Anyone would know how to apply my settings permanently?

 

Thanks.

42 minutes ago, Uncleclaude said:

after a system reboot I always need to reapply my settings

Sounds like you don't have appdata mapped to actual storage. Post docker run

6 minutes ago, trurl said:

Sounds like you don't have appdata mapped to actual storage. Post docker run

Just checked, the config folder is pointing to the one in appdata. Also this issue only happens after a full system restart, if I stop and start back only the Qbittorrent container my config is still there.
 

Anyone know if the latest docker image release addresses the RSS feed issue?

Running round in circles here. Does anyone have any advice on how to reliably test port forwarding?

I've been used to testing via websites like (yougetsignal.com) but the tests are never successful on my Windows machine.

On the box running qbitorrentvpn the client also is not indicating a correctly fowarded port.

 

I use wevpn and their support are claiming port forwarding is working fine for them when testing, but all my clients I've tested it doesn't work.

 

I even tried a port foward outside the VPN to check if it was the router, but that works fine. 

On 5/21/2022 at 1:07 PM, Uncleclaude said:

Just checked, the config folder is pointing to the one in appdata. Also this issue only happens after a full system restart, if I stop and start back only the Qbittorrent container my config is still there.
 

 

I can confirm that I experience this issue as well. Haven't found a workaround beyond doing a backup/restore of my appdata folder. Not entirely sure why it happens.

Is there any step by step setup guide to getting this container working with:

 

mullvad vpn

 

wireguard

 

?

On 5/29/2022 at 12:17 AM, erfly7 said:

Is there any step by step setup guide to getting this container working with:

 

mullvad vpn

 

wireguard

 

?

 

Hello there.

 

1. Go to https://mullvad.net/sv/account/#/wireguard-config/

   and make your config file. You need to login to make you Wireguard key

   Download your configuration

 

2. Docker: 

    Edit the container . ( i changed from nordvpn to mullvad and change this settings. )

    Container Variable: VPN_USER           "Your wireguard key here"

    Container Variable: VPN_PASS           "Leave it blank"

    Container Variable: VPN_CLIENT        "Wireguard"

 

3. restart the docker container. ( This will create floder "wireguard" in appdata/binhex-qbittorrentvpn/wireguard

 

4. Copy the file in the zip file you got from Mullvad to appdata/binhex-qbittorrentvpn/wireguard

    (can be more files in that zip file you only need one)

 

5. Restart it again and it should now work.

 

Hope it helps.

    

 

 

Thanks figured it out

 

Finally started, had one number in LAN_Network wrong

 

1. How do I know the VPN is working?

2. Do I have change the download location in Qbittorent to /data?

17 hours ago, erfly7 said:

Thanks figured it out

 

Finally started, had one number in LAN_Network wrong

 

1. How do I know the VPN is working?

2. Do I have change the download location in Qbittorent to /data?

1. go to check the logg.

   In there you vill have a line like this "[info] Successfully retrieved external IP address 123.123.123.123 "

   thats says your ext ip adress is. it shuld not be the same as your computers external ip adress. EDIT: just rememberd you can che the IPs here http://checkmyip.torrentprivacy.com/

 

2. If i remember correct you need to change it. Do it here.  Your is probably /data

 

 

Edited May 31, 20224 yr by Fredde

Hello, 

 

Is it possible to use https://draculatheme.com/qbittorrent Dark mode on this container?

 

When i use the instructions on the site i get this error message: "Unacceptable file type, only regular file is allowed."

and cant use the webUI at all 

 

hope you can help!

 

I'm having some trouble getting the webui to work. Heres what the logs show with DEBUG enabled:

2022-06-02 10:53:11,482 DEBG 'watchdog-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...

2022-06-02 10:53:11,609 DEBG 'watchdog-script' stdout output:
[debug] DNS operational, we can resolve name 'www.google.com' to address '172.253.115.103 172.253.115.99 172.253.115.105 172.253.115.104 172.253.115.147 172.253.115.106'

2022-06-02 10:53:11,610 DEBG 'watchdog-script' stdout output:
[debug] Waiting for iptables chain policies to be in place...

2022-06-02 10:53:11,620 DEBG 'watchdog-script' stdout output:
[debug] iptables chain policies are in place

2022-06-02 10:53:11,625 DEBG 'watchdog-script' stdout output:
[debug] VPN incoming port is 42119
[debug] qBittorrent incoming port is 42119
[debug] VPN IP is x.x.x.x
[debug] qBittorrent IP is x.x.x.x

The VPN IP and qBittorrent IP are identical but I redacted them just incase. These same lines are output to the log every 30 seconds or so. Not sure where to go from here 🤷‍♂️

 

Hello again...

 

Same issue as @SxC97

 

I cant access the local UI, heres my pastebin: https://pastebin.com/raw/SFx6MG75

 

edit: seems to be only when vpn is enabled. If I disable VPN it works fine.

 

LAN is correct(192.168.10.0/24)

 

Edited June 2, 20224 yr by WenzelComputing

On 5/31/2022 at 2:25 PM, Jarno said:

Hello, 

 

Is it possible to use https://draculatheme.com/qbittorrent Dark mode on this container?

 

When i use the instructions on the site i get this error message: "Unacceptable file type, only regular file is allowed."

and cant use the webUI at all 

 

hope you can help!

 

 

 

you are using the wrong location. need to make sure the file location is correct ie: /data/Torrents/Theme/themelocationhere

 

Follow this guide for themes: 

 

5 hours ago, WenzelComputing said:

Hello again...

 

Same issue as @SxC97

 

I cant access the local UI, heres my pastebin: https://pastebin.com/raw/SFx6MG75

 

edit: seems to be only when vpn is enabled. If I disable VPN it works fine.

 

LAN is correct(192.168.10.0/24)

 

I looked through @WenzelComputing pastebin and can confirm that my logs look almost identical. I also followed the instructions in Q2 and Q4 of the Docker VPN Github page. I executed 

/sbin/modprobe iptable_mangle

on my Unraid machine and made sure my LAN_NETWORK was properly configured.

On 6/2/2022 at 7:38 PM, SxC97 said:

I looked through @WenzelComputing pastebin and can confirm that my logs look almost identical. I also followed the instructions in Q2 and Q4 of the Docker VPN Github page. I executed 

/sbin/modprobe iptable_mangle

on my Unraid machine and made sure my LAN_NETWORK was properly configured.

i gave up on waiting for an official fix. here is my unofficial fix: 

 

go back to 4.3.9 version.

 

new version is completely broken.

Edited June 4, 20224 yr by WenzelComputing

Hello. daily or twice a day I keep having to restart the docker because it loses network. i've tried looking for others with this same issue with no luck.

 

here are the logs

 

2022-06-07 01:56:21,562 DEBG 'start-script' stdout output:
2022-06-07 01:56:21 Restart pause, 5 second(s)

2022-06-07 01:56:26,562 DEBG 'start-script' stdout output:
2022-06-07 01:56:26 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2022-06-07 01:56:26,563 DEBG 'start-script' stdout output:
2022-06-07 01:56:26 TCP/UDP: Preserving recently used remote address: [AF_INET]xxx.xxx.xxx.xxx:1194
2022-06-07 01:56:26 Socket Buffers: R=[212992->212992] S=[212992->212992]
2022-06-07 01:56:26 UDP link local: (not bound)
2022-06-07 01:56:26 UDP link remote: [AF_INET]173xxx.xxx.xxx:1194
2022-06-07 01:56:26 write UDP []: Network is unreachable (code=101)
2022-06-07 01:56:26 Network unreachable, restarting
2022-06-07 01:56:26 SIGHUP[soft,network-unreachable] received, process restarting

2022-06-07 01:56:26,564 DEBG 'start-script' stdout output:
2022-06-07 01:56:26 WARNING: file 'credentials.conf' is group or others accessible
2022-06-07 01:56:26 OpenVPN 2.5.6 [git:makepkg/e8df2e64d6f817e6+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Mar 16 2022
2022-06-07 01:56:26 library versions: OpenSSL 1.1.1o  3 May 2022, LZO 2.10

 

On 6/3/2022 at 9:09 PM, WenzelComputing said:

i gave up on waiting for an official fix. here is my unofficial fix: 

 

go back to 4.3.9 version.

 

new version is completely broken.

I have the same issue and have followed the same troubleshooting steps. Unfortunately I cant get it to working. How did you install the older version?

15 minutes ago, Dexm57 said:

I have the same issue and have followed the same troubleshooting steps. Unfortunately I cant get it to working. How did you install the older version?

You can install any tagged version by adding a colon and the tag number after the name in the repository field in docker configuration.