Hi There - I’m having an issue with my Wireguard VPN client not connecting to the Wireguard Server properly after the client is rebooted. Here’s what I have:
Router: HOME (Convexa-B1300) - this is located at my office
Wireguard VPN Server
Router: TRAVEL (Convexa-B1300) - this will travel with me when I travel
Wireguard VPN Client
Here’s the issue:
The TRAVEL router is connected on the WAN via WiFi (say a hotel or coffee shop). When it first boots up, it connects to the WAN over WifFi just fine. The Wireguard client FAILS to connect to the Wireguard server on HOME router. I have to go to the gui for the Wireguard client, hit ABORT then then hit CONNECT. Then works fine. Whenever the TRAVEL router is connected via WIFI and first boots or is rebooted it will fail until I hit ABORT and then hit CONNECT via the gui.
When the TRAVEL router is connected to the WAN via Ethernet, there is no problem. I do not have to abort the client on the TRAVEL router when it first boots or when it reboots.
I can replicate this 100% of the time and I need some help here figuring out what to do. Any help is appreciated.
Using the DDNS name of SOMETHING.glddns.com causes my wireguard client to fail. Using the dynamic IP from my ISP allows my wireguard client to connect. However, once the dynamic IP address changes then my wireguard client will no longer connect.
Yes, DDNS does resolve correctly to my ISP address. WireGuard VPN client will work with DDNS name in the following way: If I turn on the TRAVEL router the WireGuard client fails to connect. All I do is hit disconnect and then hit connect and it works. I created a WireGuard VPN client using IP address and it works every single time. The WireGuard client using DDNS name fails when the router boots and if I disconnect and reconnect it works.
I still have no solution to this problem. I am temporarily using IP address to connect from the remote router to the main office router. Any help is appreciated. Are there some logs I can post to help with this?