Closed eebette closed 1 year ago
Issue started on 7.2.0
Confirmed connection is verified successfully on 7.1.1:
protonwire | [SUCCESS ] Connected to node-es-03.protonvpn.net (via 195.181.167.194)
protonwire | [SUCCESS ] Connection verified!
Confirmed issue occurs on a fresh install of Raspberry Pi OS on RPi4
I was able to find a way to manually disconnect from the VPN here
Running cat /etc/resolv.conf.protonwire > /etc/resolv.conf && rm /etc/resolv.conf.protonwire
in my container running 7.2.0 fixed this issue for me.
I was able to find a way to manually disconnect from the VPN here
Running
cat /etc/resolv.conf.protonwire > /etc/resolv.conf && rm /etc/resolv.conf.protonwire
in my container running 7.2.0 fixed this issue for me.
Unfortunately, this sets the dns server of your requests to the ISP nameserver which is a huge vulnerability for IP leaks.
I was able to find a way to manually disconnect from the VPN here Running
cat /etc/resolv.conf.protonwire > /etc/resolv.conf && rm /etc/resolv.conf.protonwire
in my container running 7.2.0 fixed this issue for me.Unfortunately, this sets the dns server of your requests to the ISP nameserver which is a huge vulnerability for IP leaks.
Ah, yikes. Thank you for filling me in.
This is resolved by doing one of the following:
1) changing the Netshield option to Block malware only
instead of Block malware, ads and trackers
since that level of Netshield monitoring will break
2) changing the docker environment variable IPCHECK_URL
to a URL that is not blocked by Proton VPN's Netshield. Not sure which one this could be since I haven't tested it but I can confirm that the default and https://icanhazip.com
DOES NOT work as they get blocked.
Version
Latest (ghcr.io/tprasadtp/protonwire:latest)
Credential and Server Validation
nl-free-127.protonvpn.net
or server name likeNL#1
) as mentioned in the docs.System Architecture
aarch64
Kernel Version
6.1.21-v8+
Running on a NAS?
No
Runtime
docker
Version of Runtime
My configuration
Whitelisting API endpoints
I am not using ad-blocking DNS server or gateway
Troubleshooting & Runtime
Container/Pod/systemd log output with DEBUG=1 or
--debug
flagAny additional info
I think maybe this is related to curl(6) happening for
icanhazip.com
:Code of Conduct & PII Redaction