-
[Support] binhex - qBittorrentVPN
Thanks, after disabling strict port forward I'm able to access the web UI. Unfortunately, the default login/password does not seem to be admin/adminadmin and I can't see any default password in the logs :(
-
[Support] binhex - qBittorrentVPN
Hello, I'm trying to use this container, but even though the connection to ProtonVPN using Wireguard seems ok, I can't access the Web UI. I've defined the Wireguard config in config/wireguard/wg0.conf after downloading the file from ProtonVPN site. If I disable the VPN, the Web UI works fine. Here is my docker run command, I have a doubt on VPN_USER and VPN_PASS, but I think they are useless when using Wireguard ? docker run -d --name='binhex-qbittorrentvpn' --net='my-custom-network' --pids-limit 2048 --privileged=true -e TZ="Europe/Paris" -e HOST_OS="Unraid" -e HOST_HOSTNAME="My-NAS" -e HOST_CONTAINERNAME="binhex-qbittorrentvpn" -e 'VPN_ENABLED'='yes' -e 'VPN_USER'='unused' -e 'VPN_PASS'='unused' -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'='1.1.1.1,1.0.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/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' Here are the logs from the container : 2026-03-10 21:56:58,850 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-03-10 21:56:59,863 DEBG 'start-script' stdout output: [debug] Valid VPN adapter IP from tunnel acquired '10.2.0.2' 2026-03-10 21:57:00,875 DEBG 'start-script' stdout output: [debug] Valid VPN gateway IP address from tunnel acquired '10.2.0.1' 2026-03-10 21:57:00,875 DEBG 'start-script' stdout output: [debug] Checking we can resolve name 'www.google.com' to address... 2026-03-10 21:57:00,907 DEBG 'start-script' stdout output: [debug] DNS operational, we can resolve name 'www.google.com' to address '172.217.22.164' 2026-03-10 21:57:01,024 DEBG 'start-script' stdout output: [info] Successfully retrieved external IP address 146.70.194.110 from URL 'http://checkip.amazonaws.com' 2026-03-10 21:57:01,025 DEBG 'start-script' stdout output: [info] Script started to assign incoming port for 'protonvpn' [debug] Waiting for valid VPN gateway IP addresses from tunnel... [debug] Waiting for valid VPN adapter IP addresses from tunnel... 2026-03-10 21:57:01,027 DEBG 'start-script' stdout output: [info] Successfully brought Wireguard interface 'up' 2026-03-10 21:57:02,040 DEBG 'start-script' stdout output: [debug] Valid VPN adapter IP from tunnel acquired '10.2.0.2' 2026-03-10 21:57:03,050 DEBG 'start-script' stdout output: [debug] Valid VPN gateway IP address from tunnel acquired '10.2.0.1' [info] ProtonVPN username 'unused' does not contain the suffix '+pmp' and therefore is not enabled for port forwarding, skipping port forward assignment... 2026-03-10 21:57:03,050 DEBG 'start-script' stdout output: [info] Script finished to assign incoming port Do you have any idea about what I am doing wrong ? Thanks in advance.
-
-
[Support] binhex - Flaresolverr
Hello, I'm trying to install Flaresolverr on my Unraid NAS, I just kept the standard configuration except the network that I changed to my custom one (like I do for all my containers), but when I try to open the web UI, I got a JSON response : {"error": "Method not allowed.", "status_code": 405} Is there a setting that I need to add to be able to reach the UI ? Thanks in advance !
-
How to change share's cache config without GUI
Thanks, it seems to have solved my issue !
-
How to change share's cache config without GUI
Hi everyone, Some times ago, I removed from my array (and physically from my server) the SSD that I was using a cache drive because I needed to use the port for a parity disk and my motherboard didn't have any left available. My problem is that my appdata share is still configured with "Use cache pool" set to "Only", and as a consequence some files are not saved to disk when stopping my server, and it causes issues for some containers at startup. So, I'd like to change the configuration of the share, but the "Use cache pool" option is grayed out (because I have no cache drive left I assume). Is there a way to change this configuration without the GUI ? Thanks in advance !
-
[Support] binhex - rTorrentVPN
Hello, I'm currently using this container with a PIA subscription, and I'm thinking to move to Proton VPN. I can't find the required options to set to use a custom VPN connection (VPN_PROV=custom) using Wireguard (VPN_CLIENT=wireguard), could someone please give me some details ? Thanks in advance. Regards
-
Wake on lan
Je réponds tardivement car je n'ai pu tester avant : il y a bien une option "boot from onboard LAN" qui n'était pas activée, mais ça n'a rien changé. Idem en désactivant le Deep Sleep.
-
Wirby joined the community
-
Wake on lan
Bonjour à tous, J'essaie de configurer le WoL sur mon serveur Unraid afin de l'allumer uniquement quand j'en ai besoin et ne plus le laisser tourner inutilement toute la journée. Je pense avoir activé les bons paramètres dans mon BIOS ("Enable ACPI", qui d'après la description permet de démarrer depuis le PCI Express ou le LAN intégré), mais dans Unraid je n'ai aucune trace du wol quand je lance la commande ethtool eth0. Si j'essaie de l'activer manuellement (ethtool -s eth0 wol g), j'ai cette erreur : netlink error: Operation not supported Est-ce que vous auriez une idée de ce que je fais mal ? Merci d'avance !
Wirby
Members
-
Joined
-
Last visited