Hi, actually you could post bugs in the github repo as said in the log. However, for sure you are free not to use it.
The default login info not working is an upstream qbittorrent bug : [BUG] the 4.6.1 release breaks the web ui login · Issue #268 · linuxserver/docker-qbittorrent (github.com)
It is likely that it would be solved in the future
Edit : new addon version pushed should solve it
Hi, sorry this thread is about the addon, not the integration
Sorry, can’t repliacte here it is working in a very stable manner… I would encourage you to post a bug report in the github repo if you have additional issues but it could be more linked to the HA supervisor more than the addon or the issue would be more widespread…
Thanks for the reply, that explains it.
I found an old comment from you (2021) that mentions that the Web GUI is fixed for ingress. Using IP,port does work with the differente web UI options. Perhaps you can add this to the opening post, it’s not very evident.
Hi, actually perhaps I can look again to adapt the ingress ui based on the add-on option. I avoided doing that at the time this add-on was dev as people had to manually clear the browser cache, and it would have been confusing for a lot of people. Perhaps how I can find a way to avoiding caching the webUI altogether
Ok I’ve implemented the fact that changing webui now works for ingress! Doesn’t seem to work for qbit-matui though I’ll probably remove it from the options
EDIT : actually the default webui is not supported by ingress as qbittorrent does not expose its index.html file…
Hello,
I have a problem with web UI login;
When add-on is running with openVPN disabled I’m able to login into web UI, both from ingress and from myIP:8081.
When I turn on openVPN and I try to login, every time it replies with “Login Failed”.
Anyone can help me?
Thanks
Could you try the open on alternate connection mode? It is in the add-on options.
I believe what happens is that the whole addon network is tunnelled through vpn preventing a local ip access. The alternate vpn mode applies it at the level of bittorrent, not the container, in theory allowing access to local ip if I remember correctly
Thanks
I will also be interested by using wireguard with qbittorrent if it’s possible in future.
I have the save problem of speed with openvpn.
But the addon work already very well, thanks a lot for the work
Hi, well an alternative could be that I fully change the image to one already containing open vpn and wireguard. But there is a high probability of breaking changes as it would mean changing the container my add-on is based on
Hi, I’m looking for people interested in a v2 of my qbittorrent addon : that would support natively both openvpn and wireguard based on trigus42/qbittorrentvpn instead of instead of linuxserver/docker-qbittorrent (github.com). Anyone interested? The most important thing is to check if there is a seemless transition between the current and the new versions before I migrate the whole addon
I solved! thanks!
Multiple issues with the recent Qbittorrent update, sorry.
I have mounted folder on my Synology server, //XXX.XXX.XXX.XXX/video/NewArrivals, everything worked for a very long time, multiple updates. However the updated version has the following problems:
Another problem with the new version, it’s a one-way door. I tried rolling back to the previous version, it wont start as the update moved all the directories around, the earlier version tries to find files in /etc/openvpn/config.ovpn and fails as it’s been moved. I’m glad I did full backup prior to update
Hi, I suppose you read the changelog describing all the breaking changes? 
Indeed this aligns with the new way Homeassistant manages config locations, for all future updates. Pleas repost a log otherwise there is nothing I can help with…
ovpn files aren’t an issue. Not handling networkdisks at all is
When networkdisks is re-added, I have no new log messages and a logon prompt which rejects any password I can think of
I’m sorry but i cannot provide support without a full log…there can be so many reasons. This is why i avoid nowadays to come on these forums and only provide support via the github repository.
I do not experience your issues with network disks but someone has raised also an issue. This is unexpected as this new code to mount smb drives was put up last month and I think there was a new addon version since. Also, this add-ons performs automatic restarts to take into account configurations changes.
And btw : the fact of not being able to log is mostly likely due to the absence of a password in your configuration file which is now a requirement. The configuration script should automatically add “homeassistant” as default password if there was no preexisting one, then restart the addon
And your obviously it fails due to the lack of permissions and reports “host down” has a logic that I do not understand : the script checks if the locations can be accessed using the user writes described in the addon options. It is therefore normal that it fails if it lacks permissions. Which with I log I can see if it stems with an incorrect configuration on your side, or an incorrect passing of the permissions arguments on mine
Without networkdisks option the logon window appears for a split second and then goes away with regular dashboard. With networkdisks set, the logon window stays, rejecting any password I tried, that including “homeassistant”, “adminadmin”, my own password, cif credentials, etc
hi @alexbelgium, I have the same issue as @relyef. Long-time user. Addon doesn’t start after the 4.6.2 updates. I did read the breaking changes but fail to see what I need to do. Here’s the log:
2023-12-11 05:16:22 [INFO] Starting OpenVPN...
--------------------
2023-12-11 05:16:22 DEPRECATED OPTION: --cipher set to 'AES-256-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305). OpenVPN ignores --cipher for cipher negotiations.
2023-12-11 05:16:22 WARNING: file '/config/openvpn/mullvad_cz_prg_credentials.conf' is group or others accessible
2023-12-11 05:16:22 OpenVPN 2.6.5 x86_64-alpine-linux-musl [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD]
2023-12-11 05:16:22 library versions: OpenSSL 3.1.4 24 Oct 2023, LZO 2.10
2023-12-11 05:16:22 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
2023-12-11 05:16:22 TCP/UDP: Preserving recently used remote address: [AF_INET]146.70.129.162:1301
2023-12-11 05:16:22 Socket Buffers: R=[212992->1048576] S=[212992->1048576]
2023-12-11 05:16:22 UDPv4 link local: (not bound)
2023-12-11 05:16:22 UDPv4 link remote: [AF_INET]146.70.129.162:1301
2023-12-11 05:16:22 TLS: Initial packet from [AF_INET]146.70.129.162:1301, sid=7d24ce38 94fb0e7a
2023-12-11 05:16:22 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
2023-12-11 05:16:22 VERIFY OK: depth=2, C=SE, ST=Gotaland, L=Gothenburg, O=Amagicom AB, OU=Mullvad, CN=Mullvad Root CA v2, [email protected]
2023-12-11 05:16:22 VERIFY OK: depth=1, C=SE, ST=Gotaland, O=Amagicom AB, OU=Mullvad, CN=Mullvad Intermediate CA v6, [email protected]
2023-12-11 05:16:22 VERIFY KU OK
2023-12-11 05:16:22 Validating certificate extended key usage
2023-12-11 05:16:22 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
2023-12-11 05:16:22 VERIFY EKU OK
2023-12-11 05:16:22 VERIFY OK: depth=0, C=SE, ST=Gotaland, O=Amagicom AB, OU=Mullvad, CN=cz-prg-ovpn-101.mullvad.net, [email protected]
2023-12-11 05:16:22 Control Channel: TLSv1.3, cipher TLSv1.3 TLS_CHACHA20_POLY1305_SHA256, peer certificate: 4096 bit RSA, signature: RSA-SHA256
2023-12-11 05:16:22 [cz-prg-ovpn-101.mullvad.net] Peer Connection Initiated with [AF_INET]146.70.129.162:1301
2023-12-11 05:16:22 TLS: move_session: dest=TM_ACTIVE src=TM_INITIAL reinit_src=1
2023-12-11 05:16:22 TLS: tls_multi_process: initial untrusted session promoted to trusted
2023-12-11 05:16:23 SENT CONTROL [cz-prg-ovpn-101.mullvad.net]: 'PUSH_REQUEST' (status=1)
2023-12-11 05:16:24 PUSH: Received control message: 'PUSH_REPLY,dhcp-option DNS 10.15.0.1,redirect-gateway def1 bypass-dhcp,route-ipv6 0000::/2,route-ipv6 4000::/2,route-ipv6 8000::/2,route-ipv6 C000::/2,route-gateway 10.15.0.1,topology subnet,socket-flags TCP_NODELAY,ifconfig-ipv6 fdda:d0d0:cafe:1301::1002/64 fdda:d0d0:cafe:1301::,ifconfig 10.15.0.4 255.255.0.0,peer-id 2,cipher AES-256-GCM,protocol-flags cc-exit tls-ekm dyn-tls-crypt,tun-mtu 1500'
2023-12-11 05:16:24 Pushed option removed by filter: 'route-ipv6 0000::/2'
2023-12-11 05:16:24 Pushed option removed by filter: 'route-ipv6 4000::/2'
2023-12-11 05:16:24 Pushed option removed by filter: 'route-ipv6 8000::/2'
2023-12-11 05:16:24 Pushed option removed by filter: 'route-ipv6 C000::/2'
2023-12-11 05:16:24 Pushed option removed by filter: 'ifconfig-ipv6 fdda:d0d0:cafe:1301::1002/64 fdda:d0d0:cafe:1301::'
2023-12-11 05:16:24 OPTIONS IMPORT: --socket-flags option modified
2023-12-11 05:16:24 NOTE: setsockopt TCP_NODELAY=1 failed
2023-12-11 05:16:24 OPTIONS IMPORT: --ifconfig/up options modified
2023-12-11 05:16:24 OPTIONS IMPORT: route options modified
2023-12-11 05:16:24 OPTIONS IMPORT: route-related options modified
2023-12-11 05:16:24 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
2023-12-11 05:16:24 OPTIONS IMPORT: tun-mtu set to 1500
2023-12-11 05:16:24 ROUTE_GATEWAY 172.30.32.1/255.255.254.0 IFACE=eth0 HWADDR=02:42:ac:1e:21:05
2023-12-11 05:16:24 TUN/TAP device tun0 opened
2023-12-11 05:16:24 /sbin/ip link set dev tun0 up mtu 1500
2023-12-11 05:16:24 /sbin/ip link set dev tun0 up
2023-12-11 05:16:24 /sbin/ip addr add dev tun0 10.15.0.4/16
2023-12-11 05:16:24 /sbin/ip route add 146.70.129.162/32 via 172.30.32.1
2023-12-11 05:16:24 /sbin/ip route add 0.0.0.0/1 via 10.15.0.1
2023-12-11 05:16:24 /sbin/ip route add 128.0.0.0/1 via 10.15.0.1
2023-12-11 05:16:24 Initialization Sequence Completed
2023-12-11 05:16:24 Data Channel: cipher 'AES-256-GCM', peer-id: 2
2023-12-11 05:16:24 Timers: ping 10, ping-restart 60
2023-12-11 05:16:24 Protocol options: protocol-flags cc-exit tls-ekm dyn-tls-crypt
--------------------
[cont-init.d] 02-vpn.sh: exited 0.
[cont-init.d] 03-network.sh: executing...
2023-12-11 05:16:25 [INFO] Adding localhost as route via docker eth0
2023-12-11 05:16:25 [WARNING] Error adding route for localhost. The web interface won't be reachable for the affected network
2023-12-11 05:16:25 [INFO] Adding 127.0.0.1 as route via docker eth0
2023-12-11 05:16:25 [INFO] Adding 172.30.0.0/16 as route via docker eth0
2023-12-11 05:16:25 [INFO] Adding 192.168.0.0/16 as route via docker eth0
2023-12-11 05:16:25 [INFO] Adding additional incoming port 59595 for eth0
2023-12-11 05:16:25 [INFO] Adding additional incoming port 6882 for eth0
2023-12-11 05:16:25 [INFO] Adding additional outgoing port 59595 for eth0
2023-12-11 05:16:25 [INFO] Adding additional outgoing port 6882 for eth0
[cont-init.d] 03-network.sh: exited 0.
[cont-init.d] 03-nginx_ssl.sh: executing...
[cont-init.d] 03-nginx_ssl.sh: exited 0.
[cont-init.d] 04-qbittorrent-setup.sh: executing...
2023-12-11 05:16:25 [WARNING] ENABLE_SSL is set to no, SSL is not enabled. This could cause issues with logging if other apps use the same Cookie name (SID).
2023-12-11 05:16:25 [WARNING] If you manage the SSL config yourself, you can ignore this.
2023-12-11 05:16:25 [WARNING] UMASK not defined (via -e UMASK), defaulting to '002'
[cont-init.d] 04-qbittorrent-setup.sh: exited 0.
[cont-init.d] 05-install.sh: executing...
[cont-init.d] 05-install.sh: exited 0.
[cont-init.d] 90-dns_set.sh: executing...
2023-12-11 05:16:25 write UDPv4 []: Operation not permitted (fd=3,code=1)
[05:16:35] WARNING: DNS 8.8.8.8 was requested but can't be pinged. It won't be used
2023-12-11 05:16:35 write UDPv4 []: Operation not permitted (fd=3,code=1)
[05:16:45] WARNING: DNS 1.1.1.1 was requested but can't be pinged. It won't be used
2023-12-11 05:16:45 write UDPv4 []: Operation not permitted (fd=3,code=1)
[05:16:55] WARNING: DNS 192.168.0.1 was requested but can't be pinged. It won't be used
[05:16:55] WARNING: No valid DNS were found. Using default router (or HA) dns servers.
[cont-init.d] 90-dns_set.sh: exited 0.
[cont-init.d] 91-qbittorrent_configuration.sh: executing...
2023-12-11 05:16:55 write UDPv4 []: Operation not permitted (fd=3,code=1)
[05:16:55] INFO: Downloads can be found in /mnt/Public/Downloads
2023-12-11 05:17:06 write UDPv4 []: Operation not permitted (fd=3,code=1)
2023-12-11 05:17:16 write UDPv4 []: Operation not permitted (fd=3,code=1)
2023-12-11 05:17:24 [cz-prg-ovpn-101.mullvad.net] Inactivity timeout (--ping-restart), restarting
2023-12-11 05:17:24 SIGUSR1[soft,ping-restart] received, process restarting
2023-12-11 05:17:24 Restart pause, 1 second(s)
2023-12-11 05:17:25 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
2023-12-11 05:17:25 TCP/UDP: Preserving recently used remote address: [AF_INET]146.70.129.162:1301
2023-12-11 05:17:25 Socket Buffers: R=[212992->1048576] S=[212992->1048576]
2023-12-11 05:17:25 NOTE: setsockopt TCP_NODELAY=1 failed
2023-12-11 05:17:25 UDPv4 link local: (not bound)
2023-12-11 05:17:25 UDPv4 link remote: [AF_INET]146.70.129.162:1301
2023-12-11 05:17:25 write UDPv4 []: Operation not permitted (fd=3,code=1)
2023-12-11 05:17:28 write UDPv4 []: Operation not permitted (fd=3,code=1)
2023-12-11 05:17:32 write UDPv4 []: Operation not permitted (fd=3,code=1)
2023-12-11 05:17:40 write UDPv4 []: Operation not permitted (fd=3,code=1)
2023-12-11 05:17:56 write UDPv4 []: Operation not permitted (fd=3,code=1)
I see the info about required password but the migration script did not add any. Tried adding QBT_PASSWORD: homeassistant into the config, to no avail.