Search the Community
Showing results for tags 'gluetun'.
Found 11 results
-
I've a 2014 Mac mini server setup and I'm using Docker to run qBittorrent. I set up AirVPN on GlueTun using WireGuard as shown in the attached Docker Compose file. I've also set up port forwarding and tested it within the AirVPN port forwarding tool. (I followed this guide https://www.youtube.com/watch?v=SQEqsaKN-Go&t=350s for reference). My problem is that my torrent speeds are quite slow in qBittorrent (averaging 30-40Kbps), if I turn off the VPN I can easily hit speeds above 2-3Mbps. I'm wondering if I got something configured incorrectly, or if there are some settings I need to tweak on my end. compose.yml
-
I have my VPN setup to access a server in NY but this happened " 2025-02-23T17:37:29-05:00 INFO [ip getter] Public IP address is 156.96.151.132 (United States, New York, New York City - source: ipinfo) 2025-02-23T17:37:30-05:00 INFO [vpn] You are running 1 commit behind the most recent latest 2025-02-23T17:37:38-05:00 INFO [dns] downloading hostnames and IP block lists 2025-02-23T17:37:42-05:00 INFO [healthcheck] healthy! 2025-02-23T17:37:53-05:00 WARN [dns] cannot update filter block lists: context deadline exceeded (Client.Timeout or context cancellation while reading body) 2025-02-23T17:37:53-05:00 INFO [dns] attempting restart in 20s 2025-02-23T17:38:13-05:00 INFO [dns] downloading hostnames and IP block lists 2025-02-23T17:38:28-05:00 WARN [dns] cannot update filter block lists: context deadline exceeded (Client.Timeout or context cancellation while reading body) 2025-02-23T17:38:28-05:00 INFO [dns] attempting restart in 40s 2025-02-23T17:39:08-05:00 INFO [dns] downloading hostnames and IP block lists 2025-02-23T17:39:23-05:00 INFO [healthcheck] program has been unhealthy for 6s: restarting VPN (healthcheck error: running TLS handshake: context deadline exceeded) 2025-02-23T17:39:23-05:00 INFO [healthcheck] 👉 See https://github.com/qdm12/gluetun-wiki/blob/main/faq/healthcheck.md 2025-02-23T17:39:23-05:00 INFO [healthcheck] DO NOT OPEN AN ISSUE UNLESS YOU READ AND TRIED EACH POSSIBLE SOLUTION 2025-02-23T17:39:23-05:00 INFO [vpn] stopping 2025-02-23T17:39:23-05:00 INFO [firewall] removing allowed port 6881... 2025-02-23T17:39:23-05:00 INFO [firewall] removing allowed port 59529... 2025-02-23T17:39:23-05:00 WARN [dns] cannot update filter block lists: context deadline exceeded (Client.Timeout or context cancellation while reading body) 2025-02-23T17:39:23-05:00 INFO [dns] attempting restart in 1m20s 2025-02-23T17:39:23-05:00 INFO [vpn] starting 2025-02-23T17:39:23-05:00 INFO [firewall] allowing VPN connection... 2025-02-23T17:39:24-05:00 INFO [wireguard] Using available kernelspace implementation 2025-02-23T17:39:24-05:00 INFO [wireguard] Connecting to 195.206.105.226:47107 2025-02-23T17:39:24-05: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. 2025-02-23T17:39:24-05:00 INFO [firewall] setting allowed input port 6881 through interface tun0... 2025-02-23T17:39:24-05:00 INFO [firewall] setting allowed input port 59529 through interface tun0... 2025-02-23T17:39:24-05:00 INFO [healthcheck] healthy! 2025-02-23T17:39:24-05:00 INFO [ip getter] Public IP address is 195.206.105.227 (Switzerland, Zurich, Zürich - source: ipinfo) 2025-02-23T17:39:55-05:00 INFO [healthcheck] healthy! 2025-02-23T17:40:43-05:00 INFO [dns] downloading hostnames and IP block lists 2025-02-23T17:40:46-05:00 INFO [dns] DNS server listening on [::]:53 2025-02-23T17:40:47-05:00 INFO [dns] ready" And then it says connected to Switzerland
-
Hi all, Please note I'm quite inexperienced with networking and server things, I'm learning as I go. I downloaded a .ovpn file to use with Gluetun in Docker. After lots of fiddling, I got Gluetun up and running. However, I wanted to make some changes to my ports (specifically, changed the DDNS address for one of the ports) and I'm wondering if I need to download a new .ovpn file each time I mess with something in the AirVPN client area. Does the .ovpn save details like which ports are forwarded, the DDNS stuff for those ports, etc? Would it be easier for me to remove the .ovpn from my Gluetun docker-compose file and just use my username/password for AirVPN? Thanks.
-
Hi hoping someone can guide me here. when i've connected with the specific credentials via Openwrt, Linux server or client, i always connect to the correct city and if i reconnect quickly enough, i receive the same IP address. but i been having issues with Truenas server and connecting to private tracking sites. i need to have the same IP address with Prowlarr and my torrent. It would be ideal to have my browser as well, so if anyone knows how I can get Tailscale with the exit node working, that would be great. Anyway, i am using Dockge to install qbit, prowlarr and gluetun. The VPN connection works great, ie it connects, and i have access to both apps. They communicate with each other perfectly. Also, i am using the proper port with Airvpn. (love that service) can someone please let me know what i can fix in the stack below to improve this id be very happy. so like i said the stack below works but everytime i reconnect i connect to a different country/city not even close to the IP range specified. this is supposed to be Alhena Tornonto but im connecting to 185.200.116.211 184.75.221.195 AND 146.70.76.35 those are only 3 of the many different address i get when i reconnect. services: gluetun: image: qmcgaw/gluetun container_name: gluetun # Hostname to use for container, required in some instances for the rest of the stack to each other endpoints hostname: gluetun # line above must be uncommented to allow external containers to connect. # See https://github.com/qdm12/gluetun-wiki/blob/main/setup/connect-a-container-to-gluetun.md#external-container-to-gluetun cap_add: - NET_ADMIN devices: - /dev/net/tun:/dev/net/tun ports: - 6881:6881 - 6881:6881/udp - 8085:8085 # qbittorrent - 9696:9696 # Prowlarr volumes: - /mnt/mediapool/docker/stacks/gluetun:/gluetun environment: - VPN_TYPE=wireguard - VPN_SERVICE_PROVIDER=airvpn - WIREGUARD_ENDPOINT_IP=162.219.176.5 - WIREGUARD_PUBLIC_KEY=pubkey - WIREGUARD_PRIVATE_KEY=privatekey - WIREGUARD_PRESHARED_KEY=presharedkey - WIREGUARD_ADDRESSES=10.135.235.221/32 - TZ=America/Toronto restart: always qbittorrent: image: lscr.io/linuxserver/qbittorrent container_name: qbittorrent network_mode: service:gluetun environment: - PUID=1000 - PGID=1000 - TZ=America/Toronto - WEBUI_PORT=8085 volumes: - /mnt/mediapool/docker/stacks/qbit:/config - /mnt/mediapool/media/qbit/downloads/:/downloads depends_on: - gluetun restart: always prowlarr: image: lscr.io/linuxserver/prowlarr:latest container_name: prowlarr network_mode: service:gluetun environment: - PUID=1000 - PGID=1000 - TZ=America/Toronto volumes: - /mnt/mediapool/docker/stacks/prowlarr/data:/config restart: unless-stopped networks: {}
-
I have gluetun and qbittorrent setup and working successfully thanks to other posts in the forum but I’m running into a problem. When the vpn reconnects in gluetun, I need to manually restart qbittorrent otherwise I’m not connectable (firewalled). Is there a way to do this automatically?
-
ANSWERED gluetun port forwarding not supported?
Pulse2492 posted a topic in Troubleshooting and Problems
gluetun docker log ERROR VPN settings: provider settings: port forwarding: port forwarding cannot be enabled: value is not one of the possible choices: airvpn must be one of perfect privacy, private internet access, privatevpn or protonvpn 2024-11-17T20:13:01+01:00 INFO Shutdown successful docker compose version: "3.9" services: vpn: image: qmcgaw/gluetun container_name: vpn networks: proxy: ipv4_address: 10.0.0.4 cap_add: - NET_ADMIN devices: - /dev/net/tun:/dev/net/tun ports: - 1637:1637/udp - 13660:13660/tcp - 13660:13660/udp - 8096:8096 volumes: - ./:/gluetun environment: - VPN_SERVICE_PROVIDER=airvpn - VPN_TYPE=wireguard - VPN_PORT_FORWARDING=on - FIREWALL_VPN_INPUT_PORTS=13660 - WIREGUARD_PRIVATE_KEY=X - WIREGUARD_ADDRESSES=X - WIREGUARD_PRESHARED_KEY=X - WIREGUARD_ENDPOINT_PORT=1637 - SERVER_COUNTRIES=Netherlands - TZ=X - DNS_ADDRESS=10.128.0.1 restart: unless-stopped -
ANSWERED AirVPN with Gluetun docker and WireGuard
Alandil posted a topic in Troubleshooting and Problems
Hi, I have a recurring error that seems to concern a reception problem on the part of cloudflare.com Here it is: [healthcheck] unhealthy: dialing: dial tcp4: lookup cloudflare.com: i/o timeout This causes an unhealthy and a restart of the container, and everything that follows crashes. According to the container designer, the cause can only be external to the container. So I'm asking you to help me find a solution... Thanks in advance! -
I'm running into an issue here, and I'm not sure where to start exactly. The problem is probably not new, it's only that I didn't notice it before. Here's my setup: Proxmox > Debian > Docker > Gluetun > Multiple Qbittorrent instances Qbittorrents are routed through gluetun. I noticed I didn't get much upload, although I'm seeding a lot and was looking into the problem. I tested if ports were open on the dashboard here and it said Connection Refused (111). I did some troubleshooting which got me to restart the stack of gluetun and qbittorrents. I checked if ports are open: Yes! (I didn't change anything in the config by the way) Yay, Problem solved I thought. Only after a couple days, the same error: Connection Refused. I tested again now and the same thing happened after an hour or so. Any ideas? Here's docker-compose and gluetun logs: https://pastebin.com/g7xw5E2R It looks like a firewall issue of some kind, but there's no firewall running on the debian system. Maybe it's a gluetun issue, but I want to ask here as well Thanks in advance
-
Hi, I'm trying to expose Jellyfin to the internet through port forwarding with AirVPN. I'm trying to do a simple example of a hello world http application but I can't make it work through the airdns. My docker compose file is: ``` services: wan-tunneling: image: qmcgaw/gluetun:latest container_name: wan networks: - tunneling cap_add: - NET_ADMIN devices: - /dev/net/tun:/dev/net/tun ports: - 29898:80 volumes: - /mnt/gluetun:/gluetun environment: - VPN_SERVICE_PROVIDER=airvpn - VPN_TYPE=wireguard - WIREGUARD_PRIVATE_KEY=XXX - WIREGUARD_PRESHARED_KEY=XXX - WIREGUARD_ADDRESSES=X.X.X/32 - FIREWALL_VPN_INPUT_PORTS=29898 restart: always hello-world: container_name: web-test network_mode: container:wan image: strm/helloworld-http stdin_open: true tty: true depends_on: wan-tunneling: condition: service_healthy networks: tunneling: external: true ``` If I sh to the glueteun container, I can check that I'm connected to AirVPN. Entering to localhost:29892 does shows the http service running. 29892 is a port forwarding opened in AirVPN and I also set it to local (trough UI) to 80. When I test, is closed. Anyone has any insight in what I'm doing wrong? I did try the port-checker package that is in the docs of port testing for gluetun. If I run that and go to the AirVPN to check the ports, the port says it's open
-
hello, i am switching my gluetun container from mulvad to airvpn, and am having issues getting port forwarding to work. the container works fine when i do not have port forwarding enabled. my docker compose is below. it is populated with values from here: https://airvpn.org/generator/ gluetun: image: qmcgaw/gluetun container_name: gluetun cap_add: - NET_ADMIN devices: - /dev/net/tun:/dev/net/tun ports: - 8080:8080 #qbittorrent - 6881:6881 #qbittorrent - 6881:6881/udp #qbittorrent - 9696:9696 #prowlarr - 8989:8989 #sonarr - 7878:7878 #radarr - 6767:6767 #bazarr volumes: - ./gluetun:/gluetun environment: - VPN_SERVICE_PROVIDER=airvpn - VPN_TYPE=wireguard - WIREGUARD_PRIVATE_KEY= - WIREGUARD_PRESHARED_KEY= - WIREGUARD_ADDRESSES= - SERVER_COUNTRIES=United States - SERVER_CITITES="Chicago Illinois" - FIREWALL_VPN_INPUT_PORTS= - TZ=America/Chicago
-
I have a docker swarm running a gluetun container. The logs show that I am getting an IP and the my port forward is open. I then have a second a container running with transmission. Due to the design of docker swarm it seems that I cannot connect transmission directly to the gluetun container leaving me to connect to it via http proxy. In the transmission container I have set the peerport to my ford port#. I can also run curl ifconfig.io and it returns my airVPN ip. Netstat shows me that the forward port is open on both containers. When I open the UI for transmission and go into preferences it says the port is closed and AirVPN shows it unreachable. Suggestions?