Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Getting errors from login failure to Whoops! Connection failed. #227

Closed
kikearciniegas opened this issue Jul 22, 2021 · 24 comments
Closed
Labels
bug Something isn't working help wanted Extra attention is needed

Comments

@kikearciniegas
Copy link

I have read the open and closed issues but they are not solved or abandoned or turned into discussions without a real solution or straight forward workaround. It seems that since version 3.7.4 connection is impossible with suggestions and different behaviors all over the place... So my question is, does this work?

Describe the bug
It won't connect, no matter what I do, either the credentials are reported as wrong, or the connection to the server fail.

My docker-compose.yaml file

# deluge docker stack
# --------------------
#
# 65120,62384        - deluge          lightweight, free software, cross-platform bittorrent client
# 65300              - nordvpn         official NordVPN client
#
# (*) world accessible
# -----------------------------------------------------------------------------------------------------------------
#

# For all containers
# Create a folder for each container's data
# mkdir -p /mnt/docker/[container_name]/data

# 1. run - docker-compose -p deluge up -d

version: '3'

services:
  deluge:
  # https://deluge-torrent.org
  # lightweight, free software, cross-platform bittorrent client
  # *** admin interface is available at http://SERVER-IP:8112
  # *** default login user: admin, password deluge
    image: ghcr.io/linuxserver/deluge
    container_name: deluge
    network_mode: service:nordvpn
    security_opt:
        - no-new-privileges:true
    environment:
        - PUID=${PUID}
        - PGID=${PGID}
        - TZ=${TIME_ZONE}
        - UMASK=${UMASK}
        - DELUGE_LOGLEVEL=error
#    ports declared in nordvpn
#    ports:
#      - ${DE_UI_PORT}:8112/tcp       # deluge web-ui
#      - ${DE_PORT}:62384/tcp         # deluge tcp
#      - ${DE_PORT}:62384/udp         # deluge udp
    volumes:
        - ${DOCKER_DIR}/deluge/data:/config:rw
        - ${TDWNLDS_DIR}:/downloads:rw
    healthcheck:
        interval: 5m
        timeout: 5s
        start_period: 60s
        retries: 3
        test: curl -fSs http://127.0.0.1:8112 > /dev/null || exit 1
    restart: unless-stopped
    depends_on:
        - nordvpn

  nordvpn:
  # https://github.com/bubuntux/nordvpn
  # https://hub.docker.com/r/bubuntux/nordvpn
  # official NordVPN client
    image: ghcr.io/bubuntux/nordvpn
    container_name: nordvpn
    networks:
        - avmedia
    cap_add:
        - NET_ADMIN
    environment:
        - TZ=${TIME_ZONE}
        - USER=${NO_USER__SECRET}
        - PASS=${NO_PASSWD__SECRET}
        - TECHNOLOGY=${NO_TECH}
        - DNS=${NO_DNS}
        - KILLSWITCH=${NO_KILLSWITCH}
        - OBFUSCATE=${NO_OBFUSCATE}
        - NETWORK=${SUBNET}
        - DEBUG=Trace
    ports:
        - ${NO_PORT}:8080
        - ${DE_UI_PORT}:8112/tcp       # deluge web-ui
        - ${DE_PORT}:62384/tcp         # deluge tcp
        - ${DE_PORT}:62384/udp         # deluge udp
    healthcheck:
        interval: 5m
        timeout: 5s
        start_period: 60s
        retries: 3
        test: curl -fSs https://ipinfo.io > /dev/null || exit 1
    restart: always

networks:
  avmedia:
    external: true

My .env file

# deluge.env

#
# Global
#
TIME_ZONE=America/Panama
DOMAINNAME0=example.com

#
# Production environment
# - Uncomment the needed section. Can remove un-needed bits here
#
DOCKER_DIR=/mnt/docker
TDWNLDS_DIR=/mnt/avmedia/downloads/torrents
PGID=1000
PUID=1000
UMASK=002

#
# Networks
# - This is your local network and mask
#
SUBNET=10.0.1.0/24

#
# Deluge
#
DE_PORT=62384
DE_UI_PORT=65120

#
# NordVPN
#
NO_PORT=65320
NO_USER__SECRET=myemailhere
NO_PASSWD__SECRET=mypasswordhere
NO_TECH=NordLynx
NO_DNS=9.9.9.9,84.200.69.80,1.1.1.1
NO_KILLSWITCH=Enable
NO_OBFUSCATE=Enable

Expected behavior
Successful connection to recommended server

Logs

++ cat /etc/timezone
+ '[' /UTC '!=' America/Panama ']'
+ '[' -d /usr/share/zoneinfo/America/Panama ']'
+ '[' '!' -e /usr/share/zoneinfo/America/Panama ']'
+ '[' -z America/Panama ']'
+ ln -fs /usr/share/zoneinfo/America/Panama /etc/localtime
+ dpkg-reconfigure -f noninteractive tzdata
++ date -Iseconds
+ echo '[2021-07-21T21:42:27-05:00] Firewall is up, everything has to go through the vpn'
[2021-07-21T21:42:27-05:00] Firewall is up, everything has to go through the vpn
++ ip -o addr show dev eth0
++ awk '$3 == "inet" {print $4}'
+ docker_network=172.16.0.4/24
++ ip -o addr show dev eth0
++ awk '$3 == "inet6" {print $4; exit}'
+ docker6_network=
++ date -Iseconds
+ echo '[2021-07-21T21:42:27-05:00] Enabling connection to secure interfaces'
[2021-07-21T21:42:27-05:00] Enabling connection to secure interfaces
+ [[ -n 172.16.0.4/24 ]]
+ iptables -A INPUT -m conntrack --ctstate ESTABLISHED,RELATED -j ACCEPT
+ iptables -A INPUT -i lo -j ACCEPT
+ iptables -A FORWARD -m conntrack --ctstate ESTABLISHED,RELATED -j ACCEPT
+ iptables -A FORWARD -i lo -j ACCEPT
+ iptables -A OUTPUT -m conntrack --ctstate ESTABLISHED,RELATED -j ACCEPT
+ iptables -A OUTPUT -o lo -j ACCEPT
+ iptables -A OUTPUT -o tap+ -j ACCEPT
+ iptables -A OUTPUT -o tun+ -j ACCEPT
+ iptables -A OUTPUT -o nordlynx+ -j ACCEPT
+ iptables -t nat -A POSTROUTING -o tap+ -j MASQUERADE
+ iptables -t nat -A POSTROUTING -o tun+ -j MASQUERADE
+ iptables -t nat -A POSTROUTING -o nordlynx+ -j MASQUERADE
+ [[ -n '' ]]
++ date -Iseconds
+ echo '[2021-07-21T21:42:27-05:00] Enabling connection to nordvpn group'
[2021-07-21T21:42:27-05:00] Enabling connection to nordvpn group
+ [[ -n 172.16.0.4/24 ]]
+ iptables -A OUTPUT -m owner --gid-owner nordvpn -j ACCEPT
+ [[ -n '' ]]
++ date -Iseconds
+ echo '[2021-07-21T21:42:27-05:00] Enabling connection to docker network'
[2021-07-21T21:42:27-05:00] Enabling connection to docker network
+ [[ -n 172.16.0.4/24 ]]
+ iptables -A INPUT -s 172.16.0.4/24 -j ACCEPT
+ iptables -A FORWARD -d 172.16.0.4/24 -j ACCEPT
+ iptables -A FORWARD -s 172.16.0.4/24 -j ACCEPT
+ iptables -A OUTPUT -d 172.16.0.4/24 -j ACCEPT
+ [[ -n '' ]]
+ [[ -n 172.16.0.4/24 ]]
+ [[ -n 10.0.1.0/24 ]]
++ ip route
++ awk '/default/ {print $3}'
+ gw=172.16.0.1
+ for net in ${NETWORK//[;,]/ }
++ date -Iseconds
+ echo '[2021-07-21T21:42:27-05:00] Enabling connection to network 10.0.1.0/24'
[2021-07-21T21:42:27-05:00] Enabling connection to network 10.0.1.0/24
+ ip route
+ grep -q 10.0.1.0/24
+ ip route add to 10.0.1.0/24 via 172.16.0.1 dev eth0
+ iptables -A INPUT -s 10.0.1.0/24 -j ACCEPT
+ iptables -A FORWARD -d 10.0.1.0/24 -j ACCEPT
+ iptables -A FORWARD -s 10.0.1.0/24 -j ACCEPT
+ iptables -A OUTPUT -d 10.0.1.0/24 -j ACCEPT
+ [[ -n '' ]]
+ [[ -n '' ]]
+ mkdir -p /dev/net
+ [[ -c /dev/net/tun ]]
+ mknod -m 0666 /dev/net/tun c 10 200
+ restart_daemon
++ date -Iseconds
[2021-07-21T21:42:27-05:00] Restarting the service
+ echo '[2021-07-21T21:42:27-05:00] Restarting the service'
+ service nordvpn stop
+ rm -rf /run/nordvpn/nordvpnd.sock
+ service nordvpn start
++ date -Iseconds
+ echo '[2021-07-21T21:42:27-05:00] Waiting for the service to start'
+ attempt_counter=0
+ max_attempts=50
+ '[' -S /run/nordvpn/nordvpnd.sock ']'
+ '[' 0 -eq 50 ']'
+ attempt_counter=1
+ sleep 0.1
[2021-07-21T21:42:27-05:00] Waiting for the service to start
+ '[' -S /run/nordvpn/nordvpnd.sock ']'
+ [[ -z 8svN7T7GCG94eb4jP^b9*f0l ]]
++ date -Iseconds
+ echo '[2021-07-21T21:42:28-05:00] Logging in'
+ nordvpn logout
[2021-07-21T21:42:28-05:00] Logging in
+ nordvpn login --username myemailhere --password 'mypasswordhere'
-
-
\
|
/
-
\
|
/
-
\
|
  
Welcome to NordVPN! You can now connect to VPN by using 'nordvpn connect'.
++ date -Iseconds
++ nordvpn -version
+ echo '[2021-07-21T21:42:30-05:00] Setting up NordVPN Version 3.10.0'
+ [[ -n '' ]]
+ [[ -n 9.9.9.9,84.200.69.80,1.1.1.1 ]]
[2021-07-21T21:42:30-05:00] Setting up NordVPN Version 3.10.0
+ nordvpn set dns 9.9.9.9 84.200.69.80 1.1.1.1
DNS is set to '1.1.1.1, 84.200.69.80, 9.9.9.9' successfully.
+ [[ -n '' ]]
+ [[ -n Enable ]]
+ nordvpn set killswitch Enable
Kill Switch is set to 'enabled' successfully.
+ [[ -n Enable ]]
+ nordvpn set obfuscate Enable
Obfuscation is successfully set to 'enabled'.
+ [[ -n '' ]]
+ [[ -n NordLynx ]]
+ nordvpn set technology NordLynx
Technology is successfully set to 'NordLynx'.
+ [[ -n 172.16.0.4/24 ]]
+ nordvpn whitelist add subnet 172.16.0.4/24
Subnet 172.16.0.0/24 is whitelisted successfully.
+ [[ -n 10.0.1.0/24 ]]
+ for net in ${NETWORK//[;,]/ }
+ nordvpn whitelist add subnet 10.0.1.0/24
Subnet 10.0.1.0/24 is whitelisted successfully.
+ [[ -n '' ]]
+ [[ -n '' ]]
+ [[ -n '' ]]
+ [[ -n Trace ]]
+ nordvpn settings
-
-
Technology: NordLynx
Firewall: enabled
Kill Switch: enabled
CyberSec: disabled
Notify: disabled
Auto-connect: disabled
IPv6: disabled
DNS: 1.1.1.1, 84.200.69.80, 9.9.9.9
Whitelisted subnets:
	172.16.0.0/24
	10.0.1.0/24
t
++ date -Iseconds
[2021-07-21T21:42:30-05:00] Connecting...
+ echo '[2021-07-21T21:42:30-05:00] Connecting...'
+ attempt_counter=0
+ max_attempts=15
+ nordvpn connect
-
-
\
|
/
-
\
|
/
-
\
|
Connecting to United States #8077 (us8077.nordvpn.com)
-
-
Whoops! Connection failed. Please try again. If the problem persists, contact our customer support.
+ '[' 0 -eq 15 ']'
+ attempt_counter=1
5
+ nordvpn connect
-
-
\
|
Connecting to United States #8916 (us8916.nordvpn.com)
-
-
Whoops! Connection failed. Please try again. If the problem persists, contact our customer support.
+ '[' 1 -eq 15 ']'
+ attempt_counter=2
5
+ nordvpn connect
-
-
\
|
/
-
\
|
/
-
\
|
/
Connecting to United States #8786 (us8786.nordvpn.com)
-
-
Whoops! Connection failed. Please try again. If the problem persists, contact our customer support.
+ '[' 2 -eq 15 ']'
+ attempt_counter=3
5
+ nordvpn connect

Additional context

  • Linux version 5.11.22-2-pve (build@proxmox) (gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) Specify region #1 SMP PVE 5.11.22-4 (Tue, 20 Jul 2021 21:40:02 +0200)
  • Client: Docker Engine - Community
    Version: 20.10.7
    API version: 1.41
    Go version: go1.13.15
    Git commit: f0df350
    Built: Wed Jun 2 11:56:47 2021
    OS/Arch: linux/amd64
    Context: default
    Experimental: true

Please any help is greatly appreciated, if this doesn't work please also let me know so people with similar issues can either fix or move on to a working solution.

@kikearciniegas kikearciniegas added bug Something isn't working help wanted Extra attention is needed labels Jul 22, 2021
@bubuntux
Copy link
Owner

Try removing the kill switch variable

@kikearciniegas
Copy link
Author

Hola Julio, commented the # - KILLSWITCH=${NO_KILLSWITCH} line, but same thing... same error message.

Whoops! Connection failed. Please try again. If the problem persists, contact our customer support.

Thanks for the help, any other suggestions?

@bubuntux
Copy link
Owner

keep removing not required env variables until you find the culprit.

@kikearciniegas
Copy link
Author

Hi, I'm running only this:

    environment:
        - TZ=America/Chicago
        - USER=[redacted]
        - PASS=[redacted]
        - DEBUG=Trace

back to Invalid Username or password.

Is there a straightforward config example / solution that just works?

@roobann
Copy link

roobann commented Jul 24, 2021

Hi, I'm running only this:

    environment:
        - TZ=America/Chicago
        - USER=[redacted]
        - PASS=[redacted]
        - DEBUG=Trace

back to Invalid Username or password.

Is there a straightforward config example / solution that just works?

Same minimal configuration is not working for me suddenly

@waiteck89
Copy link

encountered the same issue here.

@Crooklar
Copy link

Crooklar commented Jul 25, 2021

getting something simular


|
/

It's not you, it's us. We're having trouble reaching our servers. If the issue persists, please contact our customer support.

[2021-07-25T09:13:41+01:00] Invalid Username or password.

[2021-07-25T09:13:42+01:00] Firewall is up, everything has to go through the vpn

[2021-07-25T09:13:42+01:00] Enabling connection to secure interfaces

[2021-07-25T09:13:42+01:00] Enabling connection to nordvpn group

[2021-07-25T09:13:42+01:00] Enabling connection to docker network

[2021-07-25T09:13:42+01:00] Enabling connection to network 192.168.1.0/24

[2021-07-25T09:13:42+01:00] Restarting the service

start-stop-daemon: warning: failed to kill 97: No such process

[2021-07-25T09:13:42+01:00] Waiting for the service to start

[2021-07-25T09:13:42+01:00] Logging in

@macuros
Copy link

macuros commented Jul 26, 2021

Same here:

Screenshot 2021-07-26 at 17 39 28

It just stopped working.

@macuros
Copy link

macuros commented Jul 26, 2021

For some reason, it is working again with v3.9.5-1. I'm using Portainer and I've just deleted the whole stack and recreated it again.

@bubuntux
Copy link
Owner

seems like there is an issue at Nordvpn side.. hopefully it will get fix soon

@AnanthVivekanand
Copy link

Same issue here, can reproduce, but have been having this issue for a couple days now. The issue is not on the nordvpn side, because I use nordvpn login on the host machine just fine. The issue is only inside the docker container.

@jonatasgz
Copy link

I’ve been having the same issue this last week. Now it is persistent.

@wilsonwilsonlg
Copy link

Same issue here. And don't seems to be in Nordvpn side, at least I can use Nordvpn with the Firefox plugin and with the Azinchen image. May be it's related to the NordLynx connection? As I'm not sure if Azinchen image is using the NordLynx.

@p-j
Copy link

p-j commented Jul 29, 2021

Same issue here since I upgraded to the latest version.
Connecting to the container I can run nordvpn account just fine, it will return the correct information, but I'm not able to connect neither using OpenVPN nor using NordLynx. I'm alway getting Whoops! Connection failed. Please try again. If the problem persists, contact our customer support.

@bubuntux
Copy link
Owner

everyone here, you guys can try:

  • Enable DEBUG=Trace
  • Use the minimal required variables to connect
  • Try to connect to a diff country
  • execute it using CLI
  • Try using an older version of the container

This definitely seems like an issue in nordvpn side due:

  • Is not happening to everyone
  • It start happening suddenly
  • The error message

@jonatasgz
Copy link

After trying a LOT I found a solution:

Resetting the nord account password. It now connects with the same settings as before.

@wilsonwilsonlg
Copy link

I can confirm that change the account password, resolved the problem for me also

@diinngg
Copy link

diinngg commented Aug 10, 2021

@kikearciniegas you should be aware that the log you posted may have included your password, though it seems the resolution here was to change the account password anyway

@kikearciniegas
Copy link
Author

@diinngg you are right, thanks. Although I had already changed that password.

@isibizi
Copy link

isibizi commented Sep 8, 2021

I have the same problem, my account license transfered to an new account and a new password is set, but not solve my problem.

@benjaminsabatini
Copy link

Eh... question. Same problem.

Whoops! Something went wrong. Please try again. If the problem persists, contact our customer support.

I had this same problem with the official Linux app, but after removing and reinstalling it, it worked again. I can re-add the container, but it does not fix the problem in the same way.

@bubuntux
Copy link
Owner

@benjaminsabatini i would recommend you migrate to https://github.com/bubuntux/nordlynx

@benjaminsabatini
Copy link

@benjaminsabatini i would recommend you migrate to https://github.com/bubuntux/nordlynx

I tried several times but had to revert to this container v3.10.0-1-1. The new nordlynx container worked with qbittorrent, but I couldn't get jackett to route through it and connect to indices.

So, I went back to v3.10.0-1-1 (latest and master wouldn't work). At first, it wouldn't connect, but after switching to OpenVPN it's fine again. NordLynx/Wireguard seems to have been at least part of the problem, I guess.

@bubuntux
Copy link
Owner

@benjaminsabatini i think i may have solve that issue on nordlynx container

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests