Problem setting up VPN on Beryle AX with NordVPN

Technical Support for Routers VPN, DNS, Leaks
1

I already update the firmware to the latest. This is the first time to setup the new Beryl AX router with NordVPN client. I am getting this error in the log:

Sat Jan 6 12:10:33 2024 daemon.notice netifd: ovpnclient (2909): * Rule ‘process_mark’\n
Sat Jan 6 12:10:33 2024 daemon.notice netifd: ovpnclient (2909): * Rule ‘wan_in_conn_mark’\n
Sat Jan 6 12:10:33 2024 daemon.notice netifd: ovpnclient (2909): * Rule ‘lan_in_conn_mark_restore’\n
Sat Jan 6 12:10:33 2024 daemon.notice netifd: ovpnclient (2909): * Rule ‘out_conn_mark_restore’\n
Sat Jan 6 12:10:33 2024 daemon.notice netifd: ovpnclient (2909): * Zone ‘lan’\n
Sat Jan 6 12:10:33 2024 daemon.notice netifd: ovpnclient (2909): * Zone ‘wan’\n
Sat Jan 6 12:10:33 2024 daemon.notice netifd: ovpnclient (2909): * Zone ‘guest’\n
Sat Jan 6 12:10:33 2024 daemon.notice netifd: ovpnclient (2909): * Zone ‘ovpnclient’\n
Sat Jan 6 12:10:33 2024 daemon.notice netifd: ovpnclient (2909): * Set tcp_ecn to off\n
Sat Jan 6 12:10:33 2024 daemon.notice netifd: ovpnclient (2909): * Set tcp_syncookies to on\n
Sat Jan 6 12:10:33 2024 daemon.notice netifd: ovpnclient (2909): * Set tcp_window_scaling to on\n
Sat Jan 6 12:10:33 2024 daemon.notice netifd: ovpnclient (2909): * Running script ‘/etc/firewall.nat6’\n
Sat Jan 6 12:10:33 2024 daemon.notice netifd: ovpnclient (2909): * Running script ‘/etc/firewall.swap_wan_in_conn_mark.sh’\n
Sat Jan 6 12:10:33 2024 daemon.notice netifd: ovpnclient (2909): * Running script ‘/etc/firewall.vpn_server_policy.sh’\n
Sat Jan 6 12:10:33 2024 daemon.notice netifd: ovpnclient (2909): * Running script ‘/var/etc/gls2s.include’\n
Sat Jan 6 12:10:33 2024 daemon.notice netifd: ovpnclient (2909): ! Skipping due to path error: No such file or directory\n
Sat Jan 6 12:10:33 2024 daemon.notice netifd: ovpnclient (2909): * Running script ‘/usr/bin/gl_block.sh’\n
Sat Jan 6 12:10:33 2024 daemon.notice netifd: ovpnclient (2909): Failed to parse json data: unexpected character\n
Sat Jan 6 12:10:33 2024 daemon.notice netifd: ovpnclient (2909): uci: Entry not found\n
Sat Jan 6 12:10:33 2024 daemon.notice netifd: ovpnclient (2909): cat: can’t open ‘/tmp/run/ovpn_resolved_ip’: No such file or directory\n

2

Afaik these log lines are normal, none of them indicate an issue.

Do you have an issue?

3

There is “failed to parse json data” and “no such file or directory” error.

There are more errors after the above.

The VPN client keeps trying for over 5 minutes, and never success. Yellow light always on.

4

Yeah, but those lines are normal.

Are you sure you entered the right credentials? There a specific ones for NordVPN - it’s not just your login.

You can view them in the NordVPN control panel.

5

Where do I enter another login, other than the login screen?

I am already logged on and got a list of VPN servers from NordVPN, and there is no authentication error.

sat jan 6 12:40:06 2024 daemon.warn ovpnclient[23311]: WARNING: --ping should normally be used with --ping-restart or --ping-exit\n
sat jan 6 12:40:06 2024 daemon.warn ovpnclient[23311]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts\n
sat jan 6 12:40:06 2024 daemon.notice ovpnclient[23311]: Outgoing Control Channel Authentication: Using 512 bit message hash ‘SHA512’ for HMAC authentication\n
sat jan 6 12:40:06 2024 daemon.notice ovpnclient[23311]: Incoming Control Channel Authentication: Using 512 bit message hash ‘SHA512’ for HMAC authentication\n
sat jan 6 12:40:06 2024 daemon.notice ovpnclient[23311]: TCP/UDP: Preserving recently used remote address: [AF_INET]185.153.179.110:1194\n
sat jan 6 12:40:06 2024 daemon.notice ovpnclient[23311]: Socket Buffers: R=[212992->212992] S=[212992->212992]\n
sat jan 6 12:40:06 2024 daemon.notice ovpnclient[23311]: UDP link local: (not bound)\n
sat jan 6 12:40:06 2024 daemon.notice ovpnclient[23311]: UDP link remote: [AF_INET]185.153.179.110:1194\n
sat jan 6 12:40:06 2024 daemon.notice ovpnclient[23311]: TLS: Initial packet from [AF_INET]185.153.179.110:1194, sid=a61ebfcb 33b24723\n
sat jan 6 12:40:06 2024 daemon.notice ovpnclient[23311]: VERIFY OK: depth=2, C=PA, O=NordVPN, CN=NordVPN Root CA\n
sat jan 6 12:40:06 2024 daemon.notice ovpnclient[23311]: VERIFY OK: depth=1, O=NordVPN, CN=NordVPN CA8\n
sat jan 6 12:40:06 2024 daemon.notice ovpnclient[23311]: VERIFY KU OK\n
sat jan 6 12:40:06 2024 daemon.notice ovpnclient[23311]: Validating certificate extended key usage\n
sat jan 6 12:40:06 2024 daemon.notice ovpnclient[23311]: ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication\n
sat jan 6 12:40:06 2024 daemon.notice ovpnclient[23311]: VERIFY EKU OK\n
sat jan 6 12:40:06 2024 daemon.notice ovpnclient[23311]: VERIFY X509NAME OK: CN=ca1571.nordvpn.com\n
sat jan 6 12:40:06 2024 daemon.notice ovpnclient[23311]: VERIFY OK: depth=0, CN=ca1571.nordvpn.com\n
sat jan 6 12:40:07 2024 daemon.notice ovpnclient[23311]: Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, peer certificate: 4096 bit RSA, signature: RSA-SHA512\n
sat jan 6 12:40:07 2024 daemon.notice ovpnclient[23311]: [] Peer Connection Initiated with [AF_INET]185.153.179.110:1194\n
sat jan 6 12:40:08 2024 daemon.notice ovpnclient[23311]: SENT CONTROL []: ‘PUSH_REQUEST’ (status=1)\n

6

I guess you are successfully connected now ?

7

No, still showing “The client is starting, please wait…”

8

The log is fine. The “failed to parse json data” is generally because no vpn policy is set up. Not a problem.

The reason that you cannot connect to Nord is generally that the server has problems or your network is blocking.

1 Like
9

Oh I figured it out! I contacted NordVPN and they told me I have to use special token to connect instead of my NordVPN ID. It’s working as expected now! Thanks

1 Like
10

:expressionless:

:smile:

1 Like
11

Didn’t know that as a newbee, sorry :rofl:

1 Like
12

Guess it’s NordVPN. Why don’t they show it in your dashboard like “HEY. LISTEN. YOU NEED THESE CREDENTIALS FOR LOGIN” - but yeah… guess why… it’s Nord.

13

But in that case, the log ususally show “Auth-failed”.

Not sure why is does not display.