Hi Raymundo,
Raymundo Soto Morales via Bug reports for GNU Guix <[email protected]>
writes:
> Did a recent update break wireguard? After doing a guix pull &&
> guix reconfigure, wireguard-wg0 cannot be started by herd.
> I am attaching both a snippet of my config and the error I get.
>
> Ray
>
> guix system: warning: exception caught while executing 'start' on service
> 'wireguard-wg0':
> Throw to key `%exception' with args `("#<&invoke-error program:
> \"/gnu/store/30gizwy43571x1nk3l7bxz8fp98iwd5a-wireguard-tools-1.0.20260223/bin/wg-quick\"
> arguments: (\"up\"
> \"/gnu/store/60sqapacz4pihmgmdr2b05ahmlp1w6p0-wireguard-config/wg0.conf\")
> exit-status: 1 term-signal: #f stop-signal: #f>")'.
> guix system: warning: some services could not be upgraded
> hint: To allow changes to all the system services to take effect, you will
> need to reboot.
If you use actual domain name rather than IP addresses in endpoints,
you'll need to wait for 'name resolution' to work. I think this is
likely a duplicate of https://codeberg.org/guix/guix/issues/838, which
includes a fix/workaround.
--
Thanks,
Maxim
