I'm currently running 4.3.9-2-01. Mostly because the issues with earlier unraid version. 

 

Now I'm wondering about protonvpn port forward will work with this version of qbit? Or do I have to update to a later version? I know I read somewhere you can manuelly update the docker template and add Proton. But will this work? 

I have a multitude of dockers running on my server (mostly binhex torrent dockers), and after months of working fine I have had 1 specific docker just quit working for gui access. It's a qbittorrent docker and I can tell it is still doing everything else, but I just can't hit the gui anymore. No config changes, no duplicates on ports used, and I have done everything from reboot the docker, to remove the docker and pull down a new image, to doing a full server build upgrade from 6.12.11 -> 6.12.14 with nothing giving gui access back.

supervisord.log Command.txt

Hey there, im new to unraid and docker stuff. when i try to run the container i get the following error:
Cannot determine external IP address.
the container worked before the last update. even if im going back to the update it wont work anymore, im running unraid 7.0

Edited January 11, 20251 yr by Shizuqt

44 minutes ago, Shizuqt said:

Hey there, im new to unraid and docker stuff. when i try to run the container i get the following error:
Cannot determine external IP address.
the container worked before the last update. even if im going back to the update it wont work anymore, im running unraid 7.0

Attach your supervisord log and docker run command to your next post. Be sure to redact users/passwords.

I usually get a Stalled torrent when ever there is an update, and all I have to do is stop the docker container and start it again, sometimes 2-5 times before it works again. But since updating to unraid 7.0 this solution no longer works. Torrents stay stalled. 

I do use proton VPN. When running the "WG" command in the console it shows it's connected and the handshake happens every 2ish minutes. 

 

FYI, this may not even be related to unraid 7.0 since the torrent I'm trying to get "Silo Season 2 Ep 09" and many other torrents stalled even without any recent updates. This container has been very spotty over the years with VPN, having to stop and start it over and over again. 

 

To test, I just disabled the VPN option in the container settings and it started working again right away.

 

I think there is an issue with the VPN portions of the container. I use Proton VPN(paid) but using the Proton VPN option in the container never worked. I had to use the "custom" option to get it to work, but now, that no longer work either. 

 

I assume some work needs to be done on this container to work with Proton properly?

 

The moment I turned the VPN option from "Yes" to "No" the container worked fine.

 

I guess for those having issues, set the "Container Variable: VPN_ENABLED" to "No" until this is fixed.

 

I don't like having to do this, but qbittorrent is the best bittorent client when having over 200+ torrents running(I have over 700 at a time on a regular basis). Other clients lag and become unresponsive, so I hope this container is fixed for the VPN parts soon.

 

On 1/7/2025 at 10:54 AM, rogales said:

@binhex, I would like to ask, if there is a possibility to release QbittorrentVPN with implemented libtorrent 1.2.2.0 version?

Thank You.

bump?

19 hours ago, wgstarks said:

Attach your supervisord log and docker run command to your next post. Be sure to redact users/passwords.

Thank you but it appears that it fixed itself. Today i tried again and it was working magicly.

Hi,

  I am not sure if I am checking this correctly or not.  Does binhex-qbittorrentvpn support health checks?  I am getting "null" when I check using the docker inspect command (docker inspect --format='{{json .State.Health}}' binhex-qbittorrentvpn).

 

I want to trigger some other containers once it is healthy

 

Thanks

 

Hello everyone,
my system ran without any problems until yesterday evening. Today I logged in and could not see any traffic (I upgraded to 7.0.0. in the meantime, but did not check the torrent function directly afterwards). After restarting the container, it is shown as started in the Unraid interface, but the WebUI is no longer accessible.I have tried to fix the warning ‘Warning: `/config/wireguard/wg0.conf’ is world accessible’, but no matter what I do with restarting the container, the rights for the wg0.conf are set to “-rwxrwxr-x” again, even when deleting the perms.txt.

I hope the attached data is not too redacted. I hope you can help me and thank you in advance.

 

Command execution.txtsupervisord.log

Edited January 12, 20251 yr by aku_pod
attachments moved to the end of post

1 hour ago, aku_pod said:

Hello everyone,
my system ran without any problems until yesterday evening. Today I logged in and could not see any traffic (I upgraded to 7.0.0. in the meantime, but did not check the torrent function directly afterwards). After restarting the container, it is shown as started in the Unraid interface, but the WebUI is no longer accessible.I have tried to fix the warning ‘Warning: `/config/wireguard/wg0.conf’ is world accessible’, but no matter what I do with restarting the container, the rights for the wg0.conf are set to “-rwxrwxr-x” again, even when deleting the perms.txt.

I hope the attached data is not too redacted. I hope you can help me and thank you in advance.

 

Command execution.txt 1.45 kB · 1 download supervisord.log 28.98 kB · 6 downloads

May be a DNS problem. Try setting your DNS to just 1.1.1.1

27 minutes ago, wgstarks said:

May be a DNS problem. Try setting your DNS to just 1.1.1.1

I am quite new to unraid, I hope I have understood you correctly. I have set the DNS from 1.1.1.1 in the ‘wg0.conf’. I hope that's what you meant.

Unfortunately this has not brought any improvement.

29 minutes ago, aku_pod said:

I am quite new to unraid, I hope I have understood you correctly. I have set the DNS from 1.1.1.1 in the ‘wg0.conf’. I hope that's what you meant.

Unfortunately this has not brought any improvement.

No. I was referring to the name server setting in the docker configuration. In the docker tab click the name of the docker. Edit the name server section to only include 1.1.1.1 and click apply.

19 minutes ago, wgstarks said:

No. I was referring to the name server setting in the docker configuration. In the docker tab click the name of the docker. Edit the name server section to only include 1.1.1.1 and click apply.

Ok, done that. I'm not quite sure if it's because of the change, or if it's because i waited much longer to log in to the webui (more than 10 minutes).
I was able to log in now, but I don't have a VPN connection (so no downloads), my torrents are gone and most of the settings seem to be missing. 

Edited January 12, 20251 yr by aku_pod

13 minutes ago, aku_pod said:

Ok, done that. I'm not quite sure if it's because of the change, or if it's because i waited much longer to log in to the webui (more than 10 minutes).
I was able to log in now, but I don't have a VPN connection (so no downloads), my torrents are gone and most of the settings seem to be missing. 

Post a new supervisord log.

20 minutes ago, wgstarks said:

Post a new supervisord log.

supervisord 02.logdone

7 minutes ago, aku_pod said:

supervisord 02.logdone

Looks like a successful start. Why do you think your not connected through the VPN?

8 minutes ago, wgstarks said:

Looks like a successful start. Why do you think your not connected through the VPN?

i rly have no idea, i double checked my user/pw and the forwarded ports. I'm rly confused what could suddenly have changed.

2 hours ago, aku_pod said:

i rly have no idea, i double checked my user/pw and the forwarded ports. I'm rly confused what could suddenly have changed.

If you can access the webUI then you are connected via the vpn.

Can you post a screenshot of what you are seeing in the webUI?

7 minutes ago, wgstarks said:

Can you post a screenshot of what you are seeing in the webUI?

At this point using it is rly slow. Im note getting any nodes and the connection is marked as "firewalled" (flame icon) which confuses me even more. 

Afraid I’m out of ideas.

15 minutes ago, wgstarks said:

Afraid I’m out of ideas.

all good, still thanks alot for your help!!! I kinda had a feeling from the begining, that ill have to go for a fresh setup.

I am setting up qbittorrentvpn for the first time and ran into two problems. The first was that the admin/adminadmin default was not working, which I was able to overcome by pasting WebUI\Password_PBKDF2="@ByteArray(ARQ77eY1NUZaQsuDHbIMCA==:0WMRkYTUWVT9wVvdDtHAjU9b3b7uB8NR1Gur2hmQCvCDpm39Q+PsJRJPaCU51dEiz+dTzh8qbPsL8WkFljQYFQ==)" at the end of the config file using console.

 

The second challenge is that after I activated the vpn, the web ui wont open. I am getting an error and a warning while the container is opening insmod: ERROR: could not load module /lib/modules/iptable_mangle.ko: No such file or directory and WARNING: file 'credentials.conf' is group or others accessible 

 

Not sure how to overcome these. Some details to hopefully help:

- I tried running the container without vpn active and it worked fine (after the default password problems).

- I know that my vpn username and password are correct.

- I am using PIA

- I moved the .pem file, the certificate, and the new york .ovpn file into the openvpn file using console. They are located at path /mnt/user/appdata/binhex-qbittorrentvpn/openvpn/ and I checked to make sure that they were actually there

 

Any troubleshooting steps would be really appreciated!

6 hours ago, AGluck said:

I am setting up qbittorrentvpn for the first time and ran into two problems. The first was that the admin/adminadmin default was not working, which I was able to overcome by pasting WebUI\Password_PBKDF2="@ByteArray(ARQ77eY1NUZaQsuDHbIMCA==:0WMRkYTUWVT9wVvdDtHAjU9b3b7uB8NR1Gur2hmQCvCDpm39Q+PsJRJPaCU51dEiz+dTzh8qbPsL8WkFljQYFQ==)" at the end of the config file using console.

 

The second challenge is that after I activated the vpn, the web ui wont open. I am getting an error and a warning while the container is opening insmod: ERROR: could not load module /lib/modules/iptable_mangle.ko: No such file or directory and WARNING: file 'credentials.conf' is group or others accessible 

 

Not sure how to overcome these. Some details to hopefully help:

- I tried running the container without vpn active and it worked fine (after the default password problems).

- I know that my vpn username and password are correct.

- I am using PIA

- I moved the .pem file, the certificate, and the new york .ovpn file into the openvpn file using console. They are located at path /mnt/user/appdata/binhex-qbittorrentvpn/openvpn/ and I checked to make sure that they were actually there

 

Any troubleshooting steps would be really appreciated!

Attach your supervisord log and docker run command to your next post. Be sure to redact users/passwords.

5 hours ago, wgstarks said:

Attach your supervisord log and docker run command to your next post. Be sure to redact users/passwords.

I think this is what you asked for. I am not sure how to save the logs as a file so I screenshotted

 

Also, everything still functions just fine if I change the "vpn enabled" setting to "no" so I know that it has something to do with my vpn setup

 

Edited January 13, 20251 yr by AGluck