Wireguard Client on Slate AX not connecting

Hello, I am using the GL iNet Slate AX in combination with the GL iNet Flint 2. I have set up the Flint 2 based on the following tutorial: https://www.youtube.com/watch?v=hKqTycmp0Rk. However, my WireGuard Client does not seem to connect to the WireGuard server I have created on the Flint 2. Flint 2 is on firmware v4.6.2 & the AX Slate is on firmware v4.6.2 as well. My server is using DDNS which was enabled.

Here is my client configuration:

[Interface]
Address = 10.0.0.2/24
PrivateKey = *********
DNS = 64.6.64.6
MTU = 1420

[Peer]
AllowedIPs = 0.0.0.0/0, ::/0
Endpoint = ******.glddns.com:51820
PersistentKeepalive = 25
PublicKey = *******

I have tried setting up and checking the port forwarding as well and doesn't seem to work either. When I try to access the DNS host ******.glddns.com it does not connect using my mobile device. Would someone be able to assist.

Please read How to troubleshoot WireGuard for the most common troubleshooting steps.

Pls read @admon 's post.

The common problem is that:

  1. You don't have a public IP
  2. Your port forward is wrong

So pls post info about the above items.

1 Like

How do I check if I have a public IP? Here is my port forwarding set up on the Flint 2:

Go somewhere like ipecho.net and see if the same IP displayed there matches the IP you have on the WAN interface on your router. If not, you are likely behind CGNAT (from your provider) and direct wireguard won't work - you might consider tailscale instead. If it does match, then follow @admon advice for troubleshooting further.

Related to your picture - forwarding port 443 won't help. You need to change protocol to udp, and change port on external and internal to 51820. Again, @admon guide should help.

When you say to check if the same IP matches the IP I have on the WAN interface of my router, are you talking about the IP of my travel router, Flint 2 or ISP? The IP I have as the Internal IP on there is the one of my travel router (AX). Not sure if that is correct, I have updated the port to 51820 in the port forwarding configuration and still can't access the DNS domain.

The device that is acting as your wireguard server.