gluetun: Bug: Latest from today 6/5/22 won't get forward port for PIA
Is this urgent?
No
Host OS
Docker on debian buster
CPU arch
x86_64
VPN service provider
Private Internet Access
What are you using to run the container
Portainer
What is the version of Gluetun
Running version latest built on 2022-06-05T16:05:56.477Z (commit f5f65d5)
What’s the problem 🤔
I just pulled latest and it get a log full of these messages below. I reverted to v3 image and is fine. I have REGION set to CA Montreal. I thought maybe PIA dropped port forwarding from ca montreal but reverting worked so it must be a bug in the gluetun image.
Share your logs
2022-06-05T21:31:19-04:00 ERROR [port forwarding] server name not found in servers: ca-montreal.privacy.network
2022-06-05T21:31:19-04:00 INFO [port forwarding] retrying in 5s
2022-06-05T21:31:24-04:00 ERROR [port forwarding] server name not found in servers: ca-montreal.privacy.network
2022-06-05T21:31:24-04:00 INFO [port forwarding] retrying in 5s
2022-06-05T21:31:29-04:00 ERROR [port forwarding] server name not found in servers: ca-montreal.privacy.network
2022-06-05T21:31:29-04:00 INFO [port forwarding] retrying in 5s
2022-06-05T21:31:34-04:00 ERROR [port forwarding] server name not found in servers: ca-montreal.privacy.network
2022-06-05T21:31:34-04:00 INFO [port forwarding] retrying in 5s
2022-06-05T21:31:39-04:00 ERROR [port forwarding] server name not found in servers: ca-montreal.privacy.network
2022-06-05T21:31:39-04:00 INFO [port forwarding] retrying in 5s
2022-06-05T21:31:44-04:00 ERROR [port forwarding] server name not found in servers: ca-montreal.privacy.network
Share your configuration
gluetun:
image: qmcgaw/gluetun:v3
container_name: gluetun
network_mode: lsio
cap_add:
- NET_ADMIN
ports:
- 8001:8000 # gluetun control
- 8191:8191 # flaresolvrr
- 9092:8080 # calibre
- 9093:8086 # calibre api
volumes:
- /apps/gluetun:/gluetun
- /apps/gluetun/post-rules.txt:/iptables/post-rules.txt
environment:
- DOT_IPV6=on
- VPNSP=private internet access
- OPENVPN_USER=redacted
- OPENVPN_PASSWORD=redacted
- OPENVPN_FLAGS=--fast-io --txqueuelen 2000
- REGION=CA Montreal
- PORT_FORWARDING=on
- PORT_FORWARDING_STATUS_FILE=/gluetun/forwarded_port
- TZ=America/New_York
restart: unless-stopped
So I realized after I submitted this that the log was all there, portainer just truncated it to 100 lines. So I restarted with latest to get the version and more log. This time I only got the message once. I don’t think I got a port number though. So I’m switching back to v3 again. Here is the tail of the log from 2nd try that didn’t seem to get the port:
2022-06-05T21:47:31-04:00 INFO [openvpn] TUN/TAP device tun0 opened
2022-06-05T21:47:31-04:00 INFO [openvpn] /sbin/ip link set dev tun0 up mtu 1500
2022-06-05T21:47:31-04:00 INFO [openvpn] /sbin/ip link set dev tun0 up
2022-06-05T21:47:31-04:00 INFO [openvpn] /sbin/ip addr add dev tun0 10.37.110.20/24
2022-06-05T21:47:31-04:00 INFO [openvpn] UID set to nonrootuser
2022-06-05T21:47:31-04:00 INFO [openvpn] Initialization Sequence Completed
2022-06-05T21:47:31-04:00 INFO [dns over tls] downloading DNS over TLS cryptographic files
2022-06-05T21:47:31-04:00 INFO [dns over tls] downloading hostnames and IP block lists
2022-06-05T21:47:32-04:00 INFO [healthcheck] healthy!
2022-06-05T21:47:35-04:00 INFO [dns over tls] init module 0: validator
2022-06-05T21:47:35-04:00 INFO [dns over tls] init module 1: iterator
2022-06-05T21:47:35-04:00 INFO [dns over tls] start of service (unbound 1.15.0).
2022-06-05T21:47:35-04:00 INFO [dns over tls] generate keytag query _ta-4a5c-4f66. NULL IN
2022-06-05T21:47:38-04:00 INFO [dns over tls] ready
2022-06-05T21:47:38-04:00 INFO [vpn] You are running on the bleeding edge of latest!
2022-06-05T21:47:38-04:00 INFO [vpn] VPN gateway IP address: 10.37.110.1
2022-06-05T21:47:38-04:00 ERROR [port forwarding] server name not found in servers: ca-montreal.privacy.network
2022-06-05T21:47:38-04:00 INFO [port forwarding] retrying in 5s
2022-06-05T21:47:39-04:00 INFO [ip getter] Public IP address is 172.98.71.103 (Canada, Quebec, Montréal)
2022-06-05T21:47:40-04:00 INFO [healthcheck] unhealthy: cannot dial: dial tcp4: i/o timeout
2022-06-05T21:47:41-04:00 INFO [healthcheck] healthy!
I think the updated servers.json for CA Montreal region must be wrong or something. The servers completely changed names, but the ones in v3 work.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 31 (9 by maintainers)
Awesome! Closing this for now, feel free to let me know if it still doesn’t work.
EDIT: Also no idea why it still works on v3.29.0
@qdm12 I stopped/removed/deleted the images I had, and then recreated from “latest” and its working now. Sorry for wasting your time. Thanks for the update!
It’s suspicious to me that the code is looking up by a field called “server name”, but the string printed out is the hostname. Unless the naming in the code is off, I think maybe somewhere in a recent checkin hostname got passed instead of server name?