IMACRAB

Alright I have a different issue now: I cannot log in. Solved ✅ I tried earlier login data, and the default username and password: "admin" // "adminadmin". I also tried deleting user/appdata/binhex-qbittorrentvpn/qBittorrent/config/qBittorrent.conf + restart to generate a new one - didn't work. I also tested adding either of these two ideas as lines into the .conf - also to no avail. [Preferences] WebUI\AuthSubnetWhitelist=192.168.1.0/24 #use your local subnet WebUI\AuthSubnetWhitelistEnabled=trueWebUI\User=admin WebUI\Password_PBKDF2="@bytearray(72ycFfm20SU9J1917+v4rg==:rmIGmlb3YZukCUlIghBhnu/8ovMGEqloSqoIlga7Tfh/tm0m7uGgHibe/B/rpn7Bs65+SrVcp1AAtPKm5AoVfw==)"When deleting the .conf file, a file with the following info is created: qBittorrent.conf I tested logging in from different browsers and OS. Am I overlooking anything? Do I need to rollback to an earlier version? [EDIT] Found the solution. What worked for me:Downgraded to 4.6.0-1-01 binhex/arch-qbittorrentvpn:4.6.0-1-01 as mentioned here and followed it's step. I could log in right away using the default username and password: "admin" // "adminadmin". It all works now. Finally.

Alright. Found the issue, which was all to basic. The wireguard config lease expired. Creating a fresh config through Proton VPN did the trick. Should have thought about that before :S Thanks for your help guys 🙏

Had it turned off, even rebooted the qbit docker but still couldn’t access it. The logs also still show the unresolved Google issue

Would you have an idea how to pull that off? I was able to find out where to get the IP address to be "172.17.0.2". But now I'm not sure where to go with it in AdGuard Home. Whitelisting doesn't seem very straight forward there... I tried setting it up as a 'Client' and deselected global settings, but it didn't change anything. Would there be another way, or am I using the wrong IP?

Yes, I'm using AdGuard Home (also as DHCP host). Here however also nothing fundamentally changed - it's still running on Unraid. The only difference is that I now, completely cut out my Internet Box (Orange LiveBox) that I previously only used as a limited DHCP Host of two IPs (itself & unraid). + can this really be the issue why I cannot use the WebUI? Everything else seems to be launching fine

Apologies to jump in like this in-between conversations, @crowdx42 & @Wetterchen. I was just curious if 🐞the issue I'm having might be connected to what you are exchanging about? I have not yet reverted back to another any other version, but just updated from 7.2.6 to 7.3 today. Having had the mentioned issue already with 7.2.6, I'm more than puzzled as I can still not connect to the WebUI.

Hey there,Following a reassignment of my Unraid IP from 192.168.1.2 to 192.168.1.100 I cannot reach my WebUI anymore. All other services/dockers seem to have had no issue with the change and are running just fine as far as I can tell. Not being too much into networking or programming knowledge, I tried tackling it with Claude & the Github but just couldn't get there. Right now, when entering the IP for the WebUI, I get an error message that it cannot be reached no matter the browser. While Claude was hyper fixated on solving the DNS issue (which is not resolved), I also tried a rollback to version 5.1 (as mentioned for other pending issues) and of course reinstalling the docker. Nothing worked. When starting I get the following log: 2026-05-12 19:12:22,387 DEBG 'start-script' stdout output: -------------------- 2026-05-12 19:12:22,389 DEBG 'start-script' stdout output: [info] WireGuard 'peer' not found, attempting to cycle WireGuard interface... 2026-05-12 19:12:22,389 DEBG 'start-script' stdout output: [info] Attempting to bring WireGuard interface 'down'... [debug] Running WireGuard kernel implementation... 2026-05-12 19:12:22,399 DEBG 'start-script' stderr output: Warning: `/config/wireguard/wg0.conf' is world accessible 2026-05-12 19:12:22,404 DEBG 'start-script' stderr output: wg-quick: `wg0' is not a WireGuard interface 2026-05-12 19:12:22,404 DEBG 'start-script' stdout output: [warn] Failed to bring 'down' WireGuard kernel implementation 2026-05-12 19:12:22,405 DEBG 'start-script' stdout output: [info] Configuring WireGuard... 2026-05-12 19:12:22,417 DEBG 'start-script' stdout output: [info] Attempting to bring WireGuard interface 'up'... [debug] Running WireGuard kernel implementation... 2026-05-12 19:12:22,428 DEBG 'start-script' stderr output: Warning: `/config/wireguard/wg0.conf' is world accessible 2026-05-12 19:12:22,440 DEBG 'start-script' stderr output: [#] ip link add dev wg0 type wireguard 2026-05-12 19:12:22,443 DEBG 'start-script' stderr output: [#] wg addconf wg0 /dev/fd/63 2026-05-12 19:12:22,445 DEBG 'start-script' stderr output: [#] ip -4 address add 10.2.0.2/32 dev wg0 2026-05-12 19:12:22,455 DEBG 'start-script' stderr output: [#] ip link set mtu 1420 up dev wg0 2026-05-12 19:12:22,468 DEBG 'start-script' stderr output: [#] wg set wg0 fwmark 51820 2026-05-12 19:12:22,470 DEBG 'start-script' stderr output: [#] ip -4 rule add not fwmark 51820 table 51820 2026-05-12 19:12:22,472 DEBG 'start-script' stderr output: [#] ip -4 rule add table main suppress_prefixlength 0 2026-05-12 19:12:22,474 DEBG 'start-script' stderr output: [#] ip -4 route add 0.0.0.0/0 dev wg0 table 51820 2026-05-12 19:12:22,481 DEBG 'start-script' stderr output: [#] nft -f /dev/fd/63 2026-05-12 19:12:22,486 DEBG 'start-script' stderr output: [#] '/root/wireguardup.sh' 2026-05-12 19:12:22,493 DEBG 'start-script' stdout output: [debug] Waiting for valid VPN gateway IP addresses from tunnel... [debug] Waiting for valid VPN adapter IP addresses from tunnel... 2026-05-12 19:12:23,502 DEBG 'start-script' stdout output: [debug] Valid VPN adapter IP from tunnel acquired '10.2.0.2' 2026-05-12 19:12:24,509 DEBG 'start-script' stdout output: [debug] Valid VPN gateway IP address from tunnel acquired '10.2.0.1' 2026-05-12 19:12:24,509 DEBG 'start-script' stdout output: [debug] Checking we can resolve name 'www.google.com' to address... 2026-05-12 19:12:39,530 DEBG 'start-script' stdout output: [debug] Having issues resolving name 'www.google.com' [debug] Retrying in 5 secs... [debug] 11 retries left 2026-05-12 19:12:59,551 DEBG 'start-script' stdout output: [debug] Having issues resolving name 'www.google.com' [debug] Retrying in 5 secs... [debug] 10 retries leftdocker run -d --name='binhex-qbittorrentvpn' --net='bridge' --pids-limit 2048 --privileged=true -e TZ="Europe/Paris" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Gordon" -e HOST_CONTAINERNAME="binhex-qbittorrentvpn" -e 'VPN_ENABLED'='yes' -e 'VPN_USER'='xxx -e 'VPN_PASS'='xxx -e 'VPN_PROV'='protonvpn' -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' -e 'WEBUI_PORT'='8080' -e 'VPN_INPUT_PORTS'='' -e 'VPN_OUTPUT_PORTS'='' -e 'DEBUG'='true' -e 'VPN_OPTIONS'='' -e 'ENABLE_STARTUP_SCRIPTS'='no' -e 'USERSPACE_WIREGUARD'='no' -e 'NAME_SERVERS'='10.2.0.1' -e 'ENABLE_HEALTHCHECK'='yes' -e 'HEALTHCHECK_COMMAND'='' -e 'HEALTHCHECK_ACTION'='' -e 'HEALTHCHECK_HOSTNAME'='google.com' -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/templates/main/unraid/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' 3c07c9936ce35c9a69229207ff5f74e75322d7376a254033d7a7a6b1fc2deb55In addition, I attached my current docker settings. Any help is appreciated 🙏 /edit: Docker Run was added

Thanks both of you for the quick and elaborate answers! I always deleted the 'Domain' aspect which automatically greyed-out the connect button. Leaving WORKGROUP set and resetting the password to be sure it's the correct one worked in the end. Much appreciated.

Hello there, I was trying to open shared drives from my server on an Ubuntu laptop. While the folders do show up, I'm not quite sure what to enter in the displayed fields: Username Domain Password Username usually has my laptop username prewritten whereas Domain comes with 'WORKGROUP' prefilled. Those prefilled credentials do not work however. While I did try it with the users I have created on my server, it seems that I'm missing (at least) the 'Domain' information. Does anyone know where I could find that information? I'd be happy to be able to access the shared folders from my laptop as well. Thank you!

Hello, I was able to get my prowlarr up and running with flaresolverr. While some indexers work without an issue, some other, bigger indexers are throwing up the following error message: Does anyone here know how to solve this issue? I can visit the websites in question manually from my browser without any issue.

Hey, hey, I looked into it again and both yours and also the 'official' docker didn't work initially. After ticking off the 'Use Proxy' options within prowlarr it worked however. Would you know if I just misconfigured the Proxy options for prowlarr in that case or was it never meant to work with 'Use Proxy' turned on? These were my options: Thanks again for your help!

Hey, hey, I was off for a moment myself - thanks for looking into it again. Yes, it's the IP address of my Unraid Server. For reference, prowlarr uses the exact same address, but with a :9696 at the end. The :8191 is also not used by any other docker.

Thanks for the tip. Is it this one? docker run -d --name='binhex-prowlarr' --net='bridge' -e TZ="Europe/Paris" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Gordon" -e HOST_CONTAINERNAME="binhex-prowlarr" -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:9696]/' -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/prowlarr-icon.png' -p '9696:9696/tcp' -v '/mnt/user/appdata/binhex-prowlarr':'/config':'rw' 'binhex/arch-prowlarr' e55bf9753161d07da6aeb272004338a0f3b9fea8b369d53840417411057cf307 The command finished successfully!

What would be a good way to figure that out? I'm currently using mostly images made by you. That includes: FlareSolverr Prowlarr Sonarr QBitTorrent <- I should have succeeded to get my VPN up and running for this one

Thanks for coming back to me on this! That's very odd, because that is exactly what I did. I did not change anything throughout the installation of FlareSolverr either. And I got the following error from prowlarr when clicking to 'test':