Windows: netclient causes high CPU usage on wireguard: "Unable to ingest and encrypt"

[janost]

Netclient causes the wireguard manager process to spam errors in its log and constantly hammer the CPU. I was able reproduce the issue on 2 separate Windows 10 computers. The issue seems to happen randomly, sometimes it doesn't happen for several hours, sometimes it happens instantly after the computer boots up. Netclient version: v0.9.2

[QZAiXH]

I encountered the same situation as you, did you solve it?

[janost]

No, I did not. There was a wireguard app update about 2 days ago to version 0.5.3 and I believe I haven't encountered the issue since, but I'm not 100% sure.

[Bpazy]

I have the same situation with Wireguard version 0.5.3. In my test, I found that occurred when netclient retrieves new configuration and triggers wireguard reconnecting.

But this problem will never occur when I close the wireguard GUI.

[cx9208]

same problem, and windows node cant set ingress or egress

[afeiszli]

Adding to triage. As a workaround for users, as @Bpazy is mentioning, keeping the WireGuard GUI closed should resolve the problem

[QZAiXH]

Close the GUI, the configuration will not be updated

[janost]

Yeah, closing the GUI is not really a proper workaround, because without it netclient will not be able to reconfigure the tunnel, which kind of defeats the purpose of netmaker.

I haven't tested with 0.10.0 yet.

[Blaiselux]

Just tested with 0.10.0, still [MGR] Unable to ingest and encrypt the .conf file

[afeiszli]

The Windows agent has been re-factored as of 0.11 and no longer integrates with the WireGuard app. Users should no longer experience this issue.