Closed brpaz closed 1 month ago
@qdm12 is more or less the only maintainer of this project and works on it in his free time. Please:
Deleting the file servers.json in /gluetun fixed this problem for me
Yup ran into this same issue after redeploying my image to latest. Deleting servers.json also fixed the issue.
Running on Synology DMS 7.2.1
It worked for me as well. Seems that for some reason the servers list is not being updated correctly. I will close this issue,
Closed issues are NOT monitored, so commenting here is likely to be not seen. If you think this is still unresolved and have more information to bring, please create another issue.
This is an automated comment setup because @qdm12 is the sole maintainer of this project which became too popular to monitor issues closed.
That's strange, and what happens if you run the v3.38 image and then back the v3.39 image? Does it fail again? 🤔
Edit: Looks like in my case, "FREE_ONLY" is not compatible with "PORT_FORWARDING". Once I removed port forwarding from the config it just worked.
Hello! I am using gluetun within docker and I am having the same issue using ProtonVPN and free only servers.
I noticed, inside the servers.json file there are servers that meet the criteria of UDP, Free, and OpenVPN, but it just returns and repeats the following error:
2024-09-24T22:41:51Z ERROR [vpn] finding a valid server connection: filtering servers: no server found: for VPN openvpn; protocol udp; free tier only
If I remove "FREE_ONLY=ON" then that results in successful server connections, but invalid credentials since my account is free only.
Below is a snip of my docker-compose. I left out ports and volumes for privacy.
gluetun:
image: qmcgaw/gluetun:latest
cap_add:
- NET_ADMIN
environment:
- VPN_SERVICE_PROVIDER=protonvpn
- OPENVPN_USER=<userID>
- OPENVPN_PASSWORD=<userPass>
- PORT_FORWARDING=on
- FREE_ONLY=on
network_mode: bridge
Edit: Looks like in my case, "FREE_ONLY" is not compatible with "PORT_FORWARDING". Once I removed port forwarding from the config it just worked.
port forwarding only filter is not supported: together with free only filter
if a user tries to use it.I think this is resolved, so closing this! And thanks for debugging and finding out what the error was!
Closed issues are NOT monitored, so commenting here is likely to be not seen. If you think this is still unresolved and have more information to bring, please create another issue.
This is an automated comment setup because @qdm12 is the sole maintainer of this project which became too popular to monitor issues closed.
Similar issue here, using this:
environment:
- TZ=xxxxxx/xxxxxx
- PUID=xxx
- PGID=xxx
- VPN_SERVICE_PROVIDER=protonvpn
- VPN_TYPE=wireguard
- VPN_PORT_FORWARDING=on
- VPN_PORT_FORWARDING_PROVIDER=protonvpn
- SECURE_CORE_ONLY=on
- PORT_FORWARD_ONLY=on
- WIREGUARD_PRIVATE_KEY=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx=
- SHADOWSOCKS=off
- HTTPPROXY=off
And it says:
2024-09-29T16:47:40+02:00 ERROR [vpn] finding a VPN server: filtering servers: no server found: for VPN wireguard; protocol udp; port forwarding only; secure core only; target ip address 0.0.0.0
Despite the fact that there are, indeed, many ProtonVPN servers that support Wireguard, secure-core and port forwarding.
Tried deleting /gluetun/servers.json and no change.
Tried adding - PROTOCOL=tcp
and no change.
I see that in the json, only OpenVPN servers have the fields "udp":
and "tcp":
, but the wireguard servers have neither field. Could that be why the wireguard ones return false for both udp and tcp?
Is this urgent?
Yes
Host OS
Fedora
CPU arch
x86_64
VPN service provider
ProtonVPN
What are you using to run the container
Kubernetes
What is the version of Gluetun
Running version v3.38.0 built on 2024-03-25T15:53:33.983Z (commit b3ceece)
What's the problem 🤔
Hello.
After updating to gluetun 3.39, I cannot get a connection to ProtonVPN. It always says there are no servers available.
[vpn] finding a valid server connection: filtering servers: no server found: for VPN openvpn; protocol udp
I have tried updating the servers manually but still get the same error.
Share your logs (at least 10 lines)
Share your configuration
No response