crowdx42

Well I just went back to the previous Unraid release and it works fine. Not sure why upgrading Unraid would have this effect though.

So I tried the latest Unraid update, 7.2.6 to 7.3.0 and had the issue with webui not working, reverted to previous version and everything works again. Weird.

I tried above and it resulted in the torrent webui showing as sabnzbd instead (it is the docker that uses port 8080). I then removed the torrent docker, did a fresh install using the default ports ( I changed sabnzbd port to 8081) and this finally worked. I then updated all my other dockers to connect using the 8080 port and all seems well. Thank you for all your help

I believe below is what is requested: docker run -d --name='binhex-qbittorrentvpn' --net='bridge' --pids-limit 2048 --privileged=true -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e HOST_HOSTNAME="UNRAID" -e HOST_CONTAINERNAME="binhex-qbittorrentvpn" -e 'VPN_ENABLED'='yes' -e 'VPN_USER'='xxxxxxx' -e 'VPN_PASS'='xxxxxx' -e 'VPN_PROV'='pia' -e 'VPN_CLIENT'='openvpn' -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'='8688' -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/templates/main/unraid/binhex/images/qbittorrent-icon.png' -p '8688: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/Finished_Torrents/':'/data':'rw' --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'ghcr.io/binhex/arch-qbittorrentvpn' bc177e209e8ba18f88d0178a28caa3fad51a5ba6672e6d4bb483b763a46ea249

Does the below log show what is needed? 2026-05-12 07:17:35,597 DEBG 'watchdog-script' stdout output: [debug] VPN incoming port is 26082 [debug] qBittorrent incoming port is 26082 [debug] VPN IP is 10.19.112.199 [debug] qBittorrent IP is 10.19.112.199 2026-05-12 07:18:05,602 DEBG 'watchdog-script' stdout output: [debug] Checking we can resolve name 'www.google.com' to address... 2026-05-12 07:18:05,650 DEBG 'watchdog-script' stdout output: [debug] DNS operational, we can resolve name 'www.google.com' to address '142.251.152.119 142.251.155.119 142.251.151.119 142.251.154.119 142.251.156.119 142.251.153.119 142.251.157.119 142.251.150.119' 2026-05-12 07:18:05,651 DEBG 'watchdog-script' stdout output: [debug] Waiting for iptables chain policies to be in place... 2026-05-12 07:18:05,662 DEBG 'watchdog-script' stdout output: [debug] iptables chain policies are in place 2026-05-12 07:18:05,667 DEBG 'watchdog-script' stdout output: [debug] VPN incoming port is 26082 [debug] qBittorrent incoming port is 26082 [debug] VPN IP is 10.19.112.199 2026-05-12 07:18:05,667 DEBG 'watchdog-script' stdout output: [debug] qBittorrent IP is 10.19.112.199 2026-05-12 07:18:33,775 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port 2026-05-12 07:18:35,673 DEBG 'watchdog-script' stdout output: [debug] Checking we can resolve name 'www.google.com' to address... 2026-05-12 07:18:35,720 DEBG 'watchdog-script' stdout output: [debug] DNS operational, we can resolve name 'www.google.com' to address '142.251.156.119 142.251.155.119 142.251.152.119 142.251.150.119 142.251.157.119 142.251.151.119 142.251.153.119 142.251.154.119' 2026-05-12 07:18:35,721 DEBG 'watchdog-script' stdout output: [debug] Waiting for iptables chain policies to be in place... 2026-05-12 07:18:35,731 DEBG 'watchdog-script' stdout output: [debug] iptables chain policies are in place 2026-05-12 07:18:35,737 DEBG 'watchdog-script' stdout output: [debug] VPN incoming port is 26082 [debug] qBittorrent incoming port is 26082 [debug] VPN IP is 10.19.112.199 2026-05-12 07:18:35,738 DEBG 'watchdog-script' stdout output: [debug] qBittorrent IP is 10.19.112.199 2026-05-12 07:19:05,744 DEBG 'watchdog-script' stdout output: [debug] Checking we can resolve name 'www.google.com' to address... 2026-05-12 07:19:05,792 DEBG 'watchdog-script' stdout output: [debug] DNS operational, we can resolve name 'www.google.com' to address '142.251.152.119 142.251.155.119 142.251.156.119 142.251.150.119 142.251.157.119 142.251.153.119 142.251.154.119 142.251.151.119' 2026-05-12 07:19:05,792 DEBG 'watchdog-script' stdout output: [debug] Waiting for iptables chain policies to be in place... 2026-05-12 07:19:05,803 DEBG 'watchdog-script' stdout output: [debug] iptables chain policies are in place 2026-05-12 07:19:05,809 DEBG 'watchdog-script' stdout output: [debug] VPN incoming port is 26082 [debug] qBittorrent incoming port is 26082 2026-05-12 07:19:05,809 DEBG 'watchdog-script' stdout output: [debug] VPN IP is 10.19.112.199 [debug] qBittorrent IP is 10.19.112.199 2026-05-12 07:19:35,815 DEBG 'watchdog-script' stdout output: [debug] Checking we can resolve name 'www.google.com' to address... 2026-05-12 07:19:35,863 DEBG 'watchdog-script' stdout output: [debug] DNS operational, we can resolve name 'www.google.com' to address '142.251.152.119 142.251.153.119 142.251.150.119 142.251.156.119 142.251.154.119 142.251.157.119 142.251.151.119 142.251.155.119' 2026-05-12 07:19:35,863 DEBG 'watchdog-script' stdout output: [debug] Waiting for iptables chain policies to be in place... 2026-05-12 07:19:35,871 DEBG 'watchdog-script' stdout output: [debug] iptables chain policies are in place 2026-05-12 07:19:35,877 DEBG 'watchdog-script' stdout output: [debug] VPN incoming port is 26082 [debug] qBittorrent incoming port is 26082 [debug] VPN IP is 10.19.112.199 [debug] qBittorrent IP is 10.19.112.199

Nope, I get site cannot be reached timeout. As for the ports, I have Port: Web Interface: set to 8687 and also the Variable: WEBUI_PORT: set to 8687. As stated previously, I have done a full reinstall of the docker with no joy. This was all working fine before I updated Unraid to 7.2.6. Below is the config for the docker. [AutoRun] enabled=false program= [BitTorrent] Session\AddTorrentStopped=false Session\Interface=tun0 Session\InterfaceName=tun0 Session\Port=49560 Session\QueueingSystemEnabled=true Session\SSL\Port=8930 Session\ShareLimitAction=Stop Session\UseRandomPort=false [Meta] MigrationVersion=8 [Network] Cookies=@Invalid() PortForwardingEnabled=false Proxy\HostnameLookupEnabled=false Proxy\Profiles\BitTorrent=true Proxy\Profiles\Misc=true Proxy\Profiles\RSS=true [Preferences] Connection\Interface=tun0 Connection\InterfaceName=tun0 Connection\PortRangeMin=6881 Connection\UPnP=false General\Locale=en General\UseRandomPort=false WebUI\Address=* WebUI\CSRFProtection=false WebUI\LocalHostAuth=false WebUI\Port=8687 WebUI\ServerDomains=* WebUI\UseUPnP=false

The laptop ip is 192.168.1.65 and the Unraid ip is 192.168.1.55.

Still no joy connecting, I updated teh ovpn file and I think in the attached log it shows it is working? supervisord.log

So here is the updated log, from the esponse above, I believe I needed to copy an ovpn file from PIA that allows port forwarding as shown in the list? I did a full fresh install and still no success. supervisord.log

Below I have attached my log. supervisord.log

Hi, I updated Unraid to 7.2.6 and after rebooting the server after the upgrade, I cannot access qbittorrent. I deleted the folder in app data and reinstalled and still no joy. Is there an incompatiblilty with the latest Unraid? Thank you for any help you can provide

With 192.168.1.0/24 the WebUI was getting page not found, whereas changing it to 192.168.1.2/24 fixed the issue and WebUI works. I am not sure of the reason why, only that it works now. Could it be that my gateway is 192.168.1.1 and so the router did not like having it's IP address included in the IP range?

That is the only thing that got it working for the WebUI.

I finally got it working, I changed Variable: LAN_NETWORK: setting to my network range and now it works, default was 192.168.1.0/24, I updated it to 192.168.1.2/24 .

well I finally got the WebUI working, but only with the VPN turned off. I use Private Internet Access, I have downloaded the OpenVPN files from their site and put them in the OpenVPN folder and from the logs it looks like it connected and was assigned an IP, but the WebUI still gives a page not found error. Thoughts? What should I be checking on the VPN side to make sure everything is working?

the IP shown is what I updated, the correct IP for the VPN shows correctly in the log.

below is from the log, I am using the most recent docker, I changed the qBittorent IP in the log to 99.99.99.99 for privacy: 026-02-19 15:22:34,723 DEBG 'watchdog-script' stdout output: [info] qBittorrent process listening on port 8585 2026-02-19 15:22:35,186 DEBG 'watchdog-script' stdout output: [debug] VPN incoming port is 22084 [debug] qBittorrent incoming port is 22084 [debug] VPN IP is 99.99.99.99 [debug] qBittorrent IP is 99.99.99.99 2026-02-19 15:23:05,192 DEBG 'watchdog-script' stdout output: [debug] Checking we can resolve name 'www.google.com' to address... 2026-02-19 15:23:05,388 DEBG 'watchdog-script' stdout output: [debug] DNS operational, we can resolve name 'www.google.com' to address '142.250.183.36' 2026-02-19 15:23:05,388 DEBG 'watchdog-script' stdout output: [debug] Waiting for iptables chain policies to be in place... 2026-02-19 15:23:05,399 DEBG 'watchdog-script' stdout output: [debug] iptables chain policies are in place 2026-02-19 15:23:05,408 DEBG 'watchdog-script' stdout output: [debug] VPN incoming port is 22084 [debug] qBittorrent incoming port is 22084 [debug] VPN IP is 99.99.99.99 [debug] qBittorrent IP is 99.99.99.99

But I am getting the error below, shoudl I not be able to get to the web-ui regardless?

I also have the same issue, I have not changed anything on the container and it has been running fine for months, but now I cannot access the web-ui. I tried doing a clean install with the same results (deleted the app data folder and did a full fresh setup unsing screen shots of my original settings that were working) Thoughts?

Yes, you have been great support for your product. Very happy with all your help.

I bought the openfan controller in January and today I hooked up 3 new Noctua fans, they ran for a while and then all the fans stopped. The docker will no longer run. Altogether there were 8 fans hooked up, could it be the board died? I notice there are 2 buttons on the board, do they do anything? All help welcome. Patrick

Also having issues with the latest update, getting the error below: /usr/sbin/init.sh: line 295: /usr/local/bin/dos2unix.sh: No such file or directory

Very cool, I have Open Fan Controller working with the docker, I think I will wait until there is an update with a less hack version lol

Is there anyone working on getting open fan to automate fab speeds based on drive temps?

The eBay seller has shipped a new backplane, once I get that installed I will try some testing again, most likely this will occur over the weekend. Until then, I will keep the server up or stop the array before shutting it down. I agree that it seems like sleep is initiating before the drives are able to do their sleep process and thus when the drives wake, Unraid does not find the drive correctly and this then sometimes ends in the drive getting the Red X beside it, as Unraid believes the drive dropped off the array before the array stopped.