OVPN Wireguard as a custom provider issue #677

Magic-Deceiver · 2021-10-15T12:47:02Z

Magic-Deceiver
Oct 15, 2021

I have been using Gluetun for quite a while now and it has been proven to be extremely solid. Kudos to @qdm12!

However, recently I have started using OVPN as a VPN provider and for some reason, it simply won't work.

Below is my configuration for docker-compose, and the logs associated with it. Maybe someone more knowledgeable will be able to answer what I did wrong.

version: "3"
services:
  gluetun:
    image: qmcgaw/gluetun
    container_name: gluetun
    cap_add:
      - NET_ADMIN
    ports:
      - 8550:80/tcp
      - 9117:9117/tcp # Jackett WebUI
      - 8080:8080/tcp # qBitorrent WebUI
      - 6881:6881/tcp # qBitorrent tcp connection port
      - 6881:6881/udp # qBitorrent udp connection port
    volumes:
      - /my-path-to-config/gluetun:/gluetun
    environment:
      - VPNSP=custom
      - VPN_TYPE=wireguard
      - WIREGUARD_ENDPOINT_IP=152.89.162.27 # endpoint IP according to "https://www.nslookup.io/dns-records/vpn72.prd.zurich.ovpn.com"
      - WIREGUARD_ENDPOINT_PORT=9929 # this port is what I see on the wireguard configuration file
      - WIREGUARD_PUBLIC_KEY=DO9_____________________________= # this is the public key I generated on OVPN
      - WIREGUARD_PRIVATE_KEY=MNX_____________________________= # this is the private key
       # - WIREGUARD_PRESHARED_KEY= (Im actually not sure what to put this one and I see that this is not a mandatory env variable, so I deleted it, I have tried adding peer public key in there but it didn't work either)
      - WIREGUARD_ADDRESS=172.30.76.76/32 # this is the address assigned to me
    restart: always

The file I downloaded (modified) for the public key DO9_____________________________=

[Interface]
PrivateKey = MNX_____________________________
Address = 172.30.76.76/32, fd00:0:1337:cafe:1111:1111:ec98:9d42/128
DNS = 46.227.67.134, 192.165.9.158
 
[Peer]
PublicKey = lL+_____________________________=
AllowedIPs = 0.0.0.0/1, 128.0.0.0/1, ::/1, 8000::/1
Endpoint = vpn72.prd.zurich.ovpn.com:9929

And this is the logs, it basically repeats itself:

2021/10/15 12:36:20 INFO vpn: stopping
2021/10/15 12:36:20 INFO vpn: starting
2021/10/15 12:36:20 INFO firewall: setting VPN connection through firewall...
2021/10/15 12:36:20 INFO wireguard: Connecting to 152.89.162.27:9929
2021/10/15 12:36:20 INFO wireguard: Wireguard is up
2021/10/15 12:36:33 ERROR ip getter: Get "https://ipinfo.io/ip": dial tcp: lookup ipinfo.io on 1.1.1.1:53: read udp 172.30.76.76:41613->1.1.1.1:53: i/o timeout
2021/10/15 12:36:33 INFO ip getter: retrying in 5s
2021/10/15 12:36:38 INFO dns over tls: downloading DNS over TLS cryptographic files
2021/10/15 12:36:48 WARN dns over tls: cannot update files
2021/10/15 12:36:48 INFO dns over tls: attempting restart in 2m40s
2021/10/15 12:36:48 ERROR ip getter: Get "https://domains.google.com/checkip": dial tcp: lookup domains.google.com on 1.1.1.1:53: read udp 172.30.76.76:48809->1.1.1.1:53: i/o timeout
2021/10/15 12:36:48 INFO ip getter: retrying in 5s

I am not entirely sure what I did wrong, and I hope someone could help me get this working, because so far I really enjoyed OVPN (substantially faster speed than Mullvad in my experience, but I've heard the opposite on Reddit)

Thanks for tuning in, and I hope that maybe one day Quentin will be able to add OVPN as one of the providers!

Have a great rest of your day!

MD

Update:

Okay, my dumb brain put the public key wrong. Instead of this (public key from OVPN):

  - WIREGUARD_PUBLIC_KEY=DO9_____________________________=
  - WIREGUARD_PRIVATE_KEY=MNX_____________________________=

It should be this (public key from peer):

  - WIREGUARD_PUBLIC_KEY=lL+_____________________________=
  - WIREGUARD_PRIVATE_KEY=MNX_____________________________=

If anyone needs help, feel free to reach out! Would love to help out anyone who has trouble setting it up! (disclaimer: I am no expert in this, but I spent a substantial amount of time trying to make it work, lol)

qdm12 · 2021-10-15T14:53:46Z

qdm12
Oct 15, 2021
Maintainer

Nice you figured it out. Feel free to subscribe to issue #610 so that you could plug in the config file directly instead of via env variables.

Actually, I need to add native support for ovpn.com in #495 so here are a few quick questions for Wireguard:

Do each server config have the same interface address?
Do each server config have the same endpoint port?
Do they have IP addresses for their endpoint or only hostnames?
Is your interface private key the same for all server configs?
Do they have maybe an API to get all of their server information (such as IP address, Wireguard public key)?

Feel free to reply in #495 or here, up to you.

Thanks!!

2 replies

Magic-Deceiver Oct 15, 2021
Author

As far as I know, interface config remains the same
All peer endpoint ports are the same
they use the hostname in the form of VPN server#, servers city location (e.g. vpn71.prd.newyork.ovpn.com:9929) (prd remains the same for all)
If I download multiple configs using the same public key generated by OVPN, then all the interface private key remains the same
That I have no idea. The only option I have seen is to manual download

I hope this helps!

derekcentrico Nov 21, 2023

I'm happy to supply the wireguard config files and assist in any way to bake it in. The only issue as mentioned previously is the use of addresses and not IPs. I presume this helps swap out and prevent clients needing to reconfigure setups if an IP changes. Would be nice to keep that.

Zippzapp65 · 2023-09-04T15:07:12Z

Zippzapp65
Sep 4, 2023

I will try to use this because I really want to use OVPN on my server .

0 replies

Zippzapp65 · 2023-09-04T17:36:51Z

Zippzapp65
Sep 4, 2023

Yes i got it to work thanks for the guide :)

0 replies

derekcentrico · 2023-11-21T02:33:57Z

derekcentrico
Nov 21, 2023

I posted an issue that has the same io timeout. However I don't think I'm wrong with settings.

To confirm, ovpn config public key under peer is gluetun public key and interface private key is gluetun private key. Correct? Not following about your generated key because that should be the private key although it makes new ones unless you paste old ones in the config generator.

3 replies

AndreCox Dec 10, 2023

From my testing to get it to work simply follow these steps,

Go to your Ovpn Dashboard and click on Wireguard - Configuration files
For Add-On service select None
Select the country you want your vpn to go to
Press generate wireguard keys
Leave DNS on default
For endpoint select use IP address
Then press display config

From here you can see the public and private keys and paste them into your config file
You can also see the servers IP and port which you will need for the environment variables.

derekcentrico Dec 10, 2023

Sure, so I've been doing it that way. However, USA Chicago, USA New York, and Sweden Stockholm do not work. They work fine loaded into a Wireguard client that isn't this. Which server(s) have you confirmed function and I'll try those? Happy to toss you a coffee for assistance.

AndreCox Dec 13, 2023

I'll do some testing with those servers, but I have been using Canada Toronto with success, although I've had some issues where It breaks over a couple days.

AndreCox · 2023-12-13T19:31:48Z

AndreCox
Dec 13, 2023

One thing I noticed is that it works for a couple of days, and then stops working after I restart the container

3 replies

AndreCox Dec 13, 2023

After some more testing, by using the wireguard client on my PC the credentials still work so I assume that something is breaking in the container

AndreCox Dec 13, 2023

What's weirder is that it's working I can ping google.com, and using dig I find that my public IP is going through the VPN server. I'll keep you guys updated on whether I can solve it.

AndreCox Dec 13, 2023

And it randomly started working again after a couple restarts...

Zippzapp65 · 2023-12-14T09:29:23Z

Zippzapp65
Dec 14, 2023

Running OVPN on my synology with this yaml file in a docker container and works great connected to Stockholm.

environment:
- PUID=1031
- PGID=65537
- VPNSP=custom
- VPN_TYPE=wireguard
- WIREGUARD_ENDPOINT_IP=217.64.148.67 # endpoint IP according to "https://www.nslookup.io/dns-records/vpn61.prd.kista.ovpn.com"
- WIREGUARD_ENDPOINT_PORT=9929 # this port is what I see on the wireguard configuration file
- WIREGUARD_PUBLIC_KEY=xxx= # this is the public key I generated on OVPN
- WIREGUARD_PRIVATE_KEY=xxx= # this is the private key I generated on OVPN
- WIREGUARD_ADDRESS=172.16.75.112/32 # this is the address assigned to me
- TZ=Europe/Stockholm
- HTTPPROXY=off #change to on if you wish to enable
- SHADOWSOCKS=off #change to on if you wish to enable
- FIREWALL_OUTBOUND_SUBNETS=172.20.0.0/16,192.168.0.0/24 #change this in line with your subnet see note on guide.
- FIREWALL_VPN_INPUT_PORTS=57410 #uncomment this line and change the port as per the note on the guide

0 replies

derekcentrico · 2023-12-16T17:50:48Z

derekcentrico
Dec 16, 2023

Running OVPN on my synology with this yaml file in a docker container and works great connected to Stockholm.

I'm going to just give up I guess. I've tried your settings as well and I get that same i/o error. Configs work just fine using a wireguard client, but not with gluetun. I'm at a complete loss.

1 reply

Zippzapp65 Dec 16, 2023

I can recommend using this guide.
https://drfrankenstein.co.uk/

AndreCox · 2023-12-17T23:06:40Z

AndreCox
Dec 17, 2023

Everything Is working for me now, the major issue I'm having is that port forwarding breaks after a couple of days.

1 reply

AndreCox Dec 17, 2023

Gives this weird issue

2023-12-17T18:11:12Z INFO [healthcheck] healthy!
2023-12-17T18:12:27Z INFO [healthcheck] unhealthy: dialing: dial tcp4: lookup cloudflare.com: i/o timeout
2023-12-17T18:12:28Z INFO [healthcheck] healthy!
2023-12-17T18:14:19Z INFO [healthcheck] unhealthy: dialing: dial tcp4: lookup cloudflare.com: i/o timeout
2023-12-17T18:14:20Z INFO [healthcheck] healthy!
2023-12-17T18:19:06Z INFO [healthcheck] unhealthy: dialing: dial tcp4: lookup cloudflare.com: i/o timeout
2023-12-17T18:19:07Z INFO [healthcheck] healthy!
2023-12-17T18:24:49Z INFO [healthcheck] unhealthy: dialing: dial tcp4: lookup cloudflare.com: i/o timeout
2023-12-17T18:24:50Z INFO [healthcheck] healthy!
2023-12-17T18:57:58Z INFO [healthcheck] unhealthy: dialing: dial tcp4: lookup cloudflare.com: i/o timeout
2023-12-17T18:57:59Z INFO [healthcheck] healthy!
2023-12-17T20:10:34Z INFO [healthcheck] unhealthy: dialing: dial tcp4: lookup cloudflare.com: i/o timeout
2023-12-17T20:10:35Z INFO [healthcheck] healthy!
2023-12-17T20:31:59Z INFO [healthcheck] unhealthy: dialing: dial tcp4: lookup cloudflare.com: i/o timeout
2023-12-17T20:32:00Z INFO [healthcheck] healthy!
2023-12-17T21:15:40Z INFO [healthcheck] unhealthy: dialing: dial tcp4: lookup cloudflare.com: i/o timeout
2023-12-17T21:15:42Z INFO [healthcheck] healthy!
2023-12-17T22:12:09Z INFO [healthcheck] unhealthy: dialing: dial tcp4: lookup cloudflare.com: i/o timeout
2023-12-17T22:12:10Z INFO [healthcheck] healthy!
2023-12-17T23:02:44Z INFO [healthcheck] unhealthy: dialing: dial tcp4: lookup cloudflare.com: i/o timeout
2023-12-17T23:02:46Z INFO [healthcheck] healthy!
2023-12-17T23:07:41Z INFO [healthcheck] unhealthy: dialing: dial tcp4: lookup cloudflare.com: i/o timeout
2023-12-17T23:07:42Z INFO [healthcheck] healthy!
2023-12-17T23:08:26Z INFO [healthcheck] unhealthy: dialing: dial tcp4: lookup cloudflare.com: i/o timeout
2023-12-17T23:08:28Z INFO [healthcheck] healthy!

Container reports healthy though.

Zippzapp65 · 2023-12-29T07:52:23Z

Zippzapp65
Dec 29, 2023

Anyone figured out what this does?

WIREGUARD_PRESHARED_KEY=

2 replies

AndreCox Dec 29, 2023

Simply the preshaped key used by wireguard so that the encrypted tunnel can be created. You can find it in the wireguard config file

Zippzapp65 Dec 29, 2023

Ok there is no WIREGUARD_PRESHARED_KEY= when generating wireguard config file at OVPN.

[Interface]
PrivateKey = XXX=
Address = 172.25.112.101/32, fd00:0000:1337:cafe:1111:1111:0c36:a1e1/128
DNS = 46.227.67.134,192.165.9.158,2a07:a880:4601:10f0:cd45::1,2001:67c:750:1:cafe:cd45::1

[Peer]
PublicKey = XXX=
AllowedIPs = 0.0.0.0/0, ::/0
Endpoint = 217.64.148.50:9929

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

OVPN Wireguard as a custom provider issue #677

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 9 comments 12 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

OVPN Wireguard as a custom provider issue #677

Replies: 9 comments · 12 replies

qdm12 Oct 15, 2021 Maintainer

Magic-Deceiver Oct 15, 2021 Author

Replies: 9 comments 12 replies

qdm12
Oct 15, 2021
Maintainer

Magic-Deceiver Oct 15, 2021
Author