search

tprasadtp / protonvpn-docker

ProtonVPN Wireguard Docker Image. Supports ARMv8 (64-bit ) and x86 (64-Bit).
GNU General Public License v3.0
290 stars 25 forks source link

Failing checkups #27

Closed sebastianarena closed 3 years ago

sebastianarena commented 3 years ago

Hi! Loved the docker container! It seems I have kind of a problem with the health checkups it does internally. This is what the logging shows:

[Service - INIT] PROTONVPN_SVC_DISCONNECTING: 0
[Service - CHCK] #2 Failed!
[Service - CHCK] connected to # instead of #AR

Every check, up until the third, and then reconnects. The weird part is the connection is working perfectly. I use the connection from different containers, and they work, and see the proper IP from Proton.

So, how is the container doing the checkups? Why does it seem to be failing? Any help is appreciated!

tprasadtp commented 3 years ago

Can you please exec into the container and run curl -vv https://ipinfo.io and check if it executes?( Please redact any personal information like IP address in the output). Healthcheck verifies whether country you connected matches with public IP address you got from the VPN.

sebastianarena commented 3 years ago

@tprasadtp thank you for this! It turns out, that domain was being blocked by my internal Pi-Hole! Whitelisting it solved the issue. Maybe something to add to the README so people know the container uses this service and can do the same I did in case they use their own DNS.

tprasadtp commented 3 years ago

It is already in the README.

sebastianarena commented 3 years ago

I don’t know how I missed it. Sorry for wasting your time. Great container! Already starred it! Thanks

github-actions[bot] commented 3 years ago

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days.

github-actions[bot] commented 3 years ago

This issue was closed because it has been stalled for 14 days with no activity.