Can anyone help setting up gluetun docker container? reddit / selfhosted ---------------------------------------------------------------------- fabiustus · 2023-11-07 09:14 Hi, I'm only asking here because I found another thread here where sb else got help with gluetun docker container, so I supposed it's not off topic. ​ I run Debian on a htpc with a ryzen apu. Docker with several containers is running, set up with dockstarter.com. The gluetun container is unhealthy and idk how to solve it. This is the docker compose override file (dockstarter has gluetun included, additional options are set by using a docker compose override file): `gluetun:` `cap_add:` `- NET_ADMIN` `environment:` `- VPN_SERVICE_PROVIDER=custom` `- VPN_TYPE=wireguard` `- VPN_ENDPOINT_IP=`[`185.189.115.103`](https://185.189.115.103) `- VPN_ENDPOINT_PORT=1443` `- WIREGUARD_PUBLIC_KEY=**********************` `- WIREGUARD_PRIVATE_KEY=************************` `- WIREGUARD_ADDRESSES=`[`192.168.1.111/32`](https://192.168.1.111/32) My vpn provider is torguard. I get the following output in portainer log: `2023-11-07T10:10:42+01:00 INFO [routing] default route found: interface eth0, gateway` [`172.18.0.1`](https://172.18.0.1)`, assigned IP` [`172.18.0.22`](https://172.18.0.22) `and family v4` `2023-11-07T10:10:42+01:00 INFO [routing] adding route for` [`0.0.0.0/0`](https://0.0.0.0/0) `2023-11-07T10:10:42+01:00 INFO [firewall] setting allowed subnets...` `2023-11-07T10:10:42+01:00 INFO [routing] default route found: interface eth0, gateway` [`172.18.0.1`](https://172.18.0.1)`, assigned IP` [`172.18.0.22`](https://172.18.0.22) `and family v4` `2023-11-07T10:10:42+01:00 INFO TUN device is not available: open /dev/net/tun: no such file or directory; creating it...` `2023-11-07T10:10:42+01:00 INFO [dns] using plaintext DNS at address` [`1.1.1.1`](https://1.1.1.1) `2023-11-07T10:10:42+01:00 INFO [http server] http server listening on [::]:8000` `2023-11-07T10:10:42+01:00 INFO [firewall] allowing VPN connection...` `2023-11-07T10:10:42+01:00 INFO [healthcheck] listening on` [`127.0.0.1:9999`](https://127.0.0.1:9999) `2023-11-07T10:10:42+01:00 INFO [wireguard] Using available kernelspace implementation` `2023-11-07T10:10:42+01:00 INFO [wireguard] Connecting to` [`185.189.115.103:1443`](https://185.189.115.103:1443) `2023-11-07T10:10:42+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-07T10:10:42+01:00 INFO [dns] downloading DNS over TLS cryptographic files` `2023-11-07T10:10:50+01:00 INFO [healthcheck] program has been unhealthy for 6s: restarting VPN (see` [`https://github.com/qdm12/gluetun- wiki/blob/main/faq/healthcheck.md`](https://github.com/qdm12/gluetun- wiki/blob/main/faq/healthcheck.md)`)` `2023-11-07T10:10:50+01:00 INFO [vpn] stopping` `2023-11-07T10:10:50+01:00 ERROR [vpn] cannot get version information: Get "`[`https://api.github.com/repos/qdm12/gluetun/commits`](https://a pi.github.com/repos/qdm12/gluetun/commits)`": context canceled` `2023-11-07T10:10:50+01:00 ERROR [ip getter] Get "`[`https://ipinfo.io/`](https://ipinfo.io/)`": dial tcp: lookup` [`ipinfo.io`](https://ipinfo.io) `on` [`1.1.1.1:53`](https://1.1.1.1:53)`: write udp 172.18.0.22:41311->`[`1.1.1.1:53`](https://1.1.1.1:53)`: write: operation not permitted - retrying in 5s` `2023-11-07T10:10:50+01:00 INFO [vpn] starting` `2023-11-07T10:10:50+01:00 INFO [firewall] allowing VPN connection...` `2023-11-07T10:10:50+01:00 INFO [wireguard] Using available kernelspace implementation` `2023-11-07T10:10:50+01:00 INFO [wireguard] Connecting to` [`185.189.115.103:1443`](https://185.189.115.103:1443) `2023-11-07T10:10:50+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-07T10:10:57+01:00 WARN [dns] cannot update files: Get "`[`htt ps://www.internic.net/domain/named.root`](https://www.internic.net/dom ain/named.root)`": context deadline exceeded (Client.Timeout exceeded while awaiting headers)` `2023-11-07T10:10:57+01:00 INFO [dns] attempting restart in 10s` `2023-11-07T10:11:01+01:00 INFO [healthcheck] program has been unhealthy for 11s: restarting VPN (see` [`https://github.com/qdm12/gluetun- wiki/blob/main/faq/healthcheck.md`](https://github.com/qdm12/gluetun- wiki/blob/main/faq/healthcheck.md)`)` `2023-11-07T10:11:01+01:00 INFO [vpn] stopping` `2023-11-07T10:11:02+01:00 INFO [vpn] starting` `2023-11-07T10:11:02+01:00 INFO [firewall] allowing VPN connection...` `2023-11-07T10:11:02+01:00 INFO [wireguard] Using available kernelspace implementation` `2023-11-07T10:11:02+01:00 INFO [wireguard] Connecting to` [`185.189.115.103:1443`](https://185.189.115.103:1443) `2023-11-07T10:11:02+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-07T10:11:07+01:00 INFO [dns] downloading DNS over TLS cryptographic files` `2023-11-07T10:11:10+01:00 ERROR [ip getter] Get "`[`https://ipinfo.io/`](https://ipinfo.io/)`": context deadline exceeded (Client.Timeout exceeded while awaiting headers) - retrying in 10s` `2023-11-07T10:11:18+01:00 INFO [healthcheck] program has been unhealthy for 16s: restarting VPN (see` [`https://github.com/qdm12/gluetun- wiki/blob/main/faq/healthcheck.md`](https://github.com/qdm12/gluetun- wiki/blob/main/faq/healthcheck.md)`)` `2023-11-07T10:11:18+01:00 INFO [vpn] stopping` `2023-11-07T10:11:18+01:00 INFO [vpn] starting` `2023-11-07T10:11:18+01:00 INFO [firewall] allowing VPN connection...` `2023-11-07T10:11:18+01:00 INFO [wireguard] Using available kernelspace implementation` `2023-11-07T10:11:18+01:00 INFO [wireguard] Connecting to` [`185.189.115.103:1443`](https://185.189.115.103:1443) `2023-11-07T10:11:18+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-07T10:11:22+01:00 WARN [dns] cannot update files: Get "`[`htt ps://www.internic.net/domain/named.root`](https://www.internic.net/dom ain/named.root)`": context deadline exceeded (Client.Timeout exceeded while awaiting headers)` `2023-11-07T10:11:22+01:00 INFO [dns] attempting restart in 20s` `2023-11-07T10:11:35+01:00 ERROR [ip getter] Get "`[`https://ipinfo.io/`](https://ipinfo.io/)`": context deadline exceeded (Client.Timeout exceeded while awaiting headers) - retrying in 20s` `2023-11-07T10:11:41+01:00 INFO [healthcheck] program has been unhealthy for 21s: restarting VPN (see` [`https://github.com/qdm12/gluetun- wiki/blob/main/faq/healthcheck.md`](https://github.com/qdm12/gluetun- wiki/blob/main/faq/healthcheck.md)`)` `2023-11-07T10:11:41+01:00 INFO [vpn] stopping` `2023-11-07T10:11:41+01:00 INFO [vpn] starting` `2023-11-07T10:11:41+01:00 INFO [firewall] allowing VPN connection...` `2023-11-07T10:11:41+01:00 INFO [wireguard] Using available kernelspace implementation` `2023-11-07T10:11:41+01:00 INFO [wireguard] Connecting to` [`185.189.115.103:1443`](https://185.189.115.103:1443) `2023-11-07T10:11:41+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-07T10:11:42+01:00 INFO [dns] downloading DNS over TLS cryptographic files` `2023-11-07T10:11:57+01:00 WARN [dns] cannot update files: Get "`[`htt ps://www.internic.net/domain/named.root`](https://www.internic.net/dom ain/named.root)`": context deadline exceeded (Client.Timeout exceeded while awaiting headers)` `2023-11-07T10:11:57+01:00 INFO [dns] attempting restart in 40s` `2023-11-07T10:12:08+01:00 INFO [healthcheck] program has been unhealthy for 26s: restarting VPN (see` [`https://github.com/qdm12/gluetun- wiki/blob/main/faq/healthcheck.md`](https://github.com/qdm12/gluetun- wiki/blob/main/faq/healthcheck.md)`)` `2023-11-07T10:12:08+01:00 INFO [vpn] stopping` `2023-11-07T10:12:09+01:00 INFO [vpn] starting` `2023-11-07T10:12:09+01:00 INFO [firewall] allowing VPN connection...` `2023-11-07T10:12:09+01:00 INFO [wireguard] Using available kernelspace implementation` `2023-11-07T10:12:09+01:00 INFO [wireguard] Connecting to` [`185.189.115.103:1443`](https://185.189.115.103:1443) `2023-11-07T10:12:09+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-07T10:12:10+01:00 ERROR [ip getter] Get "`[`https://ipinfo.io/`](https://ipinfo.io/)`": context deadline exceeded (Client.Timeout exceeded while awaiting headers) - retrying in 40s` `2023-11-07T10:12:37+01:00 INFO [dns] downloading DNS over TLS cryptographic files` `2023-11-07T10:12:40+01:00 INFO [healthcheck] program has been unhealthy for 31s: restarting VPN (see` [`https://github.com/qdm12/gluetun- wiki/blob/main/faq/healthcheck.md`](https://github.com/qdm12/gluetun- wiki/blob/main/faq/healthcheck.md)`)` `2023-11-07T10:12:40+01:00 INFO [vpn] stopping` `2023-11-07T10:12:40+01:00 INFO [vpn] starting` `2023-11-07T10:12:40+01:00 INFO [firewall] allowing VPN connection...` `2023-11-07T10:12:40+01:00 INFO [wireguard] Using available kernelspace implementation` `2023-11-07T10:12:40+01:00 INFO [wireguard] Connecting to` [`185.189.115.103:1443`](https://185.189.115.103:1443) `2023-11-07T10:12:40+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.` One thing I tried is to set network mode for another container to container:gluetun and map its port in the gluetun compose section. After that I'm able to reach the container, so I guess something must have worked :) I suspect there's some routing problem, but concerning this I'm a real noob. On the host os, debian, I have firewalld running. There's a gui for that and I put all interfaces into zone public. I further allowed wireguard service and in the ports section I added port 1443 both tcp and udp. Is it possible that there's also some firewall settings on my router that prevent gluetun to work properly? ---------------------------------------------------------------------- trexxeon · 2023-11-07 10:53 Try adding this to your compose: ‘’’ healthcheck: test: ["CMD", "curl", "-f", "cloudflare.com:443"] interval: 1m30s timeout: 10s retries: 3 start_period: 40s ‘’’ And see if it works ---------------------------------------------------------------------- fabiustus · 2023-11-07 14:18 Unfortunately no :( Only thing that changed is that now the container has the status "starting" in portainer instead of "unhealthy". Here's the log again, maybe you have other ideas: | ├── 192.168.0.0/16 | ├── 169.254.0.0/16 | ├── ::1/128 | ├── fc00::/7 | ├── fe80::/10 | ├── ::ffff:127.0.0.1/104 | ├── ::ffff:10.0.0.0/104 | ├── ::ffff:169.254.0.0/112 | ├── ::ffff:172.16.0.0/108 | └── ::ffff:192.168.0.0/112 ├── Firewall settings: | └── Enabled: yes ├── Log settings: | └── Log level: INFO ├── Health settings: | ├── Server listening address: 127.0.0.1:9999 | ├── Target address: cloudflare.com:443 | ├── Duration to wait after success: 5s | ├── Read header timeout: 100ms | ├── Read timeout: 500ms | └── VPN wait durations: | ├── Initial duration: 6s | └── Additional duration: 5s ├── Shadowsocks server settings: | └── Enabled: no ├── HTTP proxy settings: | └── Enabled: no ├── Control server settings: | ├── Listening address: :8000 | └── Logging: yes ├── OS Alpine settings: | ├── Process UID: 1000 | ├── Process GID: 1000 | └── Timezone: europe/vienna ├── Public IP settings: | ├── Fetching: every 12h0m0s | └── IP file path: /tmp/gluetun/ip └── Version settings: └── Enabled: yes 2023-11-07T12:52:58+01:00 INFO [routing] default route found: interface eth0, gateway 172.18.0.1, assigned IP 172.18.0.22 and family v4 2023-11-07T12:52:58+01:00 INFO [routing] adding route for 0.0.0.0/0 2023-11-07T12:52:58+01:00 INFO [firewall] setting allowed subnets... 2023-11-07T12:52:58+01:00 INFO [routing] default route found: interface eth0, gateway 172.18.0.1, assigned IP 172.18.0.22 and family v4 2023-11-07T12:52:58+01:00 INFO TUN device is not available: open /dev/net/tun: no such file or directory; creating it... 2023-11-07T12:52:58+01:00 INFO [dns] using plaintext DNS at address 1.1.1.1 2023-11-07T12:52:58+01:00 INFO [http server] http server listening on [::]:8000 2023-11-07T12:52:58+01:00 INFO [firewall] allowing VPN connection... 2023-11-07T12:52:58+01:00 INFO [healthcheck] listening on 127.0.0.1:9999 2023-11-07T12:52:58+01:00 INFO [wireguard] Using available kernelspace implementation 2023-11-07T12:52:58+01:00 INFO [wireguard] Connecting to 185.189.115.103:1443 2023-11-07T12:52:58+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-07T12:52:59+01:00 INFO [dns] downloading DNS over TLS cryptographic files 2023-11-07T12:53:06+01:00 INFO [healthcheck] program has been unhealthy for 6s: restarting VPN (see https://github.com/qdm12/gluetun-wiki/blob/main/faq/healthcheck.md) 2023-11-07T12:53:06+01:00 INFO [vpn] stopping 2023-11-07T12:53:06+01:00 ERROR [vpn] cannot get version information: Get "https://api.github.com/repos/qdm12/gluetun/commits": context canceled 2023-11-07T12:53:06+01:00 ERROR [ip getter] Get "https://ipinfo.io/": dial tcp: lookup ipinfo.io on 1.1.1.1:53: write udp 172.18.0.22:43169->1.1.1.1:53: write: operation not permitted - retrying in 5s 2023-11-07T12:53:07+01:00 INFO [vpn] starting 2023-11-07T12:53:07+01:00 INFO [firewall] allowing VPN connection... 2023-11-07T12:53:07+01:00 INFO [wireguard] Using available kernelspace implementation 2023-11-07T12:53:07+01:00 INFO [wireguard] Connecting to 185.189.115.103:1443 2023-11-07T12:53:07+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-07T12:53:14+01:00 WARN [dns] cannot update files: Get "https://www.internic.net/domain/named.root": context deadline exceeded (Client.Timeout exceeded while awaiting headers) 2023-11-07T12:53:14+01:00 INFO [dns] attempting restart in 10s 2023-11-07T12:53:18+01:00 INFO [healthcheck] program has been unhealthy for 11s: restarting VPN (see https://github.com/qdm12/gluetun-wiki/blob/main/faq/healthcheck.md) 2023-11-07T12:53:18+01:00 INFO [vpn] stopping 2023-11-07T12:53:18+01:00 INFO [vpn] starting 2023-11-07T12:53:18+01:00 INFO [firewall] allowing VPN connection... 2023-11-07T12:53:18+01:00 INFO [wireguard] Using available kernelspace implementation 2023-11-07T12:53:18+01:00 INFO [wireguard] Connecting to 185.189.115.103:1443 2023-11-07T12:53:18+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-07T12:53:24+01:00 INFO [dns] downloading DNS over TLS cryptographic files 2023-11-07T12:53:26+01:00 ERROR [ip getter] Get "https://ipinfo.io/": ---------------------------------------------------------------------- fabiustus · 2023-11-07 14:21 Wow, what's going on with reddit? Seems I cannot answer to the comment here ---------------------------------------------------------------------- fabiustus · 2023-11-07 14:24 Unfortunately no :( Only thing that changed is that now the container has the status "starting" in portainer instead of "unhealthy". Here's the log again, maybe you have other ideas: https://pastebin.com/vVEv12Tg ---------------------------------------------------------------------- trexxeon · 2023-11-07 19:35 Ah okay, skip that healthcheck and try adding this: - HEALTH_VPN_DURATION_INITIAL=120s as an env variable. ---------------------------------------------------------------------- kirblarzkb · 2023-11-08 02:06 I assume you’re trying to run for an arrsuite? If so, I’ll post a pastebin of the config I use when I got home. Took some trial and error to get it working properly. ---------------------------------------------------------------------- kirblarzkb · 2023-11-08 02:25 Here's a sample config i use. [https://pastebin.com/1TVqb29Q](https://pastebin.com/1TVqb29Q) For Gluetun service, ensure your volume is mapped to where you have the volume for it located. my example shows /var/dockerd/gluetun. I used Transmission, but the second half (Transmission: line down) you can swap out for whatever downloader you want. Just make sure to keep the "network\_mode: "service:gluetun" " line in there. ---------------------------------------------------------------------- fabiustus · 2023-11-08 07:54 This just makes the health check timeout longer? I think the issue might be somewhere else, it doesn't help either: `2023-11-08T08:51:51+01:00 INFO [routing] default route found: interface eth0, gateway 172.18.0.1, assigned IP 172.18.0.22 and family v4` `2023-11-08T08:51:51+01:00 INFO [routing] adding route for 0.0.0.0/0` `2023-11-08T08:51:51+01:00 INFO [firewall] setting allowed subnets...` `2023-11-08T08:51:51+01:00 INFO TUN device is not available: open /dev/net/tun: no such file or directory; creating it...` `2023-11-08T08:51:51+01:00 INFO [dns] using plaintext DNS at address 1.1.1.1` `2023-11-08T08:51:51+01:00 INFO [http server] http server listening on [::]:8000` `2023-11-08T08:51:51+01:00 INFO [wireguard] Connecting to 185.189.115.103:1443` `2023-11-08T08:51:51+01:00 INFO [firewall] allowing VPN connection...` `2023-11-08T08:51:51+01:00 INFO [healthcheck] listening on 127.0.0.1:9999` `2023-11-08T08:51:51+01:00 INFO [wireguard] Using available kernelspace implementation` `2023-11-08T08:51:51+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-08T08:52:07+01:00 WARN [dns] cannot update files: Get "https://www.internic.net/domain/named.root": context deadline exceeded (Client.Timeout exceeded while awaiting headers)` `2023-11-08T08:51:52+01:00 INFO [dns] downloading DNS over TLS cryptographic files` `2023-11-08T08:52:07+01:00 INFO [dns] attempting restart in 10s` `2023-11-08T08:52:17+01:00 INFO [dns] downloading DNS over TLS cryptographic files` `2023-11-08T08:52:22+01:00 ERROR [ip getter] Get "https://ipinfo.io/": context deadline exceeded (Client.Timeout exceeded while awaiting headers) - retrying in 5s` `2023-11-08T08:52:22+01:00 ERROR [vpn] cannot get version information: Get "https://api.github.com/repos/qdm12/gluetun/commits": context deadline exceeded (Client.Timeout exceeded while awaiting headers)` `2023-11-08T08:52:32+01:00 WARN [dns] cannot update files: Get "https://www.internic.net/domain/named.root": context deadline exceeded (Client.Timeout exceeded while awaiting headers)` `2023-11-08T08:52:32+01:00 INFO [dns] attempting restart in 20s` `2023-11-08T08:52:42+01:00 ERROR [ip getter] Get "https://ipinfo.io/": context deadline exceeded (Client.Timeout exceeded while awaiting headers) - retrying in 10s` `2023-11-08T08:52:52+01:00 INFO [dns] downloading DNS over TLS cryptographic files` `2023-11-08T08:53:07+01:00 WARN [dns] cannot update files: Get "https://www.internic.net/domain/named.root": context deadline exceeded (Client.Timeout exceeded while awaiting headers)` `2023-11-08T08:53:07+01:00 INFO [dns] attempting restart in 40s` `2023-11-08T08:53:07+01:00 ERROR [ip getter] Get "https://ipinfo.io/": context deadline exceeded (Client.Timeout exceeded while awaiting headers) - retrying in 20s` `2023-11-08T08:53:42+01:00 ERROR [ip getter] Get "https://ipinfo.io/": context deadline exceeded (Client.Timeout exceeded while awaiting headers) - retrying in 40s` ---------------------------------------------------------------------- fabiustus · 2023-11-08 07:55 Yeah, amongst other containers ---------------------------------------------------------------------- fabiustus · 2023-11-08 08:22 With dockstarter there are env variables set, one of them is \_NETWORK\_MODE and according to the app setup this needs to be changed to "container:gluetun". [https://dockstarter.com/apps/gluetun/#installsetup](https://dockstart er.com/apps/gluetun/#installsetup) After doing that and mapping a port of a testcontainer I can reach the testcontainer under the mapped port in my lan so I suppose sth. worked. ---------------------------------------------------------------------- fabiustus · 2023-11-08 08:25 Only difference I could spot is that I don't have the tun device mapped but if I'm right that's not necessary when using wireguard, it's only needed for openvpn. ---------------------------------------------------------------------- trexxeon · 2023-11-08 09:59 Yeah, I had trouble getting torguard to work with gluetun 3 days ago, and setting the healthcheck timeout longer made it actually connect to the vpn. I tried like 5 different locations and spent hours trying to figure out what was wrong. ---------------------------------------------------------------------- fabiustus · 2023-11-08 10:26 Hmm.. good try but seems that didn't work for me. ---------------------------------------------------------------------- trexxeon · 2023-11-08 10:31 Was the config you posted your whole config for gluetun? ---------------------------------------------------------------------- fabiustus · 2023-11-08 10:34 It's the part from the compose override file yeah. ---------------------------------------------------------------------- trexxeon · 2023-11-08 10:41 this is my whole config for torguard gluetun, and it works (for me): version: "3" services: gluetun: image: qmcgaw/gluetun:latest container_name: gluetun cap_add: - NET_ADMIN environment: - VPN_SERVICE_PROVIDER=custom - VPN_TYPE=wireguard - VPN_ENDPOINT_IP=45.12.211.12 - VPN_ENDPOINT_PORT=1443 - WIREGUARD_PUBLIC_KEY=pryh45R5rKiWYihaCMOArDPx6pSgn+plLC0SlmWG8SE= - WIREGUARD_PRIVATE_KEY=iaSSgDWf/X+9I12zkHxMTx2DcazVmNdZ8BQiVTRK0L4= - WIREGUARD_ADDRESSES=10.13.23.42/24 - DNS_ADDRESS=10.8.0.1 # if you port forward, change this to that port number #- FIREWALL_VPN_INPUT_PORTS=6881 - WIREGUARD_MTU=1390 - HEALTH_VPN_DURATION_INITIAL=120s - TZ=Europe/Stockholm # if you need to open ports #ports: # - 8686:8686 # lidarr ---------------------------------------------------------------------- fabiustus · 2023-11-08 11:09 Thx. WIREGUARD\_ADDRESSES specifies the IP Adress of the device that gluetun container runs on right? I see you ended it with /24 so in your case it's a range of IP addresses which made me curious. ​ But I now tried with my lan network as ip range and added the mtu and dns variables, still getting same errors. ---------------------------------------------------------------------- trexxeon · 2023-11-08 11:13 No, wireguard addresses is the internal address that it gets from the wireguard vpn, you should find it in the config you downloaded from torguard ---------------------------------------------------------------------- fabiustus · 2023-11-08 11:48 OMG... I feel dumb right now. Thx that was it! ---------------------------------------------------------------------- trexxeon · 2023-11-08 11:55 No probs, glad it worked out ✌️ ---------------------------------------------------------------------- fabiustus · 2023-11-10 19:55 So, from inside my lan I can access the containers routed through gluetun. But if I connect to my wireguard server (running on my router) from outside, I cannot access the gluetun containers anymore. Do you happen to know how I can allow other subnets to my gluetun container config? When I'm connected to wireguard server from outside, my device has [192.168.200.2](https://192.168.200.2). I suppose if I can add that IP or a whole subnet to gluetun I'll be able to access the gluetun containers. ---------------------------------------------------------------------- powerofneptune · 2023-11-23 13:58 Did you ever get this fixed? I’m getting the same error timeout in my logs too. I don’t know ---------------------------------------------------------------------- fabiustus · 2023-11-23 14:20 Yeah, it was a stupid mistake: For WIREGUARD_ADDRESSES you need to enter the Endpoint Ip ypu get from your vpn provider...I ebtered my lan ip :D ---------------------------------------------------------------------- powerofneptune · 2023-11-23 22:48 Damnit. I do put in the end point ip. And idk what to do. I’m not sure if it’s running right or not though. So I get it to run, it will timeout at first but after retrying connection it connects and the container shows as healthy but anytime I try and log in qbittorrent using the default creds I get invalid username or password. I’ve tried every password I have saved, every username, username with default password, admin with every password and I just can’t get in. ---------------------------------------------------------------------- fabiustus · 2023-11-26 13:37 Hmm.. it's hard to help without knowing your setup and config. Can you post the part in docker compose or the docker command you use for gluetun? Do you use portainer? The only thing I noticed is that the containers that are routed through gluetun needed to be recreated. No idea why but that fixed it for me. Dockstarter has the option prune to delete unused images of containers but I guess it should work within portainer too. But if the gluetun container itself shows unhealthy there's probably a problem with the container config. ---------------------------------------------------------------------- powerofneptune · 2023-11-26 18:19 Oh, well I’m running it through omv on a rpi4. This issue though, looks as if it somehow resolved itself. Uhmm, I got frustrated and just let it sit for a bit and after gluetun kept retrying a connection several times, it finally connected and gave a healthy status. But now I’m somewhat worried if it’s actually working correctly the way it’s supposed to be since anytime I restart the container it will still initially timeout and give an unhealthy but after one retry it connects. It appears to be working with my von since it gives me an ip from somewhere I’m not and it matches the one from the von provider. Also, for some reason I have sonarr and radarr in the same stack and specified which ports to use but every time I run it both of them seem to keep wanting to listen in on the same port. I don’t quite get why or how. But this is what my docker compose file looks like and what the logs in portainer show for gluetun [both screenshots are in here](https://imgur.com/a/RYHC2E6) ---------------------------------------------------------------------- noxiouskarn · 2023-11-28 21:08 when you changed gluetun those other contaners lost visibility of the network container gluetun. So by recreating those containers while the new version of gluetun is running they will see containers /gluetun as a valid network again. Thats all changed gluetun new container id created and other containers need that id info not just that path name