PureVPN not working on GL.iNet (GL-MT2500)- device

Technical Support for Routers
1

Hi, can someone please help on why I cannot set up Wireguard Server using PureVPN Config File. In the Wireguard Server it is showing The client is starting, please wait…“” Below are the logs I am getting. Can you also advise the device OS?

Thu Jul 6 10:17:17 2023 user.notice wireguard-debug: USER=root ifname=wgclient ACTION=REKEY-TIMEOUT SHLVL=1 HOME=/ HOTPLUG_TYPE=wireguard LOGNAME=root DEVICENAME= TERM=linux SUBSYSTEM=wireguard PATH=/usr/sbin:/usr/bin:/sbin:/bin PWD=/
Thu Jul 6 10:17:23 2023 user.notice wireguard-debug: USER=root ifname=wgclient ACTION=REKEY-TIMEOUT SHLVL=1 HOME=/ HOTPLUG_TYPE=wireguard LOGNAME=root DEVICENAME= TERM=linux SUBSYSTEM=wireguard PATH=/usr/sbin:/usr/bin:/sbin:/bin PWD=/

2

You should be loading the PureVPN config file into the WireGuard Client, not the WireGuard Server.

PureVPN is a VPN provider that hosts their own VPN servers (I used them previously). Their PureVPN config files are to be used by client devices in order to connect to their own VPN servers.

I do not work for and I am not directly associated with GL.iNet

3

Sorry, this was my mistake, a typo error. Actually, I have uploaded the file on the WireGuard client. The above issue is from the client and not the server.

4

Can you show the PureVPN config file (with private info redacted) and the complete portion of the system log from before you started the WireGuard client to after it has failed.?

5

This is fixed by the PureVPN support team. There was a problem with the config file.Thanks

6

Would you care to post the ‘fix’ in case someone in the future stumbles across this same thread?

7

In the below config, PureVPN support added /24 after the Address and changed the Endpoint server address to the IP address. In the command prompt using nslookup can find the IP address. When downloading the manual config from the PureVPN site, these addresses need to be changed,

[Interface]
PrivateKey=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx=
Address=172.18.16.89/24
DNS=138.199.38.50,138.199.38.XX
[Peer]
PublicKey=XXXXXXXXXXXXXXXXXXXXXXXXXXXX=
AllowedIPs=0.0.0.0/0
Endpoint=138.199.38.XX:51820
PersistentKeepalive=21

2 Likes
8

Ouch. So their conf files or their config generators aren’t up to date. How bothersome. It’s still not the strangest thing I’ve seen VPN providers do for WG conf, though.

I’m glad you got it sorted.

1 Like