Can't connect to Wireguard Server

[bring.fringe18]

@dikilikid

I decided to manually switch the endpoint to my Beryl Wireguard Server’s IP address to see if that works at least. And it worked! I was able to establish the connection between my client and my server.

@dikilikid

After the tests, I decided to put my Dynamic DNS address back again in the configuration file my client.

Can you confirm you’re able to dig your DDNS & the correct Public Internet/WAN IP?

@dikilikid

And now I am getting a different error in the logs. Not related to the previous “wg_resolved_ip” error basically.

It might be related to a ‘kill switch’ via Global Options/Proxy but I’m just speculating.

Here’s a example of a ‘pure’ WG Server → WG Client using two GL devices all on the same subnet. If you can model based on that, it should just be a matter of then adding the GL DDNS string back into the confs:

No TCP for connected VPN clients (just ICMP)

Well there certainly was a hurdle to overcome: after enabling the VPN WG Server GL GUI’s defaults for generating WG Client confs automatically set the endpoint to the public IP. I wanted the WG Client device to connect to the WG Server directly within the LAN, not over the WAN/Internet, so of course I changed that to the WG Server’s IP 192.168.10.1 from the perspective of the Client device. My Client device, the Certa, is known to preform with VPN providers using a MTU of 1320. YMMV. Server …