# HELP: Unable to connect to VPN client. Included logs **URL:** \ **Category:** VPN, DNS, Leaks\ **Created:** [November 13, 2023, 3:51pm UTC](https://forum.gl-inet.com/t/help-unable-to-connect-to-vpn-client-included-logs/35149 "2023-11-13T15:51:14Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![bring.fringe18](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/bring.fringe18/32/11777_2.png) [@bring.fringe18](https://forum.gl-inet.com/u/bring.fringe18)\ **Post date:** [November 13, 2023, 4:52pm UTC](https://forum.gl-inet.com/t/help-unable-to-connect-to-vpn-client-included-logs/35149/2 "2023-11-13T16:52:59Z")
Can you connect if you put the Slate AX as a Client to the Flint as WG Server locally? Flint (WG Server) LAN -\> Slate AX (WG Client) WAN. Update the Client settings ('endpoint') to reflect the Flint's LAN IPv4 (also an endpoint, normally 192.168.8.1). ... & don't forget to change the Slate AX to a different subnet like 192.168.18.1 (GL GUI -\> Network -\> LAN -\> Private Network -\> Router IP Address). `wg show` is a quick way to confirm connectivity if you can SSH. See below: > [@No TCP for connected VPN clients (just ICMP)](https://forum.gl-inet.com/t/no-tcp-for-connected-vpn-clients-just-icmp/30871/22): > > 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 … > [@HOW-TO: Script: List My OPKGs (to a file for backup)](https://forum.gl-inet.com/t/how-to-script-list-my-opkgs-to-a-file-for-backup/30963/3): > > References & Resources --- _[View the full topic](https://forum.gl-inet.com/t/help-unable-to-connect-to-vpn-client-included-logs/35149)._