[Support] binhex - qBittorrentVPN


Recommended Posts

Can someone help me figure out why I can't log in to Qbittorrent from Firefox?  Works just fine on Chrome or Edge so I assume it has to be a Firefox problem but I'm not sure.  I get to the login screen and enter my password and username and then it just reloads the login screen.

Link to comment
On 9/22/2022 at 10:24 PM, sph031772 said:

My docker had been running good for months. I haven't changed anything in the docker settings since I initially set it up, but I did move my appdata folder to a new SATA SSD cache protected by RAID 1 from a stand alone NVME.   I noticed after I moved it the qbittorent Web UI login took longer to prompt, a few seconds.   Now it just simply stopped working a few weeks later.  When I disable VPN it works though.   CA backups has been backing up QBIT and I also noticed that the folder permission state owner nobody (not sure if that changed at one point).   Im using Nordvpn as my VPN, I tried replacing the sever file with a new one, but no luck.

 

All of my ARR dockers use a separate bridge network I created called dockerrnet 172.18.0.0/16 

I tried switching to br0 and changing the LAN Network settings, nothing has worked.

 

I see static routes but I'm not sure what the gateways are.

 

Route: 172.17.0.0/16

Geteway: docker01

Route: 172.18.0.0/16

Gateway: br-31fc6dcb88df1

 

I get the following error when I start the Docker with VPN enabled.

 

472 DEBG 'start-script' stdout output:
TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
TLS Error: TLS handshake failed

DEBG 'start-script' stdout output:
SIGHUP[soft,tls-error] received, process restarting

 

I'm running Tag 4.4.5-1-01.

 

Any help would be much appreciated.

 

image.png.75bd6499c59e57096e9a1ed2157cbaea.png

supervisord.log_1.txt 84.37 kB · 0 downloads


You get a solution to this issue? Seems to be the exact same problem I'm getting after a recent update. NordVPN and disabling the VPN works fine.

Thank you!

Link to comment

Suffered form a power  trip, now I need help with log in issues and qbit writing old completed files back into the cache (4.3.9-2-01)

 

1st - im running into issues login into the webgui, i have the login saved on the web browser so i know its right and hasnt changed since setting it up. every time i try it out, i get invalid username or password. Using the default admin login does let me in but the everything is cleared out, doesn't show any torrents or files at all. I have tried resetting the default log in but my config file looks very odd and might have been corrupted some how.

 

2nd -  i somehow got the same problem that was occurring in 4.4.0 that was causing all files to be written to the cache drive instead of the disk. was a while since i found the solution that fixed it but idk why it happened as 4.3 was one of the fixes. should I just pull the latest and try out the fixes for 4.3 after?

qbit.PNG

qbit - conf.PNG

Link to comment

Does anyone else have issues with qBittorrent where torrents just stop seeding?  It's gotten much worse over the last few months and basically when I check in, several trackers do not know about a large chunk of torrents that I'm seeding.  Rebooting the container fixes it for a while, but it'll come back.

 

I'm only about ~500 torrents and I've seen others using way more than that and the host machine has plenty of resources so not sure what the issue could be exactly.

 

Just curious if others see some, not all, torrents silently stop seeding when they should still be seeding.

Link to comment

I have the same problem with downloads - it may be because I do not seed *that* much.

After a while I have the impression as though my qBT container silently goes to sleep - doesn't see any sources anymore.

A reboot briefly remedies the situation but after a day or two, at best after a couple of days, the situation is as it was.

I already deleted the container and set it up from scratch again but the situation quickly went to where it was before.

i wonder whether this is just two sides of the same problem.

Link to comment

what is the default container path /data to host /mnt/user/appdata/data used for? just noticed it was creating this in my appdata. its on the default template but dont know what it does. trying to setup hardlinks so i made a new path for container /data/torrents/ to host /mnt/user/data/torrents/

Edited by droopie
Link to comment
42 minutes ago, droopie said:

what is the default container path /data to host /mnt/user/appdata/data used for? just noticed it was creating this in my appdata. its on the default template but dont know what it does. trying to setup hardlinks so i made a new path for container /data/torrents/ to host /mnt/user/data/torrents/

/data is the path for your downloads.

Link to comment
Just now, wgstarks said:

/data is the path for your downloads.

so its safe to change the downloads out of the appdata on the host since thats the default location? 
changed it from /data to /data/torrents on the container and changed /mnt/user/appdata/data to  /mnt/user/data/torrents/ on the host

Link to comment
4 minutes ago, droopie said:

so its safe to change the downloads out of the appdata on the host since thats the default location? 
changed it from /data to /data/torrents on the container and changed /mnt/user/appdata/data to  /mnt/user/data/torrents/ on the host

I would have left it as /data and then set the download location in qbit settings to /data/torrents just because that matches the path in Sonarr and Radarr. You don’t say if you’re using either of those though.

Link to comment
5 minutes ago, wgstarks said:

I would have left it as /data and then set the download location in qbit settings to /data/torrents just because that matches the path in Sonarr and Radarr. You don’t say if you’re using either of those though.

yea im using the trash guides so it says to use /data/torrent on the container path for qbit but for arr's it says to set the container paths to /data. i was wondering if i had to match all them to /data but figured they are smarter and im new to this so just left it as how they said. not sure it needs updating

Link to comment
Just now, droopie said:

yea im using the trash guides so it says to use /data/torrent on the container path for qbit but for arr's it says to set the container paths to /data. i was wondering if i had to match all them to /data but figured they are smarter and im new to this so just left it as how they said. not sure it needs updating

Whatever container and host path you use in the *arrs must exactly match what you have configured in qbit. Otherwise you’ll get an error from them that the path does not exist since they’ll be searching in the wrong place.

Link to comment
16 minutes ago, wgstarks said:

Whatever container and host path you use in the *arrs must exactly match what you have configured in qbit. Otherwise you’ll get an error from them that the path does not exist since they’ll be searching in the wrong place.

For examples and better explanation see here.

Scroll down to Q4.

Link to comment
3 hours ago, DanielPT said:

Hi all.

Thanks for this nice docker!

Im all new to unraid.

Im trying to use this with mullvad. I have created a wireguard conf file. But how to i "upload" it to th wireguard folder? :)

Thanks!

I’m sure there are multiple ways to accomplish this. I usually just enable sharing for appdata and then drag and drop the file to the appropriate folder in the mounted share. You could also install the Dynamix File Manager plugin. It has an upload option.

  • Like 1
Link to comment
3 hours ago, DanielPT said:

But im a correct that the port that i use in the wireguard config i need to set it in qbitrorrent?

I don’t use wireguard so I may be wrong but I doubt you need to do this. Q21 in the faq describes how to setup wireguard.

 

3 hours ago, DanielPT said:

And how can i test it? 

You can test by downloading any well seeded torrent. Ubuntu is what I usually use.

  • Like 1
Link to comment

 

35 minutes ago, wgstarks said:

I don’t use wireguard so I may be wrong but I doubt you need to do this. Q21 in the faq describes how to setup wireguard.

 

You can test by downloading any well seeded torrent. Ubuntu is what I usually use.

Thanks for the reply :)

 

I can see that my settings looks good. Download goes fast. I just want to test if im "reachable" with the port config :)

Link to comment

for some reason files are not downloading to where im trying to get them to go the docker container /data path is set to /mnt/user/tor/ but its sending it to /mnt/user/appdata/binhex-qbittorrentvpn/qBittorrent and in the webui its /config/qBittorrent/downloads if i try to set it to anything else in the webui it says cannot make save path. the appdata path is on my small cache ssd for my dockers so i cant have all the torrents downloading there. thanks for any ideas

Link to comment
On 10/29/2022 at 8:30 PM, DanielPT said:

 

Thanks for the reply :)

 

I can see that my settings looks good. Download goes fast. I just want to test if im "reachable" with the port config :)

if the plug icon (bottom of qbittorrent web ui) is green then you are reachable i.e. port forwarding is working.

Link to comment

Thanks man! :)

 

EDIT: Got it working - I removed Host 3 then it brake webui. Added it and now i webui.

I have made alot of conf files and tryed meny things.

Now i cant access my Webui anymore. 

 

Any ideas? :(

 

Will CA Backup / Restore Appdata still brake the docker? :) 

 

Thanks!

 

 

 

 

Edited by DanielPT
Link to comment

 

Hi all,

I'm in need of some sort of urgent help here.

This has been working perfectly on Mullvad VPN for over a year now, but suddenly it just stopped.

I can no longer access the webUI, and no download requests are accepted. I've tried restarting the container and checking all my settings, but everything looks fine. I'm at a loss.
Did Mullvad change something recently that makes it where I have to use wireguard now or something? I don't see anything on their site about it, but I haven't done an exhaustive search. I just have a pissed off wife I'm trying to appease, so any help will be awesome. lol

 

EDIT: If I flip the 'VPN_ENABLED" variable to "no", it seems to work fine, but this is obviously not ideal, as it kinda defeats the purpose. 

Edited by Elmojo
Link to comment
2 minutes ago, Elmojo said:

Hi all,

I'm in need of some sort of urgent help here.

This has been working perfectly on Mullvad VPN for over a year now, but suddenly it just stopped.

I can no longer access the webUI, and no download requests are accepted. I've tried restarting the container and checking all my settings, but everything looks fine. I'm at a loss.
Did Mullvad change something recently that makes it where I have to use wireguard now or something? I don't see anything on their site about it, but I haven't done an exhaustive search. I just have a pissed off wife I'm trying to appease, so any help will be awesome. lol

Post there contents of supervisord.log in your appdata folder.

Link to comment

Here's just the part from the last time I restarted the container, and then when I disabled the VPN and restarted it again...

Created by...
___.   .__       .__
\_ |__ |__| ____ |  |__   ____ ___  ___
 | __ \|  |/    \|  |  \_/ __ \\  \/  /
 | \_\ \  |   |  \   Y  \  ___/ >    <
 |___  /__|___|  /___|  /\___  >__/\_ \
     \/        \/     \/     \/      \/
   https://hub.docker.com/u/binhex/

2022-11-02 21:02:04.377689 [info] Host is running unRAID
2022-11-02 21:02:04.415799 [info] System information Linux 1954464e178d 5.15.46-Unraid #1 SMP Fri Jun 10 11:08:41 PDT 2022 x86_64 GNU/Linux
2022-11-02 21:02:04.456379 [info] OS_ARCH defined as 'x86-64'
2022-11-02 21:02:04.495462 [info] PUID defined as '1001'
2022-11-02 21:02:04.539328 [info] PGID defined as '100'
2022-11-02 21:02:04.633757 [info] UMASK defined as '000'
2022-11-02 21:02:04.672597 [info] Permissions already set for '/config'
2022-11-02 21:02:04.720468 [info] Deleting files in /tmp (non recursive)...
2022-11-02 21:02:04.777290 [info] VPN_ENABLED defined as 'yes'
2022-11-02 21:02:04.819589 [info] VPN_CLIENT defined as 'openvpn'
2022-11-02 21:02:04.860236 [info] VPN_PROV defined as 'custom'
2022-11-02 21:02:04.912225 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/mullvad_us_atl.ovpn
2022-11-02 21:02:05.120742 [info] VPN remote server(s) defined as 'us-atl-105.mullvad.net,us-atl-104.mullvad.net,us-atl-101.mullvad.net,us-atl-103.mullvad.net,us-atl-102.mullvad.net,'
2022-11-02 21:02:05.154388 [info] VPN remote port(s) defined as '1301,1301,1301,1301,1301,'
2022-11-02 21:02:05.187845 [info] VPN remote protcol(s) defined as 'udp,udp,udp,udp,udp,'
2022-11-02 21:02:05.226177 [info] VPN_DEVICE_TYPE defined as 'tun0'
2022-11-02 21:02:05.261517 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2022-11-02 21:02:05.301258 [info] LAN_NETWORK defined as '192.168.11.0/24'
2022-11-02 21:02:05.344647 [info] NAME_SERVERS defined as '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'
2022-11-02 21:02:05.386736 [info] VPN_USER defined as 'xxxxxx'
2022-11-02 21:02:05.431075 [info] VPN_PASS defined as 'xxxxxx'
2022-11-02 21:02:05.473985 [info] ENABLE_PRIVOXY defined as 'no'
2022-11-02 21:02:05.521751 [info] VPN_INPUT_PORTS defined as 'REDACTED'
2022-11-02 21:02:05.561524 [info] VPN_OUTPUT_PORTS not defined (via -e VPN_OUTPUT_PORTS), skipping allow for custom outgoing ports
2022-11-02 21:02:05.604734 [info] WEBUI_PORT defined as '8080'
2022-11-02 21:02:05.646152 [info] Starting Supervisor...
2022-11-02 21:02:05,896 INFO Included extra file "/etc/supervisor/conf.d/qbittorrent.conf" during parsing
2022-11-02 21:02:05,897 INFO Set uid to user 0 succeeded
2022-11-02 21:02:05,901 INFO supervisord started with pid 8
2022-11-02 21:02:06,905 INFO spawned: 'start-script' with pid 236
2022-11-02 21:02:06,907 INFO spawned: 'watchdog-script' with pid 237
2022-11-02 21:02:06,908 INFO reaped unknown pid 9 (exit status 0)
2022-11-02 21:02:06,914 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2022-11-02 21:02:06,914 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2022-11-02 21:02:06,914 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2022-11-02 21:02:06,920 DEBG 'watchdog-script' stdout output:
[info] qBittorrent config file already exists, skipping copy
[info] Removing session lock file (if it exists)...

2022-11-02 21:02:07,029 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.222 to /etc/resolv.conf

2022-11-02 21:02:07,035 DEBG 'start-script' stdout output:
[info] Adding 84.200.69.80 to /etc/resolv.conf

2022-11-02 21:02:07,039 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.174 to /etc/resolv.conf

2022-11-02 21:02:07,044 DEBG 'start-script' stdout output:
[info] Adding 1.1.1.1 to /etc/resolv.conf

2022-11-02 21:02:07,049 DEBG 'start-script' stdout output:
[info] Adding 209.222.18.218 to /etc/resolv.conf

2022-11-02 21:02:07,055 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.177 to /etc/resolv.conf

2022-11-02 21:02:07,062 DEBG 'start-script' stdout output:
[info] Adding 84.200.70.40 to /etc/resolv.conf

2022-11-02 21:02:07,068 DEBG 'start-script' stdout output:
[info] Adding 1.0.0.1 to /etc/resolv.conf

2022-11-02 21:05:14,221 DEBG 'start-script' stdout output:
[crit] 'us-atl-105.mullvad.net' cannot be resolved, possible DNS issues, exiting...

2022-11-02 21:05:14,221 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23425766678704 for <Subprocess at 23425766673808 with name start-script in state RUNNING> (stdout)>
2022-11-02 21:05:14,221 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23425766678656 for <Subprocess at 23425766673808 with name start-script in state RUNNING> (stderr)>
2022-11-02 21:05:14,222 INFO exited: start-script (exit status 1; not expected)
2022-11-02 21:05:14,222 DEBG received SIGCHLD indicating a child quit
2022-11-02 21:39:32,560 WARN received SIGTERM indicating exit request
2022-11-02 21:39:32,561 DEBG killing watchdog-script (pid 237) with signal SIGTERM
2022-11-02 21:39:32,561 INFO waiting for watchdog-script to die
2022-11-02 21:39:32,562 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 23425766679088 for <Subprocess at 23425766678416 with name watchdog-script in state STOPPING> (stdout)>
2022-11-02 21:39:32,562 DEBG fd 15 closed, stopped monitoring <POutputDispatcher at 23425766679136 for <Subprocess at 23425766678416 with name watchdog-script in state STOPPING> (stderr)>
2022-11-02 21:39:32,563 INFO stopped: watchdog-script (exit status 143)
2022-11-02 21:39:32,563 DEBG received SIGCHLD indicating a child quit
Created by...
___.   .__       .__
\_ |__ |__| ____ |  |__   ____ ___  ___
 | __ \|  |/    \|  |  \_/ __ \\  \/  /
 | \_\ \  |   |  \   Y  \  ___/ >    <
 |___  /__|___|  /___|  /\___  >__/\_ \
     \/        \/     \/     \/      \/
   https://hub.docker.com/u/binhex/

2022-11-02 21:46:53.279086 [info] Host is running unRAID
2022-11-02 21:46:53.312759 [info] System information Linux 5b098552d729 5.15.46-Unraid #1 SMP Fri Jun 10 11:08:41 PDT 2022 x86_64 GNU/Linux
2022-11-02 21:46:53.359554 [info] OS_ARCH defined as 'x86-64'
2022-11-02 21:46:53.399484 [info] PUID defined as '1001'
2022-11-02 21:46:53.507180 [info] PGID defined as '100'
2022-11-02 21:46:53.639214 [info] UMASK defined as '000'
2022-11-02 21:46:53.682330 [info] Permissions already set for '/config'
2022-11-02 21:46:53.728705 [info] Deleting files in /tmp (non recursive)...
2022-11-02 21:46:53.782141 [info] VPN_ENABLED defined as 'no'
2022-11-02 21:46:53.823187 [warn] !!IMPORTANT!! VPN IS SET TO DISABLED', YOU WILL NOT BE SECURE
2022-11-02 21:46:53.868503 [info] WEBUI_PORT defined as '8080'
2022-11-02 21:46:53.917979 [info] Starting Supervisor...
2022-11-02 21:46:54,310 INFO Included extra file "/etc/supervisor/conf.d/qbittorrent.conf" during parsing
2022-11-02 21:46:54,310 INFO Set uid to user 0 succeeded
2022-11-02 21:46:54,314 INFO supervisord started with pid 7
2022-11-02 21:46:55,319 INFO spawned: 'start-script' with pid 80
2022-11-02 21:46:55,322 INFO spawned: 'watchdog-script' with pid 81
2022-11-02 21:46:55,322 INFO reaped unknown pid 8 (exit status 0)
2022-11-02 21:46:55,338 DEBG 'start-script' stdout output:
[info] VPN not enabled, skipping configuration of VPN

2022-11-02 21:46:55,339 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2022-11-02 21:46:55,339 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2022-11-02 21:46:55,339 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22496522788848 for <Subprocess at 22496522783952 with name start-script in state RUNNING> (stdout)>
2022-11-02 21:46:55,340 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22496522788080 for <Subprocess at 22496522783952 with name start-script in state RUNNING> (stderr)>
2022-11-02 21:46:55,340 INFO exited: start-script (exit status 0; expected)
2022-11-02 21:46:55,340 DEBG received SIGCHLD indicating a child quit
2022-11-02 21:46:55,341 DEBG 'watchdog-script' stdout output:
[info] qBittorrent config file already exists, skipping copy
[info] Removing session lock file (if it exists)...

2022-11-02 21:46:55,395 DEBG 'watchdog-script' stdout output:
[info] qBittorrent not running

2022-11-02 21:46:55,396 DEBG 'watchdog-script' stdout output:
[info] Removing session lock file (if it exists)...

2022-11-02 21:46:55,418 DEBG 'watchdog-script' stdout output:
[info] Attempting to start qBittorrent...

2022-11-02 21:46:55,540 DEBG 'watchdog-script' stdout output:
[info] qBittorrent process started
[info] Waiting for qBittorrent process to start listening on port 8080...

2022-11-02 21:46:55,671 DEBG 'watchdog-script' stdout output:
[info] qBittorrent process listening on port 8080

 

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.