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
Comments
Try removing the kill switch variable |
Hola Julio, commented the
Thanks for the help, any other suggestions? |
keep removing not required env variables until you find the culprit. |
Hi, I'm running only this:
back to Is there a straightforward config example / solution that just works? |
Same minimal configuration is not working for me suddenly |
encountered the same issue here. |
getting something simular
|
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. |
seems like there is an issue at Nordvpn side.. hopefully it will get fix soon |
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. |
I’ve been having the same issue this last week. Now it is persistent. |
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. |
Same issue here since I upgraded to the latest version. |
everyone here, you guys can try:
This definitely seems like an issue in nordvpn side due:
|
After trying a LOT I found a solution: Resetting the nord account password. It now connects with the same settings as before. |
I can confirm that change the account password, resolved the problem for me also |
@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 |
@diinngg you are right, thanks. Although I had already changed that password. |
I have the same problem, my account license transfered to an new account and a new password is set, but not solve my problem. |
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. |
@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. |
@benjaminsabatini i think i may have solve that issue on nordlynx container |
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
My .env file
Expected behavior
Successful connection to recommended server
Logs
Additional context
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.
The text was updated successfully, but these errors were encountered: