32 minutes ago, PakledVueAdmin said:

Ok, you can ignore my last question as I got the Docker up and running to the point of getting to the login prompt. My only issue now is I can't figure out the default admin password. Can anyone help me with that? Again I'm on Unraid 7.0.1, with the docker that was last updated on 2/19/25.

check the log it will tell you the password (its dynamic if not set) /config/supervisord.log

Recently installed docker container from CA and added my wg0 config from my VPN provider. 

The container starts but the UI is inaccessible.  

• Firefox Reports: Can't Establish a Connection (Not a connection timed out)
• Chrome reports: Cant be reached (Refused to connect)

There are no conflicts with other containers for the webUI port (8080), even so, to do my due diligence, I followed all of the steps to change the port (internally and externally) but that didn't help so I reset it back to default.  I've also re-installed and configured the container to no avail.  This behavior also persisted through an Unraid upgrade.

 

I can't even curl the webUI from within the container ("Could not connect")

 

qbittorrentvpn-supervisord.txt
qbittorrentvpn-docker-run.txt

58 minutes ago, navigat0 said:

Recently installed docker container from CA and added my wg0 config from my VPN provider. 

The container starts but the UI is inaccessible.  

• Firefox Reports: Can't Establish a Connection (Not a connection timed out)
• Chrome reports: Cant be reached (Refused to connect)

There are no conflicts with other containers for the webUI port (8080), even so, to do my due diligence, I followed all of the steps to change the port (internally and externally) but that didn't help so I reset it back to default.  I've also re-installed and configured the container to no avail.  This behavior also persisted through an Unraid upgrade.

 

I can't even curl the webUI from within the container ("Could not connect")

 

qbittorrentvpn-supervisord.txt 20.42 kB · 0 downloads
qbittorrentvpn-docker-run.txt 1.39 kB · 0 downloads

form your log:-

[info] ProtonVPN 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

Hi - I am unable to connect to the web ui of my container.
Please see the attached cry for help

 

 

For me, I had to run the container with VPN NOT enabled at first - then I could get in, turns out that VPN was not connecting - switching to wireguard seems to have fixed that.

 

also had to manually set the initial admin password for some reason.

this equals 'adminadmin' if anyone needs it


WebUI\Password_PBKDF2="@ByteArray(ARQ77eY1NUZaQsuDHbIMCA==:0WMRkYTUWVT9wVvdDtHAjU9b3b7uB8NR1Gur2hmQCvCDpm39Q+PsJRJPaCU51dEiz+dTzh8qbPsL8WkFljQYFQ==)"

 

goes in the

 

qBittorrent.conf file  . . .

 

 

Edited April 11, 20251 yr by Fuzzydamnt

Can I get a sanity check on port-forwarding? I use AirVPN and I have my wg0 config file placed in the right folder and my qbit set to the same port as I set in AirVPN's site, not the configuration file (12345, for example).

 

When I check canyouseeme(dot)org on a browser that I route through qbit, it shows my exit vpn but it says port 12345 is closed. The same is true when I go to AirVPN's port page and 'test' the port - connection refused.

 

Do I need to add 12345 to my VPN_OUTPUT_PORTS field? I looked at the VPN FAQs and only saw Q27 where it was talking about accessing other routed containers on my lan (though, I'm able to do so with their WebUI ports on my VPN_INPUT_PORTS field, not ouput). 

 

I tested adding 12345 to my VPN_OUTPUT_PORTS field and canyouseeme(dot)org says I'm good now. I checked IPLeak(dot)net and it only showed my exit IP and my forwarded port (though, it showed the same forwarded port even before I added 12345 to my output variable). I want to make sure I'm able to seed as many Linux isos as possible. Thanks 

Edited April 12, 20251 yr by Shu

On 4/12/2025 at 3:58 AM, Shu said:

I tested adding 12345 to my VPN_OUTPUT_PORTS field and canyouseeme(dot)org says I'm good now

dont do that, you have in effect punched a hole in your vpn network allowing incoming connections to that port. all you need to do is go to airvpn vpn provider, get yourself a incoming port, configure qbittorrent to use it, and thats it!, (don't port forward on your router).

41 minutes ago, binhex said:

dont do that, you have in effect punched a hole in your vpn network allowing incoming connections to that port. all you need to do is go to airvpn vpn provider, get yourself a incoming port, configure qbittorrent to use it, and thats it!, (don't port forward on your router).

Thank you for the reply. I didn't add the port forward on the router side; just within the docker config area. I've now removed 12345 from VPN_OUTPUT_PORTS. Though, when I tried IPLeak(dot)net with 12345 in that ouput field, I only saw my exit vpn and port - do you think it's still the case where I should not have it? I want to make sure I'm easily connectable by peers (and safely connectable) 

 

Edit: I've read that PIA does the port-forwarding within the vpn-config-file automatically but I don't think AirVPN has something similar - that's part of the reason I'm wondering if there's some manual setup I have to do (other than enable the port forward option on AirVPN's side and set my qBit to use that same port)

Edited April 13, 20251 yr by Shu
typo

I'm prefacing this with the fact that i'm brand new to Unraid, but i'm having a hell of a time getting torrents to seed, and i'm assuming its a lack of port forward on my setup. I can port forward until the cows come home, i just cant for the life of me figure out WHAT port needs to be forwarded. I'm using PIA w/ openvpn. As a note however, i did try (as a test) to dmz the address of my server in my router to see if that would make a difference and it did not.

I'm sure this is just a lack of understanding on my end of where i need to find the info

3 hours ago, pkaiser86 said:

dmz the address of my server in my router

Never do this 

12 hours ago, Shu said:

do you think it's still the case where I should not have it?

yes

 

12 hours ago, Shu said:

I've read that PIA does the port-forwarding within the vpn-config-file automatically but I don't think AirVPN has something similar

correct, it does not.

 

12 hours ago, Shu said:

I'm wondering if there's some manual setup I have to do (other than enable the port forward option on AirVPN's side and set my qBit to use that same port)

nope, that is all you have to do.

4 hours ago, pkaiser86 said:

I'm prefacing this with the fact that i'm brand new to Unraid, but i'm having a hell of a time getting torrents to seed, and i'm assuming its a lack of port forward on my setup. I can port forward until the cows come home, i just cant for the life of me figure out WHAT port needs to be forwarded. I'm using PIA w/ openvpn. As a note however, i did try (as a test) to dmz the address of my server in my router to see if that would make a difference and it did not.

I'm sure this is just a lack of understanding on my end of where i need to find the info

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

Hey there binhex, not a config issue but still something urgent:

 

qbittorrent 5.0.4 is getting blacklisted/banned on many forums and trackers as there seem to be issues with it, 5.0.5 has been out for the last two days and the general recommendation is to upgrade to it. I really don't want to annoy you but is there an ETA for the updated container?

All the best and thank you for your hard work!

4 hours ago, styx.techno said:

Hey there binhex, not a config issue but still something urgent:

 

qbittorrent 5.0.4 is getting blacklisted/banned on many forums and trackers as there seem to be issues with it, 5.0.5 has been out for the last two days and the general recommendation is to upgrade to it. I really don't want to annoy you but is there an ETA for the updated container?

All the best and thank you for your hard work!

awaiting on upstream update from here https://archlinux.org/packages/extra/x86_64/qbittorrent-nox/, once its updated then it will be auto built

Was going to just delete this but leaving for others in case someone stumbles on similar problems.

 

Q: In this release there's no "Torrent Creator" like the Win version, where is it? 

A: Man, it's been years since I've used the Win client, but I read they removed it and I assume from this docker image as well.    I found a CLI tool that works for now.

 

Q: I can't add trackers.  No dialog box pops up. 

A: Trackers are per torrent file.  So once the torrent has been added, then the "Add Trackers" shows up accepting input.

Edited April 18, 20251 yr by yoleska

15 hours ago, yoleska said:

Q: In this release there's no "Torrent Creator" like the Win version, where is it? 

A: Man, it's been years since I've used the Win client, but I read they removed it and I assume from this docker image as well.    I found a CLI tool that works for now.

If you install VueTorrent (alternative web ui) then this comes with a torrent creation tool:-

On 4/11/2025 at 8:03 PM, Fuzzydamnt said:

this equals 'adminadmin' if anyone needs it


WebUI\Password_PBKDF2="@ByteArray(ARQ77eY1NUZaQsuDHbIMCA==:0WMRkYTUWVT9wVvdDtHAjU9b3b7uB8NR1Gur2hmQCvCDpm39Q+PsJRJPaCU51dEiz+dTzh8qbPsL8WkFljQYFQ==)"

 

goes in the

 

qBittorrent.conf file  . . .

 

 

 

I add this line and when I restart container it get's removed. I can't login, any ideas?

Hi! I'm unsure of the reason but my qBittorrentvpn's webui became unreachable, if I turn off VPN it works. I reinstalled the image fresh and got the VPN details again, it's still the same. Was hoping to get some help here, thank you!

command-execution.txt supervisord.log

11 hours ago, vaahr said:

Hi! I'm unsure of the reason but my qBittorrentvpn's webui became unreachable, if I turn off VPN it works. I reinstalled the image fresh and got the VPN details again, it's still the same. Was hoping to get some help here, thank you!

command-execution.txt 1.39 kB · 1 download supervisord.log 31.92 kB · 1 download

what is the ip address of the machine running the web browser that you are using to attempt connection to qbittorrent web ui?

The ip is 192.168.1.129.

Hey there,

I can't acces the WebUI anymore. It worked fine, up until some days ago but I'm not sure what changed. I might have changed some network settings but nothing that should interfere with the docker.

When I disable the VPN everything works fine, as soon as VPN is enabled its not reachable anymore but

 docker exec -it binhex-qbittorrentvpn curl http://localhost:8080

will return HTML code describing the interface:

<head>
    <meta charset="UTF-8" />
    <meta http-equiv="X-UA-Compatible" content="IE=10" />
    <meta name="application-name" content="qBittorrent" />
    <meta name="description" content="qBittorrent WebUI">
    <meta name="viewport" content="width=device-width, initial-scale=1.0">

    <title>qBittorrent WebUI</title>

    <link rel="icon" type="image/png" href="images/qbittorrent32.png" sizes="32x32" />
    <link rel="icon" type="image/svg+xml" href="images/qbittorrent-tray.svg" sizes="any" />
    <link rel="stylesheet" type="text/css" href="css/dynamicTable.css?v=w3dtn5" />
    <link rel="stylesheet" type="text/css" href="css/style.css?v=w3dtn5" />
    <!--<link rel="stylesheet" type="text/css" href="css/Content.css" />-->
    <link rel="stylesheet" type="text/css" href="css/Core.css?v=w3dtn5" />
    <link rel="stylesheet" type="text/css" href="css/Layout.css?v=w3dtn5" />
    <link rel="stylesheet" type="text/css" href="css/Window.css?v=w3dtn5" />
    <link rel="stylesheet" type="text/css" href="css/Tabs.css?v=w3dtn5" />
    <noscript>

So it seems like its running, and I just cant reach it anymore.

 

Thanks in advance for any possible solutions.

 

command execution.txt supervisord.log

Having the same problem, the logs show the last entry as:

 

"[info] Trying to connect to the PIA WireGuard API on 'au-sydney.privacy.network'..."

 

And it will never make it past that, I tried swapping and replacing the .ovpn files but still doesn't work.

15 hours ago, vaahr said:

The ip is 192.168.1.129.

ok that all looks fine, no obvious issues, i can see qbittorrent has started, ensure its not tailscale getting in the way, Please see Q36 from the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Swapping the VPN client from Wireguard to Openvpn fixed it for me.

12 hours ago, barley97 said:

Hey there,

I can't acces the WebUI anymore. It worked fine, up until some days ago but I'm not sure what changed. I might have changed some network settings but nothing that should interfere with the docker.

When I disable the VPN everything works fine, as soon as VPN is enabled its not reachable anymore but

 docker exec -it binhex-qbittorrentvpn curl http://localhost:8080

will return HTML code describing the interface:

<head>
    <meta charset="UTF-8" />
    <meta http-equiv="X-UA-Compatible" content="IE=10" />
    <meta name="application-name" content="qBittorrent" />
    <meta name="description" content="qBittorrent WebUI">
    <meta name="viewport" content="width=device-width, initial-scale=1.0">

    <title>qBittorrent WebUI</title>

    <link rel="icon" type="image/png" href="images/qbittorrent32.png" sizes="32x32" />
    <link rel="icon" type="image/svg+xml" href="images/qbittorrent-tray.svg" sizes="any" />
    <link rel="stylesheet" type="text/css" href="css/dynamicTable.css?v=w3dtn5" />
    <link rel="stylesheet" type="text/css" href="css/style.css?v=w3dtn5" />
    <!--<link rel="stylesheet" type="text/css" href="css/Content.css" />-->
    <link rel="stylesheet" type="text/css" href="css/Core.css?v=w3dtn5" />
    <link rel="stylesheet" type="text/css" href="css/Layout.css?v=w3dtn5" />
    <link rel="stylesheet" type="text/css" href="css/Window.css?v=w3dtn5" />
    <link rel="stylesheet" type="text/css" href="css/Tabs.css?v=w3dtn5" />
    <noscript>

So it seems like its running, and I just cant reach it anymore.

 

Thanks in advance for any possible solutions.

 

command execution.txt 1.36 kB · 2 downloads supervisord.log 88.65 kB · 1 download

There looks to be an issue with your openvpn config file, it seems to be causing some sort of routing issue, from your log:-
 

2025-04-21 20:53:03,115 DEBG 'start-script' stdout output:
2025-04-21 20:53:03 us=115049 Recursive routing detected, drop tun packet to [AF_INET]95.181.232.15:443

2025-04-21 20:53:06,008 DEBG 'start-script' stdout output:
2025-04-21 20:53:06 us=8401 Recursive routing detected, drop tun packet to [AF_INET]95.181.232.15:443

2025-04-21 20:53:07,147 DEBG 'start-script' stdout output:
2025-04-21 20:53:07 us=147256 Recursive routing detected, drop tun packet to [AF_INET]95.181.232.15:443

Not sure if this is the cause of the inability to access the web ui, but in any case i would get that sorted first.

4 minutes ago, Hendo said:

Swapping the VPN client from Wireguard to Openvpn fixed it for me.

most probably you were connecting to a non port forward enabled endpoint and had STRICT_PORT_FORWARD set to yes, but without logs we will never know - 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