qdm12 / gluetun

VPN client in a thin Docker container for multiple VPN providers, written in Go, and using OpenVPN or Wireguard, DNS over TLS, with a few proxy servers built-in.
https://hub.docker.com/r/qmcgaw/gluetun
MIT License
7.68k stars 359 forks source link

Bug: [ip getter] and [vpn] cannot get version information, errors upon start up. #1945

Closed erphise closed 11 months ago

erphise commented 11 months ago

Is this urgent?

No

Host OS

Unraid OS

CPU arch

x86_64

VPN service provider

ProtonVPN

What are you using to run the container

docker-compose

What is the version of Gluetun

Running version latest built on 2023-11-01T13:43:23.095Z (commit 1adbd9f)

What's the problem 🤔

As stated on title, I am permanently getting both this errors every time I try to start the container. I have looked it up before posting this issue. Found issue #1553 . But besides being closed, didn't found any solution that worked for me. Tried setting DOT=off and didn't worked.

Share your logs (at least 10 lines)

2023-11-05T22:27:27+01:00 INFO [wireguard] Wireguard setup is complete. Note Wireguard is a silent protocol and it may or may not work, without giving any error message. Typically i/o timeout errors indicate the Wireguard connection is not working.
2023-11-05T22:27:31+01:00 INFO [healthcheck] healthy!
2023-11-05T22:27:38+01:00 ERROR [vpn] cannot get version information: Get "https://api.github.com/repos/qdm12/gluetun/commits": dial tcp: lookup api.github.com on 1.1.1.1:53: read udp 10.2.0.2:42700->1.1.1.1:53: i/o timeout
2023-11-05T22:27:38+01:00 ERROR [ip getter] Get "https://ipinfo.io/": dial tcp: lookup ipinfo.io on 1.1.1.1:53: read udp 10.2.0.2:53198->1.1.1.1:53: i/o timeout - retrying in 5s

Share your configuration

version: "3"
services:
  gluetun:
    image: qmcgaw/gluetun
    container_name: gluetun
    restart: always
    network_mode: bridge
    cap_add:
      - NET_ADMIN
    devices:
      - /dev/net/tun
    volumes:
      - ./gluetun:/gluetun
    environment:
      - TZ=Europe/Madrid
      - VPN_SERVICE_PROVIDER=custom
      - VPN_TYPE=wireguard
      - VPN_ENDPOINT_IP=<ip>
      - VPN_ENDPOINT_PORT=<port>
      - WIREGUARD_PUBLIC_KEY=<public_key>
      - WIREGUARD_PRIVATE_KEY=<private_key>
      - WIREGUARD_ADDRESSES=<addresses>
      - OPENVPN_USER=<user>+pmp
      - OPENVPN_PASSWORD=<password>
      - VPN_PORT_FORWARDING=on
      - VPN_PORT_FORWARDING_PROVIDER=protonvpn
ezekieldas commented 11 months ago

If you want a wireguard connection I recommend removing the OPENVPN_ and VPN_PORT_ settings.

Also see:

erphise commented 11 months ago

If you want a wireguard connection I recommend removing the OPENVPN_ and VPN_PORT_ settings.

Removing the OPENVPN_ settings worked! Thanks!

Not sure if it was the only thing necessary to solve my problem, as I also didn't forced to upgrade the container once I composed it up on unRAID. Nonetheless, thank you so much.