What's new

Release Asuswrt-Merlin 388.2 is now available for select models

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Status
Not open for further replies.
anyone getting " Error - Authentication failure!"
when uploading nordvpn .ovpn file
RT-AX86U
 
anyone getting " Error - Authentication failure!"
when uploading nordvpn .ovpn file
RT-AX86U
You need to enter your username and password, these are not embedded in the ovpn file.
 
I'm simply trying to upload the opvn file
this does not require a password
I don't see how you can get an authentication failure on uploading a config file - that does not generate a client connection. You are doing something that's causing the client to connect before you've had the chance to enter the username and password, which would be why there's an authentication error.
 
I don't see how you can get an authentication failure on uploading a config file - that does not generate a client connection. You are doing something that's causing the client to connect before you've had the chance to enter the username and password, which would be why there's an authentication error.
is there log that would reflect the cause?
 
Did you enter the required username and password?
Did you enter the required username and password?
yes
username and password work with desktop app
I flashed the router to ASUS firmware, then use the config file and get the same results, "Authentication failure" when turning on the service
thinking something in router at this point?
 
yes
username and password work with desktop app
I flashed the router to ASUS firmware, then use the config file and get the same results, "Authentication failure" when turning on the service
thinking something in router at this point?
Look in the router's System Log for any error messages when you try to enable the VPN.
 
I think I had the same problem when I was using OpenVPN with Windscribe.

Try this:
1. Insert username and password on the client settings.
2. Hit apply to save them.
3. Upload the config file you got from your provider
4. Try to enable the service.

Screenshot 2023-07-09 at 20-18-45 ASUS Wireless Router RT-AX56U - OpenVPN Client Settings.png
 
I think I had the same problem when I was using OpenVPN with Windscribe.

Try this:
1. Insert username and password on the client settings.
2. Hit apply to save them.
3. Upload the config file you got from your provider
4. Try to enable the service.

View attachment 51607
here's the log
Jul 9 13:21:25 rc_service: httpd 1547:notify_rc restart_vpnclient1
Jul 9 13:21:25 openvpn-routing: Clearing routing table for VPN client 1
Jul 9 13:21:25 ovpn-client1[23824]: OpenVPN 2.6.3 arm-buildroot-linux-gnueabi [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD]
Jul 9 13:21:25 ovpn-client1[23824]: library versions: OpenSSL 1.1.1t 7 Feb 2023, LZO 2.08
Jul 9 13:21:25 ovpn-client1[23825]: WARNING: --ping should normally be used with --ping-restart or --ping-exit
Jul 9 13:21:25 ovpn-client1[23825]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Jul 9 13:21:25 ovpn-client1[23825]: TCP/UDP: Preserving recently used remote address: [AF_INET]153.92.40.110:1194
Jul 9 13:21:25 ovpn-client1[23825]: Socket Buffers: R=[524288->524288] S=[524288->524288]
Jul 9 13:21:25 ovpn-client1[23825]: UDPv4 link local: (not bound)
Jul 9 13:21:25 ovpn-client1[23825]: UDPv4 link remote: [AF_INET]153.92.40.110:1194
Jul 9 13:21:25 ovpn-client1[23825]: TLS: Initial packet from [AF_INET]153.92.40.110:1194, sid=aef285bd 33e72bf6
Jul 9 13:21:25 ovpn-client1[23825]: WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Jul 9 13:21:25 ovpn-client1[23825]: VERIFY OK: depth=2, C=PA, O=NordVPN, CN=NordVPN Root CA
Jul 9 13:21:25 ovpn-client1[23825]: VERIFY OK: depth=1, O=NordVPN, CN=NordVPN CA8
Jul 9 13:21:25 ovpn-client1[23825]: VERIFY KU OK
Jul 9 13:21:25 ovpn-client1[23825]: Validating certificate extended key usage
Jul 9 13:21:25 ovpn-client1[23825]: ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
Jul 9 13:21:25 ovpn-client1[23825]: VERIFY EKU OK
Jul 9 13:21:25 ovpn-client1[23825]: VERIFY X509NAME OK: CN=ca1647.nordvpn.com
Jul 9 13:21:25 ovpn-client1[23825]: VERIFY OK: depth=0, CN=ca1647.nordvpn.com
Jul 9 13:21:25 ovpn-client1[23825]: Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, peer certificate: 4096 bit RSA, signature: RSA-SHA512
Jul 9 13:21:25 ovpn-client1[23825]: [ca1647.nordvpn.com] Peer Connection Initiated with [AF_INET]153.92.40.110:1194
Jul 9 13:21:25 ovpn-client1[23825]: TLS: move_session: dest=TM_ACTIVE src=TM_INITIAL reinit_src=1
Jul 9 13:21:25 ovpn-client1[23825]: TLS: tls_multi_process: initial untrusted session promoted to trusted
Jul 9 13:21:26 ovpn-client1[23825]: SENT CONTROL [ca1647.nordvpn.com]: 'PUSH_REQUEST' (status=1)
Jul 9 13:21:31 ovpn-client1[23825]: SENT CONTROL [ca1647.nordvpn.com]: 'PUSH_REQUEST' (status=1)
Jul 9 13:21:31 ovpn-client1[23825]: AUTH: Received control message: AUTH_FAILED
Jul 9 13:21:31 ovpn-client1[23825]: SIGTERM[soft,auth-failure] received, process exiting
Jul 9 13:21:53 rc_service: httpd 1547:notify_rc start_vpnclient1
Jul 9 13:21:53 ovpn-client1[23933]: OpenVPN 2.6.3 arm-buildroot-linux-gnueabi [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD]
Jul 9 13:21:53 ovpn-client1[23933]: library versions: OpenSSL 1.1.1t 7 Feb 2023, LZO 2.08
Jul 9 13:21:53 ovpn-client1[23934]: WARNING: --ping should normally be used with --ping-restart or --ping-exit
Jul 9 13:21:53 ovpn-client1[23934]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Jul 9 13:21:53 ovpn-client1[23934]: TCP/UDP: Preserving recently used remote address: [AF_INET]153.92.40.110:1194
Jul 9 13:21:53 ovpn-client1[23934]: Socket Buffers: R=[524288->524288] S=[524288->524288]
Jul 9 13:21:53 ovpn-client1[23934]: UDPv4 link local: (not bound)
Jul 9 13:21:53 ovpn-client1[23934]: UDPv4 link remote: [AF_INET]153.92.40.110:1194
Jul 9 13:21:53 ovpn-client1[23934]: TLS: Initial packet from [AF_INET]153.92.40.110:1194, sid=7d4bb496 abeb94af
Jul 9 13:21:53 ovpn-client1[23934]: WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Jul 9 13:21:53 ovpn-client1[23934]: VERIFY OK: depth=2, C=PA, O=NordVPN, CN=NordVPN Root CA
Jul 9 13:21:53 ovpn-client1[23934]: VERIFY OK: depth=1, O=NordVPN, CN=NordVPN CA8
Jul 9 13:21:53 ovpn-client1[23934]: VERIFY KU OK
Jul 9 13:21:53 ovpn-client1[23934]: Validating certificate extended key usage
Jul 9 13:21:53 ovpn-client1[23934]: ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
Jul 9 13:21:53 ovpn-client1[23934]: VERIFY EKU OK
Jul 9 13:21:53 ovpn-client1[23934]: VERIFY X509NAME OK: CN=ca1647.nordvpn.com
Jul 9 13:21:53 ovpn-client1[23934]: VERIFY OK: depth=0, CN=ca1647.nordvpn.com
Jul 9 13:21:53 ovpn-client1[23934]: Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, peer certificate: 4096 bit RSA, signature: RSA-SHA512
Jul 9 13:21:53 ovpn-client1[23934]: [ca1647.nordvpn.com] Peer Connection Initiated with [AF_INET]153.92.40.110:1194
Jul 9 13:21:53 ovpn-client1[23934]: TLS: move_session: dest=TM_ACTIVE src=TM_INITIAL reinit_src=1
Jul 9 13:21:53 ovpn-client1[23934]: TLS: tls_multi_process: initial untrusted session promoted to trusted
Jul 9 13:21:54 ovpn-client1[23934]: SENT CONTROL [ca1647.nordvpn.com]: 'PUSH_REQUEST' (status=1)
Jul 9 13:22:00 ovpn-client1[23934]: SENT CONTROL [ca1647.nordvpn.com]: 'PUSH_REQUEST' (status=1)
Jul 9 13:22:00 ovpn-client1[23934]: AUTH: Received control message: AUTH_FAILED
Jul 9 13:22:00 ovpn-client1[23934]: SIGTERM[soft,auth-failure] received, process exiting
Jul 9 13:23:16 acsd: acs_candidate_score_intf(1112): eth7: intf check failed for chanspec: 0xe832 (36/160)
Jul 9 13:23:16 acsd: acs_candidate_score_bgnoise(1577): eth7: bgnoise check failed for chanspec: 0xe832 (36/160)
Jul 9 13:23:16 acsd: acs_candidate_score_txop(1835): eth7: txop check failed for chanspec: 0xe832 (36/160)
Jul 9 13:23:16 acsd: acs_candidate_score_intf(1112): eth7: intf check failed for chanspec: 0xe932 (40/160)
Jul 9 13:23:16 acsd: acs_candidate_score_bgnoise(1577): eth7: bgnoise check failed for chanspec: 0xe932 (40/160)
Jul 9 13:23:16 acsd: acs_candidate_score_txop(1835): eth7: txop check failed for chanspec: 0xe932 (40/160)
Jul 9 13:23:16 acsd: acs_candidate_score_intf(1112): eth7: intf check failed for chanspec: 0xea32 (44/160)
Jul 9 13:23:16 acsd: acs_candidate_score_bgnoise(1577): eth7: bgnoise check failed for chanspec: 0xea32 (44/160)
Jul 9 13:23:16 acsd: acs_candidate_score_txop(1835): eth7: txop check failed for chanspec: 0xea32 (44/160)
Jul 9 13:23:16 acsd: acs_candidate_score_intf(1112): eth7: intf check failed for chanspec: 0xeb32 (48/160)
Jul 9 13:23:16 acsd: acs_candidate_score_bgnoise(1577): eth7: bgnoise check failed for chanspec: 0xeb32 (48/160)
Jul 9 13:23:16 acsd: acs_candidate_score_txop(1835): eth7: txop check failed for chanspec: 0xeb32 (48/160)

@zer0bitz for your suggested method - when you select upload the user and password boxes go blank
 
>> AUTH: Received control message: AUTH_FAILED

This does seem to point to an issue with the credentials.

A quick google of that erorr and NordVPN took me here:
Something to do with using service credentials.

--------------------------------------------------------
UPDATE:

I just got this e-mail from them about the issue.
Due to the recent change in the authentication process, using your email and password for the manual connection method will no longer work.
You will need to use the service credentials instead.
You can find your service credentials by following these steps:
  1. Please log in to your Nord Account by following this link: https://my.nordaccount.com/dashboard/nordvpn/
  2. Click on the NordVPN tab on the left panel which is under the Services tab.
  3. Scroll down and locate the Manual Setup tab, then click on Set up NordVPN manually:
  4. Verify your email by entering the one-time code you will receive in your registered email inbox. If you are unable to find the email, please make sure to also check your spam/junk folder.
  5. Copy your service credentials by using the buttons on the right.
 
Last edited:
>> AUTH: Received control message: AUTH_FAILED

This does seem to point to and issue with the credentials

A quick google of that erorr and NordVPN took me here:
Something to do with using service credentials.

--------------------------------------------------------
UPDATE:

I just got this e-mail from them about the issue.
Due to the recent change in the authentication process, using your email and password for the manual connection method will no longer work.
You will need to use the service credentials instead.
You can find your service credentials by following these steps:
  1. Please log in to your Nord Account by following this link: https://my.nordaccount.com/dashboard/nordvpn/
  2. Click on the NordVPN tab on the left panel which is under the Services tab.
  3. Scroll down and locate the Manual Setup tab, then click on Set up NordVPN manually:
  4. Verify your email by entering the one-time code you will receive in your registered email inbox. If you are unable to find the email, please make sure to also check your spam/junk folder.
  5. Copy your service credentials by using the buttons on the right.
THANK YOU!!! fixed
 
1. Insert username and password on the client settings.
2. Hit apply to save them.
3. Upload the config file you got from your provider
4. Try to enable the service.
That's the wrong order. Uploading the config file will wipe out any existing settings.
 
yes
username and password work with desktop app
I flashed the router to ASUS firmware, then use the config file and get the same results, "Authentication failure" when turning on the service
thinking something in router at this point?
thanks for your help
much appreciated
 
I'm using RT-AX88U and I updated to "388.2_beta2"
but the router says it has an update to "388.2_2"

I feel like i went from 388.2_2 to this _beta, and the _beta version has more features.

If I'm using a beta does the router want me to go to a more official firmware and thats why it's showing an update available or should I actually update?
 
Welcome to the forums @BufferBloatCEO.

388.2_2 release final supercedes 388.2_2 Beta.

Update now.
 
Status
Not open for further replies.

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top