Looks like NordVPN download files endpoint is down... - How to proceed?

[export-mike]

Looks like NordVPN download files endpoint is down... how to proceed?

This has been working for months, And this has also been working since the provider NordVPN required service credentials.

I'm getting this error

 ERROR: OVPN: cannot ping https://downloads.nordcdn.com/configs/files, network or internet unavailable. Cannot download NORDVPN configuration files

version: '3.3'
services:
    transmission-openvpn:
        cap_add:
            - NET_ADMIN
        volumes:
            - '/Users/barry/ts/:/data'
        environment:
            - OPENVPN_PROVIDER=NORDVPN
            - OPENVPN_OPTS=--inactive 3600 --ping 10 --ping-exit 60
            - NORDVPN_COUNTRY=AU
            - OPENVPN_USERNAME=username
            - OPENVPN_PASSWORD=pwd
            - LOCAL_NETWORK=192.168.0.0/16
            - NORDVPN_CATEGORY=legacy_p2p
            - NORDVPN_PROTOCOL=tcp
        logging:
            driver: json-file
            options:
                max-size: 10m
        ports:
            - '9091:9091'
        image: haugene/transmission-openvpn
        restart: always

[KarstenWintermann]

Same issue here, thanks for posting. Other URLs under https://downloads.nordcdn.com like /apps/linux/install.sh seem to work, but /configs/files results in a cloudflare error message.

[export-mike]

just comment out the body of this function and build your own image - this is what helped me
https://github.com/haugene/docker-transmission-openvpn/blob/master/openvpn/nordvpn/configure-openvpn.sh#L220C3-L225C5

[ilike2burnthing]

Potentially - #2638

@KarstenWintermann #1697 (comment)

[KarstenWintermann]

Yes, that fixed it for me. I had to generate a user/password and then wait several hours. Thank you!

[export-mike]

yeah so the script for some reason is trying to ping the config/files directory

when we know this doesn't always work

#1697 (comment)

[edgd1er]

Well not exactly, you cannot ping a directory (error message should be changed, got mixed between nordvpn_dl and nordvpn_cdn vars) . nordvpn fqdn is resolved:

docker-transmission-openvpn/openvpn/nordvpn/configure-openvpn.sh

Line 214 in 42eb2ee

res=$(dig +short ${nordvpn_dl})||true

then ping:

docker-transmission-openvpn/openvpn/nordvpn/configure-openvpn.sh

Line 220 in 42eb2ee

ret=$(ping -c2 ${nordvpn_dl} 2>&1)||true

given nordvpn_dl=downloads.nordcdn.com

Any failure at that moment in the script is due to an ineffective dns resolution and/or a routing problem. Not a container problem nor a provider problem.

Should you have been hammering the login/password validation for any reason ( bad credentials, network problem, ...) , the container will restart and reloading information from nordvpn api and may eventually trigger the api protection (https://support.nordvpn.com/General-info/1749331992/Error-429-Too-Many-Requests.htm)

At the moment, the script store api's information (cities, countries, technologies, servers , ...) in the /tmp which is most of the time a tmpfs mount (ie files stored in memory). there files are lost at container reboot. I should may be place these files at another location to survive the container restart.
The script updates these files everyday if they are older than one day.