imthenachoman / unraid-templates

NordLynx Docker template for unRAID
MIT License
3 stars 1 forks source link

NordLynx Can't Login / Can't Get Private Key #9

Open bigbsxe opened 1 year ago

bigbsxe commented 1 year ago

First off, thank you for your support and development. I am using your older nordvpn container and it works great, but I noticed recently that it's not available on the CA. I have also subsequently noticed that my nordvpn container will just stop. I figured it's time to update to nordlynx, but I'm running into issues.

I can install the nordlynx container with no issues (no private key inputted). I check logs and get the private key missing notification. I copy the script and try to run it and get: docker run --rm --cap-add=NET_ADMIN -e USER=XXX -e PASS=XXX bubuntux/nordvpn:get_private_key A new version of NordVPN is available! Please update the application. We couldn't log you in. Make sure your credentials are correct. If you have MFA enabled, log in using the 'nordvpn login' command. Invalid Username or password.

I have tried my NordVPN service credentials as well as my standard user credentials with no luck. I know the credentials work because I have my Nord account open in another tab and have disabled MFA.

I have tried logging into the container manually: docker login nordvpn and am getting: docker login nordvpn Username: email address Password: Error response from daemon: Get "https://nordvpn/v2/": dial tcp: lookup nordvpn on 192.168.20.1:53: no such host

I'm not super knowledgeable on containers and Docker, so I'm kind of stuck on how to move forward.

On a side note, I also noticed there is no icon for nordlynx image

Any help is appreciated

bigbsxe commented 1 year ago

Bumping this. Hopefully get a response soon?

Kendrick-Bollens commented 1 year ago

Hi, also had to troubleshoot my way through that: I used the old nordvpn container from bubuntu docker run -ti --cap-add=NET_ADMIN --cap-add=NET_RAW --name vpn \ -e USER=user@email.com -e PASS='pas$word' \ -e TECHNOLOGY=NordLynx -d ghcr.io/bubuntux/nordvpn and if that does not work u can try it with the token wich you can generate under the credentials docker run -ti --cap-add=NET_ADMIN --cap-add=NET_RAW --name vpn \ -e TOKE=yourToken \ -e TECHNOLOGY=NordLynx -d ghcr.io/bubuntux/nordvpn Then you can find the privatkey in the log

JabbaDaHutt762 commented 1 year ago

First off, thank you for your support and development. I am using your older nordvpn container and it works great, but I noticed recently that it's not available on the CA. I have also subsequently noticed that my nordvpn container will just stop. I figured it's time to update to nordlynx, but I'm running into issues.

I can install the nordlynx container with no issues (no private key inputted). I check logs and get the private key missing notification. I copy the script and try to run it and get: docker run --rm --cap-add=NET_ADMIN -e USER=XXX -e PASS=XXX bubuntux/nordvpn:get_private_key A new version of NordVPN is available! Please update the application. We couldn't log you in. Make sure your credentials are correct. If you have MFA enabled, log in using the 'nordvpn login' command. Invalid Username or password.

I have tried my NordVPN service credentials as well as my standard user credentials with no luck. I know the credentials work because I have my Nord account open in another tab and have disabled MFA.

I have tried logging into the container manually: docker login nordvpn and am getting: docker login nordvpn Username: email address Password: Error response from daemon: Get "https://nordvpn/v2/": dial tcp: lookup nordvpn on 192.168.20.1:53: no such host

I'm not super knowledgeable on containers and Docker, so I'm kind of stuck on how to move forward.

On a side note, I also noticed there is no icon for nordlynx image

Any help is appreciated

ive done the same and a private key was generated but its creating an orphan image named nordvpn:get_private_key

additionally, when i enter the private key into the settings of the nordlynx docker, i get the following error in the log:

Key is not the correct length or format: 'key' Configuration parsing error