qdm12 / gluetun-wiki

Home to the Markdown Wiki page for Gluetun
MIT License
263 stars 30 forks source link

Allow purevpn wireguard #21

Open lordbah opened 7 months ago

lordbah commented 7 months ago

I tried to configure for PureVPN WireGuard after downloading config info as per https://support.purevpn.com/en_US/linux/how-to-setup-wireguard-on-linux only to get the gluetun error message 2023-10-23T21:32:02-04:00 ERROR VPN settings: provider settings: VPN provider name is not valid for Wireguard: value is not one of the possible choices: purevpn must be one of airvpn, custom, ivpn, mullvad, nordvpn, surfshark or windscribe I then changed "purevpn" to "custom" and got the error 2023-10-23T21:36:25-04:00 ERROR VPN settings: provider settings: server selection: for VPN service provider custom: the country specified is not valid: one or more values is set but there is no possible value available which is likely true if searching in servers.json. It looks like they have at least one endpoint at sx051007-wg.pointtoserver.com:51820.

I read elsewhere (https://www.reddit.com/r/PureVPNcom/comments/zjwrar/wireguard_configuration_requires_regeneration/) that their key expires. If that's still true, this probably wouldn't be useful.

qdm12 commented 7 months ago

PureVPN isn't 'natively' supported by Wireguard. I see they recently added support for Wireguard which is great, how do you get the Wireguard config file? Let me know and I'll add it to the Wiki. Also let me know if their key do actually expire... 😢

For the custom provider, you can definitely use it and plug the file in as you did. As the error mentions the country specified is not valid: one or more values is set but there is no possible value available so clear SERVER_COUNTRIES and it should work.

W-Floyd commented 6 months ago

I am using PureVPN Wireguard with this container.

You must use a custom provider, download the Wireguard configuration file, and modify it to use a direct IP rather than a hostname (https://github.com/qdm12/gluetun/issues/1793 - seems that it is because we specify VPN_ENDPOINT_IP, see setup/providers/custom.md).


In case someone is lost, here's how to get the Wireguard config start to end. Either download or copy the config like so:

image image image image image image image

To go from a hostname to an IP, we have a few options, easiest is ping, but nslookup is also neat. So open/paste the config file (depending on which you did in step 7), and copy out the Endpoint field, use that to find the IP: image

nslookup: image

ping: image

Finally, replace the hostname (step 8) in the config file with the direct IP (step 9): image

I am unsure of how the 30-minute timeout operates, but you may need to regenerate a config if you stay disconnected for too long / don't connect within 30 minutes.

Sevyn13 commented 1 month ago

I am using PureVPN Wireguard with this container.

You must use a custom provider, download the Wireguard configuration file, and modify it to use a direct IP rather than a hostname (qdm12/gluetun#1793 - seems that it is because we specify VPN_ENDPOINT_IP, see setup/providers/custom.md).

In case someone is lost, here's how to get the Wireguard config start to end. Either download or copy the config like so:

image image image image image image image

To go from a hostname to an IP, we have a few options, easiest is ping, but nslookup is also neat. So open/paste the config file (depending on which you did in step 7), and copy out the Endpoint field, use that to find the IP: image

nslookup: image

ping: image

Finally, replace the hostname (step 8) in the config file with the direct IP (step 9): image

I am unsure of how the 30-minute timeout operates, but you may need to regenerate a config if you stay disconnected for too long / don't connect within 30 minutes.

Could you share your Docker Compose file? I followed what you said but still not working.

W-Floyd commented 1 month ago

@Sevyn13 unfortunately I no longer use PureVPN due to the consistently poor experience, so my docker configuration has changed. That being said, it wasn't anything unusual.

I now use Windscribe, which is natively supported. I have found them to be much more reliable (PureVPN would randomly drop) and performant (100mbps on PureVPN vs. saturating 1gbps on Windscribe). That's just my two cents though.