14 hours ago, hmoney007 said:

so we still have no fix for the qbit torrents all just disappearing? it only happens for me in firefox and not in edge, which makes me think it's a browser specific issue.

I see all of these errors in the networking tab in firefox after the page initially loads and i see all torrents then they disappear after a few seconds and i see a stream of these errors shown in the image below. I'm happy to provide any other information that would help solve this. I do not have any other issues with any other containers in unraid nor have i added any new extensions to firefox.

Are you using the default webUI?

On 5/20/2025 at 7:42 PM, hmoney007 said:

so we still have no fix for the qbit torrents all just disappearing? it only happens for me in firefox and not in edge, which makes me think it's a browser specific issue.

I see all of these errors in the networking tab in firefox after the page initially loads and i see all torrents then they disappear after a few seconds and i see a stream of these errors shown in the image below. I'm happy to provide any other information that would help solve this. I do not have any other issues with any other containers in unraid nor have i added any new extensions to firefox.

Hi mate, I fixed this by selecting "all" under categories.

Edited May 22, 20251 yr by Repelex

On 5/20/2025 at 6:42 PM, hmoney007 said:

g tab in firefox after the page initially loads and i see all torrents then they disappear after a few seconds and i see a stream of t

On 5/21/2025 at 9:05 AM, wgstarks said:

Are you using the default webUI?

Yes I am using the default webui but I do have "dark reader" in firefox installed (but disabled for qbit).

On 5/20/2025 at 7:42 PM, hmoney007 said:

so we still have no fix for the qbit torrents all just disappearing? it only happens for me in firefox and not in edge, which makes me think it's a browser specific issue.

I see all of these errors in the networking tab in firefox after the page initially loads and i see all torrents then they disappear after a few seconds and i see a stream of these errors shown in the image below. I'm happy to provide any other information that would help solve this. I do not have any other issues with any other containers in unraid nor have i added any new extensions to firefox.

Same issue with Chrome browser. In Chrome browser, I deleted unraid_ip_address:8181 cookies/site data to fixed this issue.

Morning all!
Can we circle back to this for a moment please? I'm still stuck...
So I'm starting over with this container.

When I try to follow the initial setup guide, as linked in Post #1 of this thread, it says nothing about WG, only OpenVPN.  That's why I was thinking there was no need for the manual config, since I thought I recalled that @binhex said that switching to WG negated the need for all the manual setup.  I'm probably remembering that wrong, it's been a while.

I've put the ovpn and cert files in the 'openvpn' folder, as directed.

When I start the container, it creates an empty 'wireguard' folder, so it's obviosuly looking for the wg0 file, I just don't have one to give it.

I don't see any way to manually download any sort of WG config for PIA, and the container doesn't appear to be setting it up automatically for me, so now what do I do....?

Thanks in advance for any help! 😁

Hello good people.)

I´m having a problem, i can install the binhex-qbittorrent and acces it normaly, but i cant access when i enable vpn in the container.. Im using protonvpn and i have tried to reinstall multiple times..

I followed this guide: https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

I´ve tried to follow the guide but i cant make it work.. i think that it´s the lan network i have to change.. But i have put in my own network and the cidr /24.. What can i be doing wrong?? I also use wireguard, as protocol..

Installed as bridge..

Hope you can help me:)

Thank you!

Hello again, i think i found the problem. I tried to download the conf again.. Tried to switch to protonvpn linux config.. And now it works:))

Thank you!

Edited May 23, 20251 yr by Mattti1912
Found the solution:)

9 hours ago, Mattti1912 said:

I tried to download the conf again.. Tried to switch to protonvpn linux config.. And now it works:

Does ProtonVPN provide a Wireguard-specific configuration download for you? I'm using PIA, and don't see any option to download a WG config. I think this is my issue as well. Maybe.

Anyone can help me? Installed it multiple times, and tried multiple settings but cant get in to the webui at all

ps: vpn disabled for now

Edited May 29, 20251 yr by Gouden

22 minutes ago, Gouden said:

Anyone can help me? Installed it multiple times, and tried multiple settings but cant get in to the webui at all

ps: vpn disabled for now

Enable VPN and then:- I will need to see a log to help further, please see the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md#unraid-users

On 5/24/2025 at 2:59 AM, Elmojo said:

Does ProtonVPN provide a Wireguard-specific configuration download for you? I'm using PIA, and don't see any option to download a WG config. I think this is my issue as well. Maybe.

Please see Q31 from the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

For PIA this is fully automated, no download of WG config is required (or possible - config is dynamic)

17 minutes ago, binhex said:

Enable VPN and then:- I will need to see a log to help further, please see the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md#unraid-users

Here is the log

supervisord.log

2 minutes ago, Gouden said:

Here is the log

supervisord.log

from your log:-

2025-05-29 13:13:16,015 DEBG 'start-script' stdout output:

[info] ProtonVPN username '<you leaked your 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

Please see Q31 from the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Update: Fixed! (for me anyway)

Looking at @jayare post about deleting the cookie in Chrome, I did the same in Firefox. Deleted all Cookies associated with my UnRaid's IP. Now the torrents don't "blink out" after restarting Firefox.

I will throw my name into the hat as well with all my .torrents blinking out of the screen while using Firefox. It's damn strange though because on my laptop, using Firefox, I don't have the issue. Same version of Firefox between both my laptop and, desktop where they "blink out".

Edited May 29, 20251 yr by CoZ

8 minutes ago, binhex said:

from your log:-

2025-05-29 13:13:16,015 DEBG 'start-script' stdout output:

[info] ProtonVPN username '<you leaked your 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

Please see Q31 from the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Sorry was trying with free proton account, changed to pia account now. Still can't access the webui at all

supervisord(1).log

27 minutes ago, Gouden said:

Sorry was trying with free proton account, changed to pia account now. Still can't access the webui at all

supervisord(1).log

nothing wrong in that log file, what is the ip address of the machine running the web browser you are using to attempt connection to the web ui of qbittorrent?

3 minutes ago, binhex said:

nothing wrong in that log file, what is the ip address of the machine running the web browser you are using to attempt connection to the web ui of qbittorrent?

it's 192.168.0.18

12 minutes ago, Gouden said:

it's 192.168.0.18

Your webui port is not correctly defined, i see you are trying to use port 8085, see Q4:- https://github.com/binhex/documentation/blob/master/docker/faq/qbittorrentvpn.md

33 minutes ago, binhex said:

Your webui port is not correctly defined, i see you are trying to use port 8085, see Q4:- https://github.com/binhex/documentation/blob/master/docker/faq/qbittorrentvpn.md

Tried that, but didn't help. But reinstalled the docker again now with 8080 as port and seems to be working now so have to change the port on the other docker running on 8080

6 hours ago, binhex said:

For PIA this is fully automated, no download of WG config is required (or possible - config is dynamic)

That's why I'm so baffled as to why my setup isn't working! I've been struggling with this for weeks, with no real progress.
I've tried my best to follow the installation guide and FAQs, but I just hit a wall. It's so frustrating. :(
I don't know what else to do. What do you need from me to help troubleshoot further?

On 5/29/2025 at 1:26 PM, Elmojo said:

That's why I'm so baffled as to why my setup isn't working! I've been struggling with this for weeks, with no real progress.
I've tried my best to follow the installation guide and FAQs, but I just hit a wall. It's so frustrating. :(
I don't know what else to do. What do you need from me to help troubleshoot further?

You should attach the supervisord.log and docker run command to your next post.

8 hours ago, wgstarks said:

You should attach the supervisord.log and docker run command to your next post.

Again? Sure thing, here you go...

docker run

  -d
  --name='binhex-qbittorrentvpn'
  --net='bridge'
  --privileged=true
  -e TZ="America/New_York"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="Tower"
  -e HOST_CONTAINERNAME="binhex-qbittorrentvpn"
  -e 'VPN_ENABLED'='yes'
  -e 'VPN_USER'='xxx'
  -e 'VPN_PASS'='xxx'
  -e 'VPN_PROV'='pia'
  -e 'VPN_CLIENT'='wireguard'
  -e 'STRICT_PORT_FORWARD'='yes'
  -e 'ENABLE_PRIVOXY'='no'
  -e 'ENABLE_SOCKS'='no'
  -e 'SOCKS_USER'='admin'
  -e 'SOCKS_PASS'='socks'
  -e 'LAN_NETWORK'='192.168.1.0/24, 100.64.98.0/24'
  -e 'WEBUI_PORT'='8080'
  -e 'VPN_INPUT_PORTS'=''
  -e 'VPN_OUTPUT_PORTS'=''
  -e 'DEBUG'='false'
  -e 'VPN_OPTIONS'=''
  -e 'ENABLE_STARTUP_SCRIPTS'='no'
  -e 'USERSPACE_WIREGUARD'='no'
  -e 'NAME_SERVERS'='1.1.1.1,1.0.0.1'
  -e 'PUID'='99'
  -e 'PGID'='100'
  -e 'UMASK'='000'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://[IP]:[PORT:8080]'
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/qbittorrent-icon.png'
  -p '8080:8080/tcp'
  -p '8118:8118/tcp'
  -p '9118:9118/tcp'
  -p '58946:58946/tcp'
  -p '58946:58946/udp'
  -v '/mnt/user/appdata/binhex-qbittorrentvpn':'/config':'rw'
  -v '/mnt/user/downloads/':'/data':'rw'
  --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'ghcr.io/binhex/arch-qbittorrentvpn'

4542ef1bedcedbceb49e7138ea62bc011015345aba3cabf586463647620d5539

The command finished successfully!

supervisord.log

Edited May 31, 20251 yr by Elmojo

1 hour ago, Elmojo said:

Again?

Sorry, been out of touch for a while. Have you also tried a different endpoint?

3 hours ago, wgstarks said:

Have you also tried a different endpoint?

Sorry, I'm not sure how I'd go about trying that... but I'm willing!

6 minutes ago, Elmojo said:

Sorry, I'm not sure how I'd go about trying that... but I'm willing!

If you open the wg0.conf file (appdata/binhex-qbittorrentvpn/wireguard/wg0.conf) you'll see a line like this. You can edit it to pick your endpoint.

Endpoint = ca-montreal.privacy.network

Possibilities-

[info] pt.privacy.network

[info] china.privacy.network

[info] mongolia.privacy.network

[info] italy.privacy.network

[info] ad.privacy.network

[info] zagreb.privacy.network

[info] au-sydney.privacy.network

[info] denmark.privacy.network

[info] mexico.privacy.network

[info] venezuela.privacy.network

[info] monaco.privacy.network

[info] es-valencia.privacy.network

[info] jakarta.privacy.network

[info] philippines.privacy.network

[info] sanjose.privacy.network

[info] lu.privacy.network

[info] morocco.privacy.network

[info] fi.privacy.network

[info] ee.privacy.network

[info] tr.privacy.network

[info] in.privacy.network

[info] ua.privacy.network

[info] de-germany-so.privacy.network

[info] nigeria.privacy.network

[info] rs.privacy.network

[info] kr-south-korea-pf.privacy.network

[info] np-nepal-pf.privacy.network

[info] spain.privacy.network

[info] georgia.privacy.network

[info] taiwan.privacy.network

[info] sweden.privacy.network

[info] cambodia.privacy.network

[info] za.privacy.network

[info] kualalumpur.privacy.network

[info] bo-bolivia-pf.privacy.network

[info] nz.privacy.network

[info] saudiarabia.privacy.network

[info] au-adelaide-pf.privacy.network

[info] ca-ontario-so.privacy.network

[info] hk.privacy.network

[info] israel.privacy.network

[info] man.privacy.network

[info] br.privacy.network

[info] au-australia-so.privacy.network

2025-03-18 00:50:47,113 DEBG 'start-script' stdout output:

[info] ae.privacy.network

[info] dz.privacy.network

[info] italy-2.privacy.network

[info] santiago.privacy.network

[info] ba.privacy.network

[info] austria.privacy.network

[info] macau.privacy.network

[info] uk-2.privacy.network

[info] pe-peru-pf.privacy.network

[info] france.privacy.network

[info] au-brisbane-pf.privacy.network

[info] uy-uruguay-pf.privacy.network

[info] nl-netherlands-so.privacy.network

[info] de-berlin.privacy.network

[info] japan-2.privacy.network

[info] ec-ecuador-pf.privacy.network

[info] swiss.privacy.network

[info] md.privacy.network

[info] is.privacy.network

[info] qatar.privacy.network

[info] ca-vancouver.privacy.network

[info] ca-montreal.privacy.network

[info] bogota.privacy.network

[info] egypt.privacy.network

[info] uk-southampton.privacy.network

[info] aus-perth.privacy.network

[info] cyprus.privacy.network

[info] sg.privacy.network

[info] no.privacy.network

[info] bangladesh.privacy.network

[info] montenegro.privacy.network

[info] malta.privacy.network

[info] ireland.privacy.network

[info] japan.privacy.network

[info] lt.privacy.network

[info] sweden-2.privacy.network

[info] nl-amsterdam.privacy.network

[info] uk-london.privacy.network

[info] mk.privacy.network

[info] ro.privacy.network

[info] yerevan.privacy.network

[info] hungary.privacy.network

[info] ar.privacy.network

[info] aus-melbourne.privacy.network

[info] fi-2.privacy.network

[info] czech.privacy.network

[info] poland.privacy.network

[info] greenland.privacy.network

[info] panama.privacy.network

[info] al.privacy.network

[info] ca-toronto.privacy.network

[info] sofia.privacy.network

[info] srilanka.privacy.network

[info] denmark-2.privacy.network

[info] lv.privacy.network

[info] liechtenstein.privacy.network

[info] uk-manchester.privacy.network

[info] slovenia.privacy.network

[info] de-frankfurt.privacy.network

[info] gr.privacy.network

[info] vietnam.privacy.network

[info] ca-ontario.privacy.network

[info] brussels.privacy.network

[info] kazakhstan.privacy.network

[info] sk.privacy.network

[info] gt-guatemala-pf.privacy.network

[info] bahamas.privacy.network

Edited June 1, 20251 yr by wgstarks
added quote

Also, you will probably need to restart the docker after your edit.