Open mat926 opened 1 month ago
@qdm12 is more or less the only maintainer of this project and works on it in his free time. Please:
I'm also seeing this issue with Proton VPN
Also getting this issue using ProtonVPN on unraid, with the wireguard configuration. Deployed the container with docker compose, not from the app store
get this too. if you restart qbit it usually works again (same port)
if you restart qbit it usually works again (same port)
Yep that's the thing. Not really a gluetun bug, it's just some programs (qbittorrent) fails to reconnect when the VPN restarts internally "auto-heals". Other torrent clients (I think transmission) do reconnect fine on a vpn internal restart, so it's likely a problem with qbittorrent.
Regarding the wireguard error messages
2024-10-10T02:07:19-07:00 ERROR [wireguard] peer(hrpCβ¦ypH8) - Failed to derive keypair: invalid state for keypair derivation: handshakeZeroed
2024-10-10T02:07:19-07:00 ERROR [wireguard] peer(hrpCβ¦ypH8) - Failed to create response message: handshake initiation must be consumed first
2024-10-10T02:07:21-07:00 ERROR [wireguard] peer(hrpCβ¦ypH8) - Failed to derive keypair: invalid state for keypair derivation: handshakeZeroed
I have never seen those, any idea why this happens? Or was it just a one-off error?
Restarting the qbittorrent container would not work. But I think I see the problem in the log. During the internal vpn restart, it removes the port file forwarded_port.txt , but it does not recreate it after reconnecting. My other container for changing the qbittorrent port fails because that file doesn't exist.
I have no idea why I'm getting those wireguard error messages. It seems to be a one-off error since I don't see it in the recent logs aren't showing that.
Is this urgent?
None
Host OS
No response
CPU arch
None
VPN service provider
ProtonVPN
What are you using to run the container
docker-compose
What is the version of Gluetun
Running version v3.39.1 built on 2024-09-29T18:16:23.495Z (commit 67ae5f5)
What's the problem π€
My forwarded port is unconnectable after a few hours of running the container.
At first when I start the container I check to see the IP and port are open https://www.yougetsignal.com/tools/open-ports/ and it says it's open. But after I leave the container running for 12+ hours, I check it again and the port is closed or timed out.
Share your logs (at least 10 lines)
Share your configuration