Closed neilrees closed 1 year ago
Well, nl-free-70.protonvpn.net
does not exist. You probably meant node-nl-70.protonvpn.net
.
You cannot make up DNS names from server names. Copy it from ProtonVPN page. little drop down arrow should show you the DNS name or use server name like NL#1
(dont' forget to quote it for YAML).
Understood, presumably that server has existed at some time in the past as this config has worked previously (admittedly a few months ago) and given it was still in the same form as the example config in the README it was presumed to still be valid
Thank you for the pointer, container is now connected!
Well,
nl-free-70.protonvpn.net
does not exist. You probably meantnode-nl-70.protonvpn.net
. You cannot make up DNS names from server names. Copy it from ProtonVPN page. little drop down arrow should show you the DNS name or use server name likeNL#1
(dont' forget to quote it for YAML).
does this changed? i have only the download button. Also it should work with ip? for me it doesnt. Im a free user, but i think this should also work right? Update: i now found the name by analyse the network inspector of the page. But still get this error
[ERROR ] See https://github.com/tprasadtp/protonvpn-docker/blob/master/docs/help.md for troubleshooting.
[ERROR ] Failed to fetch server metadata after 3 tries!
[ERROR ] Please check your internet connection and try again!
[ERROR ] If you have killswitch enabled please disable it and try again!
[ERROR ] Failed to connect to 212.8.252.66
version: "3.9" # optional since v1.27.0
services:
vpn:
image: ghcr.io/tprasadtp/protonwire:latest
init: true
restart: unless-stopped
cap_add:
- NET_ADMIN # Required
#- NET_RAW
environment:
PGID: 100
PUID: 1003
# Quote this value as server name can contain '#'.
PROTONVPN_SERVER: "node-nl-114.protonvpn.net" #NL-FREE#508077
WIREGUARD_PRIVATE_KEY: "xxxxxxxxxxxxxxx"
# Set this to 1 to show debug logs for issue forms.
DEBUG: "1"
# Set this to 0 to disable kill-switch.
KILL_SWITCH: "0"
# NET_ADMIN capability is mandatory!
ports:
- "5800:5800"
- "5900:5900"
sysctls:
net.ipv4.conf.all.rp_filter: 2
net.ipv6.conf.all.disable_ipv6: 1
#- net.ipv6.conf.all.disable_ipv6=1 # Recomended if using ipv4 only
#- net.ipv4.conf.all.src_valid_mark=1
jd2gui:
image: jlesage/jdownloader-2:latest
environment:
- "USER_ID=1003"
- "GROUP_ID=100"
- "TZ=Etc/UTC"
volumes:
- "xxxx"
network_mode: service:vpn
depends_on:
- vpn
i created a new account, now it works yeah :-)
Version
7.2.3
Credential and Server Validation
nl-free-127.protonvpn.net
or server name likeNL#1
) as mentioned in the docs.System Architecture
aarch64
Kernel Version
5.15.0-1035-raspi
Running on a NAS?
No
Runtime
docker
Version of Runtime
Server Version: 20.10.21
My configuration
version: "3.5" services: protonwire: container_name: protonwire image: ghcr.io/tprasadtp/protonwire:7.2.3 init: true restart: unless-stopped environment: PROTONVPN_SERVER: "nl-free-70.protonvpn.net" DEBUG: "1" KILL_SWITCH: "0" WIREGUARD_PRIVATE_KEY: *** cap_add:
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
Is this caused by the URL
https://protonwire-api.vercel.app/v1/server/nl-free-70.protonvpn.net
returning a 404? I get a 404 no matter which server name is used.Is there an example of a URL that contains a value that does not return 404?
Code of Conduct & PII Redaction