[Support] binhex - qBittorrentVPN

[Boy Kai]

1 hour ago, Boy Kai said:

Hey everyone. Not really sure what's going on, any help would be appreciated.

 

qBittorrent was working fine until a couple days ago. Now when I start my container in Unraid, it fails to start and then goes back into stopped mode.

I get this in the container logs.

 

[info] qBittorrent process started
[info] Waiting for qBittorrent process to start listening on port 8080...

2023-12-13 09:13:33,064 DEBG 'watchdog-script' stdout output:
[info] qBittorrent process listening on port 8080

2023-12-13 09:27:26,999 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 09:42:27,324 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 09:57:27,667 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 10:12:27,968 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 10:27:28,270 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 10:42:28,587 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 10:57:28,916 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 11:12:29,242 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 11:27:29,553 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 11:42:29,859 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 11:57:30,162 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 12:12:30,474 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 12:27:30,804 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 12:42:31,116 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 12:57:31,425 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 13:12:31,746 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 13:27:32,042 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 13:42:32,359 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 13:57:32,680 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 14:12:32,998 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 14:27:33,303 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 14:42:33,626 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 14:57:33,952 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 15:12:34,261 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 15:22:38,877 WARN received SIGTERM indicating exit request
2023-12-13 15:22:38,888 DEBG killing watchdog-script (pid 267) with signal SIGTERM
2023-12-13 15:22:38,888 INFO waiting for start-script, watchdog-script to die
2023-12-13 15:22:38,889 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 22663020333008 for <Subprocess at 22663020332752 with name watchdog-script in state STOPPING> (stdout)>
2023-12-13 15:22:38,889 DEBG fd 15 closed, stopped monitoring <POutputDispatcher at 22663017967440 for <Subprocess at 22663020332752 with name watchdog-script in state STOPPING> (stderr)>
2023-12-13 15:22:38,889 WARN stopped: watchdog-script (exit status 143)
2023-12-13 15:22:38,889 DEBG received SIGCHLD indicating a child quit
2023-12-13 15:22:38,889 DEBG killing start-script (pid 266) with signal SIGTERM
2023-12-13 15:22:39,890 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22663020233424 for <Subprocess at 22663019963088 with name start-script in state STOPPING> (stdout)>
2023-12-13 15:22:39,929 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22663020352784 for <Subprocess at 22663019963088 with name start-script in state STOPPING> (stderr)>
2023-12-13 15:22:39,929 WARN stopped: start-script (terminated by SIGTERM)
2023-12-13 15:22:39,930 DEBG received SIGCHLD indicating a child quit

** Press ANY KEY to close this window ** 

 

For anyone else, going into the docker docker application settings, attempting to update a field, and selecting 'Apply' showed better error logs.

I had a port allocated twice somehow, not sure when it got introduced. Removed it from the config, and the docker started.

[bumperjeep]

Hi - I have a routing question. I'm thinking of doing a site to site vpn on my router. I wanted to make sure that there wasn't anything I could do at my router level that would override / mess up the iptables on the container. I'm referring to the iptable rules you describe here https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md.

 

I'm sure that PIA uses a 10. network internally, and my site to site might also be joining to a remote 10. network. The container does not need to talk to the remote network ever, so I'm just double checking I won't break your core functionality.

 

[Jannik_]

On 11/30/2023 at 1:09 AM, wgstarks said:

https://forums.unraid.net/topic/75539-support-binhex-qbittorrentvpn/?do=findComment&comment=1329646

 

Hi,

 

can you please post a screenshot that shows where that preferences line is?

 

My challenge: I installed and configured it according to the VPN docker how2. I can access the webui. But admin adminadmin does not work (are these still the default credentials?)

 

[wgstarks]

24 minutes ago, Jannik_ said:

where that preferences line is?

Sorry but I’m not sure what you mean by “preferences line”. The repository field is in the docker container configuration.

[Jannik_]

Thank you. I solved it with binhex-deluge. Here the default login worked.

[wgstarks]

On 11/30/2023 at 8:08 PM, practicing-haunch2956 said:

I'm wondering if that recently changed? I didn't have that added before and I had been using qbittorrent just fine until that last update. Strange.

 

Anyway, that did the trick. Thank you so much.

Qbittorrent devs have decided that default username and password must now be changed. A temporary password is supposed to be included in the container logs but may not be due to a bug which may not be resolved yet. If you read through the previous couple of pages you'll see quite a lot of discussion regarding this issue but the short version is to revert to a previous version and either stay with it or set a secure user/password.

 

https://forums.unraid.net/topic/75539-support-binhex-qbittorrentvpn/?do=findComment&comment=1329646

[LanceM26]

Hi,

 

Not really sure what's going on. I have my files stuck in moving. It's setup as downloading incomplete into /data/incomplete and moving it to /data/completed once done.

 

The torrents are pulled via Sonarr and Radarr if that helps.

 

 

It's been stuck like this for hours

[EwanL]

Hello Binhex and everyone else,

 

I am experiencing access denied errors when trying to access files/folders recently downloaded with this binhex-qbittorrentvpn community app. 

 

I have a rootshare that I can read and write to from a networked windows 10 machine successfully with a username/password setup in unraid. 

 

When I run the permission fix tool over the Downloads folder the permissions are fixed and start working for the auth user setup in unraid. 

 

I believe it's related to the UMASK setting - but I haven't been able to figure out what specifically to change to resolve new downloads getting the wrong permissions set. 

 

The current docker settings are: 

 

UMASK 002

PUID 99

PGID 100

 

Is there anything you can suggest to help me fix the permissions issues?

 

[wgstarks]

8 hours ago, LanceM26 said:

It's setup as downloading incomplete into /data/incomplete and moving it to /data/completed once done.

Have you double checked this? In the past I had a problem where qbit would switch download locations from /data to /downloads for some unknown reason and I would see all the torrents moving as you describe.

[LanceM26]

3 hours ago, wgstarks said:

Have you double checked this? In the past I had a problem where qbit would switch download locations from /data to /downloads for some unknown reason and I would see all the torrents moving as you describe.

 

Yea, I checked if the file paths are correct:

 

[wgstarks]

9 hours ago, EwanL said:

I believe it's related to the UMASK setting - but I haven't been able to figure out what specifically to change to resolve new downloads getting the wrong permissions set. 

Try 000. That’s the default.

[wgstarks]

33 minutes ago, LanceM26 said:

Yea, I checked if the file paths are correct:

Anything in the Execution Log? You probably need to enable it as n the View menu.

[EwanL]

5 hours ago, wgstarks said:

Try 000. That’s the default.

Yeah i've tried 000, 002, 022 and it doesn't seem to have an effect. 

 

I've just changed it back to 000 and run another test and had the exact same result 

 

 

The folder permissions after download.

 

All the other lines are folders after previously running the permission fixer tool. 

[wgstarks]

51 minutes ago, EwanL said:

 

All the other lines are folders after previously running the permission fixer tool. 

I’m guessing you have this share mounted in UD? Have you checked the User settings there?

[EwanL]

45 minutes ago, wgstarks said:

I’m guessing you have this share mounted in UD? Have you checked the User settings there?

 

By UD do you mean Unassigned Devices?

I have that installed but the share has no relation as far as i'm aware.

SMB is disabled on the Unassigned Devices Settings page. 

 

This share was setup through the regular unraid shares page: 

 

The user account i'm accessing with via windows 10/SMB has Read/Write permissions to this share. 

[wgstarks]

9 minutes ago, EwanL said:

 

The user account i'm accessing with via windows 10/SMB has Read/Write permissions to this share. 

Afraid I’m out of ideas. You shouldn’t have needed any permission changes to access the share. Just user and password.

[EwanL]

5 minutes ago, wgstarks said:

Afraid I’m out of ideas. You shouldn’t have needed any permission changes to access the share. Just user and password.

Well its accessible via the home network so I definitely wanted authentication on it. 

 

I appreciate the help anyway

Edited December 19, 2023 by EwanL

[DanielPT]

I havent updated for a long time becurse of the admin webui error.

 

Is it safe to upgrade? I use admin/"MYWONPW"

[wgstarks]

2 hours ago, DanielPT said:

I havent updated for a long time becurse of the admin webui error.

 

Is it safe to upgrade? I use admin/"MYWONPW"

I would add a custom user name but as long as you have a strong password you should be good. Downgrading is very simple if you have any issues. I also whitelisted my local network just to avoid having to add login info to all the *arrs.

[DanielPT]

53 minutes ago, wgstarks said:

I would add a custom user name but as long as you have a strong password you should be good. Downgrading is very simple if you have any issues. I also whitelisted my local network just to avoid having to add login info to all the *arrs.

DId the update and no problems. I also disabled login for lan. I have a pretty strong pw

[wgstarks]

9 minutes ago, DanielPT said:

no problems

Great 👍

[TallMan206]

Hi all,

 

My webUI just does not get up.

Can you help me check what is wrong?

 

Uploaded the NordVPN OpenVPN config file into the dir of the docker. 

Starting up the docker, but my webUI just does not load.

 

Thanks

 

[MaxiWheat]

Hi everyone, I'm having a very strange memory issue with this docker image.

 

I am already running an instance of this image in Docker, and it runs pretty smoothly. I seed ~1200 torrents and it idles at around 300MiB of RAM usage according to the Docker page in Unraid.

 

I'm also running an old rtorrent/rutorrent container serving ~ 2200 torrents (and on average larger than those in current qBT), that I want to migrate to qBittorrent so I created a new binhex-qbittorrentvpn container using the previous one as a template and I took good care of changing all ports and paths (including appdata) to avoid issues. The container started correctly, the webui is accessible (had to do a thing for the login since adminadmin does not work anymore, but I managed to make it work). I then imported all my torrents from rtorrent into the new qbittorrent instance without starting them to be make sure everything is fine before starting to seed. I stopped my rtorrent container to avoid "double-seeding" and started seeding with the new qbittorrent container. 

And then problems began...

Both qbittorrent containers started to increase in memory usage... I did not set a limit to their memory usage so it ended taking all my Unraid RAM (24GB) to the point the WEBUI of Unraid was not accessible anymore: I had to reboot my server. I decided to set a memory limit on the containers at 3GB (first qBT) and 6GB (new qBT) but they maxed it too, sometimes in the container logs the "watchdog-script" detected that qBT was not running anymore (it got killed inside the container) and restarted it and other times the memory stayed at 5.997GiB and the 2 CPU cores I allowed maxed at 100%. All this happening in ~5 minutes.

 

If I only start one or the other of the qBT container, everything runs fine... but if I run both, dang, the memory goes crazy.

 

Can someone explain what is going on here ? Am I missing something ? Are there special configs I need to set to avoid issues running this container twice ? Any help would be appreciated. I can also provide more information/context if required.

[bombsngravyb1]

I use wireguard through my UDM Pro, it works great ... except for qbit.

 

I have the IP's allowed, 192.168.1.0/32 but i'm still unable to access qbit - its the only app/docker that I can't access. Is there something special with qbit ?

Edited December 24, 2023 by bombsngravyb1
I'm an idiot

[Unraidmule]

If i used PrivateVPN every time it connects to a server i will be given a dynamic port - does this container relay the port in qbit? or do i have to do it manually?