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

[ERROR ] Your PROTONVPN_IPCHECK_ENDPOINT: https://ip.prasadt.workers.dev/ is invalid or is not responding with 200 #93

Closed OC-Rookier closed 2 years ago

OC-Rookier commented 2 years ago

I have been trying to fix this issue for a while now, but nothing I do seems to work.

A bit of background: I am trying to run this container on a Pi 4 to run other containers behind a VPN (of course). However, nothing I change in my docker-compose file or environment variables seems to fix this. Trying the 4.x version gives a similar result.

Full log of the container: [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 70-vpn-setup: executing... 1970-04-01 00:09:31+00:00 [OK ] OK! Check URL is secure 1970-02-22 01:56:11+00:00 [ERROR ] Your PROTONVPN_IPCHECK_ENDPOINT: https://ip.prasadt.workers.dev/ is invalid or is not responding with 200 [cont-init.d] 70-vpn-setup: exited 3. [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal.

docker-compose.yml: protonvpn: container_name: protonvpn environment: PROTONVPN_USERNAME: ${PROTONVPN_USERNAME} PROTONVPN_PASSWORD: ${PROTONVPN_PASSWORD} PROTONVPN_SERVER: RANDOM PROTONVPN_TIER: 0 image: ghcr.io/tprasadtp/protonvpn:latest restart: unless-stopped networks: - internet - proxy cap_add: - NET_ADMIN devices: - /dev/net/tun:/dev/net/tun expose: - 8080

The networks defined in the service above were defined in the networks part of the docker-compose.yml file as well. Copied straight from the documentation.

I have tried different health check URLs, putting the container straight on my default (and known good) docker network, and disabling PiHole and running the container, all without success. I put in the ProtonVPN credentials (not the account name and password) but that does not change anything. What I find interesting is that in PiHole, I can see that the Pi hosting this container makes a DNS request for whatever IP check endpoint I put in, and PiHole does not block it.

EDIT: Fixing formatting of logs and docker-compose.yml a bit. I don't know how to do it properly. I also see that the container thinks it is 1970, which is also odd.

OC-Rookier commented 2 years ago

Update: that edit I made saying that the container believed it was 1970 turned out to be the main cause. To resolve, see here.