WireGuard hosed if click install tunnel without installing server conf first

[rnveach]

I recreated my issue from earlier. I had a working install of WireGuard, client and server, but after playing around with some things it stopped working correctly. I tried searching first but did not find anything.

Originally I followed the order on WS4W installing WireGuard, then creating server and then client configurations. I installed the conf file in WireGuard manually then continued on in WS4W doing Tunnel, private network, and NAT. Everything was green and the client was connecting and working just fine.

I then disconnected everything in WireGuard and deleted the server configuration in it only. The original conf file still exists. I re-opened WS4W and without changing anything else, installed the tunnel service once again thinking this would restore my original server Wireguard. Everything was green again in WS4W but WireGuard did not show the server in the list. The log file on Wireguard seemed to say the server was running from my conf but I was not getting a handshake on the client anymore.

The server log shows a spam of the following:

2024-12-26 02:45:06.108238: [TUN] [wg_server] Receiving handshake initiation from peer 1 (10.0.2.2:1159)
2024-12-26 02:45:06.108238: [TUN] [wg_server] Sending handshake response to peer 1 (10.0.2.2:1159)
2024-12-26 02:45:06.108238: [TUN] [wg_server] Keypair 76 destroyed for peer 1
2024-12-26 02:45:06.108238: [TUN] [wg_server] Keypair 77 created for peer 1

The client logs just says "Sending handshake" and "Handshake did not complete". Nothing else.

I tried closing WireGuard and re-opening it, but it didn't change. I tried re-installing the server conf in the WireGuard manually and the client can still not connect. It seems like something gets corrupted if you install the tunnel in WS4W first before manually installing the conf in Wireguard, but I haven't tried this on a fresh install.

I didn't change any network configurations, or the client between working and broken. I didn't try creating a different named server/client conf. I tried copying/pasting the conf to a new file and manually importing it, but it did not work still. The server is on a VM but it shouldn't matter since it was working originally.

WireGuard app version: 0.5.3 Driver version: 0.10.1 OS: Windows 10.0.19045 Architecture: amd64