Closed lv10wizard closed 3 years ago
This is actually a feature and not a bug, i swear,
even if the daemon report that the connection is stable, it actually stalls and every request times out, so I put a mechanism in place to reconnects if a requests to nordvpn API takes longer than 30 seconds, this checks is made ever 5min and can be changed using env variables, Review the readme,
this also happens to me every ~ 4.20h it reconnects, but the container keeps running fine and all the containers in the network are protected at all times.
The real issue is at nordvpn side as far i can tell, the connection just stalls after a while,.there is not much we can do about it.
You could modify the reconnect interval using the env variable to something like a week or so, and after 5 hours get inside of the container and check the status of the daemon/network. Nordvpn daemon seems ok, but all the connections don't respond, we need to reconnect to make it work again.
The container reconnects every ~4h 30m (sometimes immediately after
$RECONNECT
seconds).https://api.nordvpn.com/v1/helpers/ips/insights
(wrongly?) returns"protected":false
after some time.On my Windows machine connected to
United States #8867
via the NordVPN app,curl https://api.nordvpn.com/v1/helpers/ips/insights
returns"protected":false
even though the nordvpn site says:Your Status: Protected
at the top.curl ifconfig.me
returns23.81.176.114
(the IP ofUnited States #8867
reported by the NordVPN app).Run for >5h and check the logs for reconnections.
docker-compose.yml
:The container should automatically reconnect only if there is some connection issue, not on an interval.
The
vpn
container has been up about 4 days.docker logs --tail=1000 vpn | grep 'Uptime:'