binhex qbittorrent webgui no longer acces

Hello,

Please help me with the following. Since a couple of days I no longer can acces the webgui. Happened after a update I believe, not sure which one. This morning I saw that watchtower updated the binhex container but the problem still persists. Reboot didn't help either. I've generated a new wireguard file from mullvad and place that in the appropriate directory but still no go. Here is the log from the container:

2025-07-04 10:00:59,686 DEBG 'start-script' stdout output:
[info] WireGuard 'peer' not found, attempting to cycle WireGuard interface...

2025-07-04 10:00:59,687 DEBG 'start-script' stdout output:
[info] Attempting to bring WireGuard interface 'down'...

2025-07-04 10:00:59,700 DEBG 'start-script' stderr output:
Warning: `/config/wireguard/wg0.conf' is world accessible

2025-07-04 10:00:59,705 DEBG 'start-script' stderr output:
wg-quick: `wg0' is not a WireGuard interface

2025-07-04 10:00:59,705 DEBG 'start-script' stdout output:
[warn] Failed to bring 'down' WireGuard kernel implementation

2025-07-04 10:00:59,705 DEBG 'start-script' stdout output:
[info] Configuring WireGuard...

2025-07-04 10:00:59,724 DEBG 'start-script' stdout output:
[info] Attempting to bring WireGuard interface 'up'...

2025-07-04 10:00:59,737 DEBG 'start-script' stderr output:
Warning: `/config/wireguard/wg0.conf' is world accessible

2025-07-04 10:00:59,748 DEBG 'start-script' stderr output:
[#] ip link add dev wg0 type wireguard

2025-07-04 10:00:59,751 DEBG 'start-script' stderr output:
[#] wg setconf wg0 /dev/fd/63

2025-07-04 10:00:59,753 DEBG 'start-script' stderr output:
[#] ip -4 address add 10.72.201.82/32 dev wg0

2025-07-04 10:00:59,762 DEBG 'start-script' stderr output:
[#] ip link set mtu 1420 up dev wg0

2025-07-04 10:00:59,765 DEBG 'start-script' stderr output:
[#] resolvconf -a wg0 -m 0 -x

2025-07-04 10:00:59,776 DEBG 'start-script' stderr output:
could not detect a useable init system

2025-07-04 10:00:59,793 DEBG 'start-script' stderr output:
resolvconf: signature mismatch: /etc/resolv.conf

2025-07-04 10:00:59,795 DEBG 'start-script' stderr output:
resolvconf: run `resolvconf -u` to update

2025-07-04 10:00:59,804 DEBG 'start-script' stderr output:
[#] ip link delete dev wg0

2025-07-04 10:01:00,026 DEBG 'start-script' stdout output:
[warn] Failed to bring 'up' WireGuard kernel implementation


END OF LINE

Tried running this command on omv in ssh but the argument wasn't valid or something.

resolvconf -u

Any help is appreciated.

(btw it has been running smoothly for many months non stop until recently.)

Down, prune, pull > up didn't solve it. Everything else seems tot be in order. Perhaps unbound on opnsense is the problem.

Quote from gderf

AFAIK, all of these QBT with VPN images will not spawn the QBT WebUI interface unless and until there is a verified working VPN connection. This where you need to focus your attention.

I was aware of that. Gave me some headache while back when setting up. No mention of that behaviour in the readme etc. First thing I tried was setting up a new vpn connection.

Quote from BernH

If opnsense is blocking the vpn connection then that would cause problems. As gderf said, if a vpn connection can't be established then that will keep qbit with a vpn from working. Can you ping the vpn server from omv? If you temporarily disable the vpn for the container, can you vash into it and ping the vpn server?

I run an opnsense router at the office and I know from experience that they are a bit confusing to configure, but to be honest, I don't use the unbound setup in there, just the dnsmasq settings for local dns resolution.

Unbound acts as an authoritative dns for your lan, while dnsmasq is just a dns interceptor and forwarder so not as finicky to set up. If you have changed something in there recently it could be the root of the problem. You may also need to check your port forwards and/or whitelists/blacklists in there.

Ssh into omv I was able to ping 185.65.134.76 Have not touched opnsense, disabled unbound dns blocklist to see if that helps but no.

There is the problemen then. Will modify conf file tomorrow. Thank you for the info.

Latest image fixed the bug.