Can't connect to Wireguard Server

[dikilikid]

Hey there,

I am having a weird issue with my Wireguard Server/Client setup. My previous setup was just working fine but we moved to a different place aka different ISP provider etc. So I wanted to reset everything and re-build from scratch.

I followed the documentation when setting up the server as I did before.

Did the port forwarding on My Google Nest WiFi as below. (in my previous Wireguard server setup, I was using the router century link offered, now I am using the Google Nest Wifi I have)

I also enabled the Dynamic DNS on the server.

Before setting up the client though, I wanted to give it a try and test it on the app. I scanned QR code for the configuration of the server and added it to the app. It didn’t seem to work. Couldn’t get any internet access. I was on my LTE when trying to access my server.

Since I couldn’t get any logs from the mobile app, I decided to set up the wireguard client on my other Beryl router.

At first, I used this configuration below on the client

But I couldn’t get it to work, I was getting the error logs below

Sun Aug 13 11:24:42 2023 daemon.notice netifd: Interface 'wgclient' is setting up now
Sun Aug 13 11:26:27 2023 user.notice wireguard-debug: USER=root ifname=wgclient ACTION=REKEY-GIVEUP SHLVL=1 HOME=/ HOTPLUG_TYPE=wireguard LOGNAME=root DEVICENAME= TERM=linux SUBSYSTEM=wireguard PATH=/usr/sbin:/usr/bin:/sbin:/bin PWD=/
Sun Aug 13 11:26:30 2023 daemon.notice netifd: wgclient (25905): cat: can't open '/tmp/run/wg_resolved_ip': No such file or directory
Sun Aug 13 11:26:30 2023 daemon.notice netifd: Interface 'wgclient' is now down
Sun Aug 13 11:26:30 2023 daemon.notice netifd: Interface 'wgclient' is setting up now
Sun Aug 13 11:26:31 2023 user.notice mwan3[25936]: Execute ifdown event on interface wgclient (unknown)
Sun Aug 13 11:26:31 2023 user.notice firewall: Reloading firewall due to ifdown of wgclient ()
Sun Aug 13 11:28:04 2023 daemon.notice netifd: wgclient (30193): cat: can't open '/tmp/run/wg_resolved_ip': No such file or directory
Sun Aug 13 11:28:04 2023 daemon.notice netifd: Interface 'wgclient' is now down
Sun Aug 13 11:28:05 2023 user.notice mwan3[30295]: Execute ifdown event on interface wgclient (unknown)
Sun Aug 13 11:28:05 2023 user.notice firewall: Reloading firewall due to ifdown of wgclient ()

Then from what I gathered from the logs, 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. The same adjustment on the mobile app didn’t work though. Still can’t get any internet access even though I change endpoint address to my wireguard server’s IP address in the app.

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

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

Sun Aug 13 14:14:11 2023 daemon.notice netifd: Interface 'wgclient' is setting up now
Sun Aug 13 14:15:57 2023 user.notice wireguard-debug: USER=root ifname=wgclient ACTION=REKEY-GIVEUP SHLVL=1 HOME=/ HOTPLUG_TYPE=wireguard LOGNAME=root DEVICENAME= TERM=linux SUBSYSTEM=wireguard PATH=/usr/sbin:/usr/bin:/sbin:/bin PWD=/
Sun Aug 13 14:16:00 2023 daemon.notice netifd: wgclient (7463): RTNETLINK answers: No such process
Sun Aug 13 14:16:00 2023 daemon.notice netifd: Interface 'wgclient' is now down
Sun Aug 13 14:16:00 2023 daemon.notice netifd: Interface 'wgclient' is setting up now
Sun Aug 13 14:16:00 2023 user.notice mwan3[7494]: Execute ifdown event on interface wgclient (unknown)
Sun Aug 13 14:16:01 2023 user.notice firewall: Reloading firewall due to ifdown of wgclient ()
Sun Aug 13 14:16:21 2023 daemon.notice netifd: wgclient (8957): RTNETLINK answers: No such process
Sun Aug 13 14:16:21 2023 daemon.notice netifd: Interface 'wgclient' is now down
Sun Aug 13 14:16:22 2023 user.notice mwan3[9054]: Execute ifdown event on interface wgclient (unknown)
Sun Aug 13 14:16:22 2023 user.notice firewall: Reloading firewall due to ifdown of wgclient ()

At this point I am not sure what’s happening. Any help would be appreciated!

[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 …

[dikilikid]

Thanks for your response.

I didn’t use dig before but in case it helps you can find my wg show logs down below.

wgclient

wgserver