Arch Linux

VallikDryan

Member

Registered: 2025-10-27

Posts: 2

[SOLVED] Wireguard setup as daemon. resolvconf: signature mismatch

I'm trying to setup a wireguard daemon  to connect to protonvpn. I moved the configuration files on the expected location, but when I reboot my computer, wireguard fails. This is the output of

$ journalctl -xeu wg-quick@proton 

Nov 18 21:11:24 vallik systemd[1]: Starting WireGuard via wg-quick(8) for proton...
░░ Subject: A start job for unit wg-quick@proton.service has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit wg-quick@proton.service has begun execution.
░░ 
░░ The job identifier is 142.
Nov 18 21:11:25 vallik wg-quick[726]: [#] ip link add dev proton type wireguard
Nov 18 21:11:25 vallik wg-quick[726]: [#] wg setconf proton /dev/fd/63
Nov 18 21:11:25 vallik wg-quick[726]: [#] ip -4 address add 10.2.0.2/32 dev proton
Nov 18 21:11:25 vallik wg-quick[726]: [#] ip link set mtu 1420 up dev proton
Nov 18 21:11:25 vallik wg-quick[807]: [#] resolvconf -a proton -m 0 -x
Nov 18 21:11:25 vallik wg-quick[850]: resolvconf: signature mismatch: /etc/resolv.conf
Nov 18 21:11:25 vallik wg-quick[850]: resolvconf: run `resolvconf -u` to update
Nov 18 21:11:25 vallik wg-quick[726]: [#] ip link delete dev proton
Nov 18 21:11:25 vallik systemd[1]: wg-quick@proton.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ An ExecStart= process belonging to unit wg-quick@proton.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
Nov 18 21:11:25 vallik systemd[1]: wg-quick@proton.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit wg-quick@proton.service has entered the 'failed' state with result 'exit-code'.
Nov 18 21:11:25 vallik systemd[1]: Failed to start WireGuard via wg-quick(8) for proton.
░░ Subject: A start job for unit wg-quick@proton.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit wg-quick@proton.service has finished with a failure.
░░ 
░░ The job identifier is 142 and the job result is failed.

The daemon can restart properly after I run

 # resolvconf -u 

. However, I'm not sure how safe is updating all suscribers every reboot. If it is safe, how would I go about that? Is there a better solution to this?

Last edited by VallikDryan (2025-11-22 03:19:15)

-thc

Member

Registered: 2017-03-15

Posts: 1,066

Re: [SOLVED] Wireguard setup as daemon. resolvconf: signature mismatch

The most common cause for this is the network management tampering with "/etc/resolv.conf" without "resolvconf".

Since "wg-quick" exclusively uses "resolvconf" you have to tell your network manager to use that too.

NetworkManager needs a hint:

# /etc/NetworkManager/conf.d/rc-manager.conf

[main]
rc-manager=resolvconf

systemd-resolved needs it's own version of it:

sudo pacman -S systemd-resolvconf

Last edited by -thc (2025-11-19 08:38:44)

VallikDryan

Member

Registered: 2025-10-27

Posts: 2

Re: [SOLVED] Wireguard setup as daemon. resolvconf: signature mismatch

Works like a charm!

To future readers: systemd-resolve is a daemon. Enabling it solved me the issue "Failed to set DNS configuration: Could not activate remote peer: 'org.freedesktop.resolv1': activation request failed: unknown unit".

If while debugging you get locked out of the internet, just comment the lines written on rc-manager and restart your NetworkManager.service