binhex

if your issue is related to the DNS bug then this is fixed, switch back to 'latest' image then please toggle 'advanced view' (top right of docker ui) and then click on 'force update' to ensure you are running latest, if its still lbroken then yes please post logs here as per the link.

I will need to see a log to help further, please see the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md#unraid-users pleaase also past the contents of your /config/wireguard/wg0.conf file with sensitive info redacted.

I will need to see a log to help further, please see the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md#unraid-users

i have just built latest with the fix, so latest should now work too.

A new release has been pushed out, this forcibly removes the troublesome dns entry from the wireguard config file, please pull down latest and let me know how it goes.

from your log: resolvconf: signature mismatch: /etc/resolv.conf can you do the following: https://forums.unraid.net/topic/75539-support-binhex-qbittorrentvpn/page/186/#findComment-1565276

I have a test tagged image i would like you to try, PLEASE let me know the outcome,good or bad: Go to unraid web ui/docker and left click the container and select 'edit' Go to the 'Repository' line and append ':test' to te end Scroll to the bottom and click 'Apply' Wait a minute or so for the container to start, check logs and if it looks good check webui Report back here.

That's because the change is not on your end, its with your VPN provider, they have modified/deleted/broken the endpoint you are connecting to, re-download the openvpn config file from your vpn provider.

Thats because one is a listing of openvpn config files, and one is a listing of the actual remote endpoints you connect to.

in a word, no.

looks like the remote endpoint you are trying to connect to is not in a good state, from your log: 2025-06-30 10:44:21,092 DEBG 'start-script' stdout output: 2025-06-30 10:44:21 UDPv4 link remote: [AF_INET]64.188.16.131:443 2025-06-30 10:44:21,103 DEBG 'start-script' stdout output: 2025-06-30 10:44:21 read UDPv4 [ECONNREFUSED]: Connection refused (fd=3,code=111) my advise is to download a new openvpn config file for another endpoint.

then thats your issue, incorrect LAN_NETWORK, from your log: 2025-06-28 12:14:32.452942 [info] LAN_NETWORK defined as '192.168.1.0/24 Please see Q4 from the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

what is the ip address of the machine running the web browser?

I will need to see a log to help further, please see the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md#unraid-users

your not showing the section regards https cert and key, so either try the url as http, or sort out the cert and key, one or both of them are not found.

so what is the ip address of the machine?, is it within network 10.5.24.0?

what is LAN_NETWORK defined as? and what is the ip of the machine running the web browser that you are attempting connection from?.

When the qbittorrent dev's fix it (not me) and release a new version

Issue is now resolved and a new release has been published, please pull down at your convenience.

if you restart your container it should now allow it to run, this was an accidental inclusion of code which is not quite ready for prime time yet.

Im aware of the issue, Microsoft have changed their website and my scraper is thus failing, i shall fix it up, look out for a update today

You shouldn't need to do that Hey don't thank me, I just had the task of integrating it in @ChuckPaPlex is the author and deserves the praise here. 👏 Glad you are having good success with it.

that is a connectivity related issue and/or issues with the registry (probably github), try it again in 1 hour, if still no joy then take a look at your router.

Sorry, brain fart, i did mean 'no'.

you shouldn't need to do that, the script has a 'stop' argument, so 'DBRepair.sh stop' should of done the deed.