3 minutes ago, R0Bzombie said:

Hi, how do I downgrade?

I updated to latest version today and started having problems.

Thank you

On 6/30/2025 at 8:37 AM, wgstarks said:

You append a colon and tag number to the text already in the repository field.

You can get the tag numbers here.

Thank you for the quick replies

On 6/27/2025 at 9:24 AM, gustyScanner said:

Hello!

I have been using wireguard successfully for a long time with this container, today though when the container restarted I got the following error:

2025-06-27 10:35:26,490 DEBG 'start-script' stderr output:

[#] ip link add dev wg0 type wireguard

2025-06-27 10:35:26,492 DEBG 'start-script' stderr output:

[#] wg setconf wg0 /dev/fd/63

2025-06-27 10:35:26,493 DEBG 'start-script' stderr output:

[#] ip -4 address add 10.2.0.2/32 dev wg0

2025-06-27 10:35:26,499 DEBG 'start-script' stderr output:

[#] ip link set mtu 1420 up dev wg0

2025-06-27 10:35:26,501 DEBG 'start-script' stderr output:

[#] resolvconf -a wg0 -m 0 -x

2025-06-27 10:35:26,508 DEBG 'start-script' stderr output:

could not detect a useable init system

2025-06-27 10:35:26,521 DEBG 'start-script' stderr output:

resolvconf: signature mismatch: /etc/resolv.conf

2025-06-27 10:35:26,522 DEBG 'start-script' stderr output:

resolvconf: run resolvconf -u to update

2025-06-27 10:35:26,529 DEBG 'start-script' stderr output:

[#] ip link delete dev wg0

2025-06-27 10:35:26,623 DEBG 'start-script' stdout output:

[warn] Failed to bring 'up' WireGuard kernel implementation

I am unsure what I should do to fix this, I see issues with resolvconf but since this is on startup am unsure what I should do. For now I switched to OpenVPN which is working successfully.

EDIT:
If I open the console of the container and do cat /etc/resolv.conf I see several different IP addresses listed. I recognize some like 1.1.1.1 as GOogle's DNS

nameserver 84.200.69.80

nameserver 37.235.1.174

nameserver 1.1.1.1

nameserver 37.235.1.177

nameserver 84.200.70.40

nameserver 1.0.0.1

EDIT 2:

I was able to resolve this by removing the DNS portion of my wg0.conf file

hey i am having the same error as you. i cant get wireguard or opendns configs to work. qbitt works if i disable vpn in the container template. i tried commenting out the "DNS = x.x.x.x" line in the wireguard config file and it didnt fix anything. what exactly did you do?

5 hours ago, Randyd718 said:

hey i am having the same error as you. i cant get wireguard or opendns configs to work. qbitt works if i disable vpn in the container template. i tried commenting out the "DNS = x.x.x.x" line in the wireguard config file and it didnt fix anything. what exactly did you do?

I have a test tagged image i would like you to try, PLEASE let me know the outcome,good or bad:

1. Go to unraid web ui/docker and left click the container and select 'edit'

2. Go to the 'Repository' line and append ':test' to te end

3. Scroll to the bottom and click 'Apply'

4. Wait a minute or so for the container to start, check logs and if it looks good check webui

5. Report back here.

Not working here, log attached.

5.1.0-1-01 is fine.

qb.log

I had the same problem, updated to latest today and no wg connection. After reverting back to 5.1.0-1-01 it works.

7 hours ago, Kilrah said:

Not working here, log attached.

5.1.0-1-01 is fine.

qb.log

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

51 minutes ago, binhex said:

can you do the following: https://forums.unraid.net/topic/75539-support-binhex-qbittorrentvpn/page/186/#findComment-1565276

Maybe I wasn't clear, that log was my feedback about that test image.

1 hour ago, binhex said:

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 ran the :test build and also got the same resolvconf: signature mismatch: /etc/resolv.conf error, followed by the Failed to bring 'up' WireGuard kernel implementation

Having the same problem as mentioned above

Failed to bring 'up' WireGuard kernel implementation

However do not see how or where to roll back?

2 hours ago, erfly7 said:

Having the same problem as mentioned above

Failed to bring 'up' WireGuard kernel implementation

However do not see how or where to roll back?

To roll back you need to manually specify a version. If nothing is specified it will use :latest. but you can figure out the older tags from the github page. To go to the github page you click on the docker container and selecting 'More Info'

So to rollback to the stable version before this bug. click on Qbittorrent and 'Edit'

Change the Repository to this binhex/arch-qbittorrentvpn:5.1.1-1-01

13 hours ago, erfly7 said:

Having the same problem as mentioned above

Failed to bring 'up' WireGuard kernel implementation

However do not see how or where to roll back?

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.

On 7/4/2025 at 6:36 AM, binhex said:

I have a test tagged image i would like you to try, PLEASE let me know the outcome,good or bad:

1. Go to unraid web ui/docker and left click the container and select 'edit'

2. Go to the 'Repository' line and append ':test' to te end

3. Scroll to the bottom and click 'Apply'

4. Wait a minute or so for the container to start, check logs and if it looks good check webui

5. Report back here.

I was having the "[warn] Failed to bring 'up' WireGuard kernel implementation" issue with :latest, I had to rollback to 5.1.1-1-01, tested with :test per above and it's working properly so far...

Thanks!

2 minutes ago, kaymer327 said:

I was having the "[warn] Failed to bring 'up' WireGuard kernel implementation" issue with :latest

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

1 hour ago, binhex said:

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

I just pulled latest, same issue:

2025-07-05 19:32:06,275 DEBG 'start-script' stdout output:
[info] Configuring WireGuard...
2025-07-05 19:32:06,285 DEBG 'start-script' stdout output:
[info] Attempting to bring WireGuard interface 'up'...
2025-07-05 19:32:06,292 DEBG 'start-script' stderr output:
Warning: `/config/wireguard/wg0.conf' is world accessible
2025-07-05 19:32:06,298 DEBG 'start-script' stderr output:
[#] ip link add dev wg0 type wireguard
2025-07-05 19:32:06,300 DEBG 'start-script' stderr output:
[#] wg setconf wg0 /dev/fd/63
2025-07-05 19:32:06,302 DEBG 'start-script' stderr output:
[#] ip -4 address add 10.2.0.2/32 dev wg0
2025-07-05 19:32:06,308 DEBG 'start-script' stderr output:
[#] ip link set mtu 1420 up dev wg0
2025-07-05 19:32:06,311 DEBG 'start-script' stderr output:
[#] resolvconf -a wg0 -m 0 -x
2025-07-05 19:32:06,318 DEBG 'start-script' stderr output:
could not detect a useable init system
2025-07-05 19:32:06,334 DEBG 'start-script' stderr output:
resolvconf: signature mismatch: /etc/resolv.conf
2025-07-05 19:32:06,335 DEBG 'start-script' stderr output:
resolvconf: run resolvconf -u to update
2025-07-05 19:32:06,343 DEBG 'start-script' stderr output:
[#] ip link delete dev wg0
2025-07-05 19:32:06,437 DEBG 'start-script' stdout output:
[warn] Failed to bring 'up' WireGuard kernel implementation

1 hour ago, Proddy said:

I just pulled latest, same issue:

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

5 hours ago, binhex said:

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.

Your change appears to have fixed the issue for me at least.

I was getting the Torguard Kernel problem everyone was previously describing.

6 hours ago, binhex said:

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.

still having same issue

2025-07-05 19:57:47,518 DEBG 'start-script' stdout output:

[warn] Failed to bring 'up' WireGuard kernel implementation

9 hours ago, Linguafoeda said:

still having same issue

2025-07-05 19:57:47,518 DEBG 'start-script' stdout output:

[warn] Failed to bring 'up' WireGuard kernel implementation

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.

23 hours ago, binhex said:

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

It might have been user error previously - I just changed back to :latest and Wireguard worked successfully, all is good

anyway to get attention to this bug that is neutering the app: https://github.com/binhex/arch-qbittorrentvpn/issues/298

22 hours ago, binhex said:

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.

Willing to help here, but how do I 'stop and delete the container (not the image)'? Is that just removing it from the container list in the Unraid Docker GUI and then adding the container back with the 'add container' button?

Edit: nevermind, got it. Working on the logs now.

Edited July 7, 20251 yr by thatsthefrickenlightning

7 minutes ago, thatsthefrickenlightning said:

Willing to help here, but how do I 'stop and delete the container (not the image)'? Is that just removing it from the container list in the Unraid Docker GUI and then adding the container back with the 'add container' button?

Edit: nevermind, got it. Working on the logs now.

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.

19 minutes ago, thatsthefrickenlightning said:

Willing to help here, but how do I 'stop and delete the container (not the image)'? Is that just removing it from the container list in the Unraid Docker GUI and then adding the container back with the 'add container' button?

Edit: nevermind, got it. Working on the logs now.

Files are in your DMs as I'm too rushed to ensure I redacted correctly @binhex . Am on :latest and am having the 'wireguard up' issue.

Hope that helps

10 minutes ago, thatsthefrickenlightning said:

Am on :latest

you aren't (you are running a cached old latest), please do as instructed above.