Cannot set endpoint to localhost on windows

Alessandro Rinaldi ale at
Sun Aug 30 16:26:14 CEST 2020

I have the exact same problem and it's preventing me from using
engarde[0] with the official Wireguard client on Windows. I reported
that to the mailing list some time ago.
Thanks for pointing that out again :)


On Sat, Aug 29, 2020 at 11:08 PM Hirbod Behnam
<chrome.hiri.angry at> wrote:
> Hello
> I'm not sure if this is already reported or not but I found a small
> problem with the windows client of wireguard that does not allow users
> to use "plugins" on top of wireguard.
> So here is my case. I used gost to create a really simple port
> forwarder from my localhost to my server with this command: gost
> -L=udp:// (that forwards packets on port
> 12345 to and of course my server is not :D)
> Also here is my wireguard config:
> [Interface]
> PrivateKey = xxxx
> Address =
> DNS =
> [Peer]
> PublicKey = xxxx
> AllowedIPs =,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
> Endpoint =
> PersistentKeepalive = 25
> The allowed IPs are all ip addresses except
> When I run the client, the log fills with: [TUN] [xxx-wg0] peer(xxx) -
> Failed to send data packet write udp4>
> wsasendto: The requested address is not valid in its context.
> And I cannot connect to anything. Sometimes in gost, it says that a
> connection is established but I still cannot connect to anything
> though wireguard.
> Also it's good to know that the exact config works fine with TunSafe,
> the official Ubuntu client and openvpn. (I can connect through gost)
> Thanks for the project!
> Hirbod

More information about the WireGuard mailing list