[GL-MT3000] Keep connecting to a NordVPN server via OpenVPN client but never success

Hi team,

I would like to use NordVPN with the OpenVPN configuration, which retrieved using my NordVPN credentials in the GL-MT3000’s built-in feature.

However, the client kept connecting to the server but never succeeded. I am wondering what might be the issue. I’ve tried many different endpoints but no luck, and I was able to connect to the servers with the NordVPN Mac client.

Attaching detailed information for your reference.

Thanks in advance and let me know if you need more information.

Nick

System information

Screenshot of the client shows connecting

Full log
Sat Feb 17 22:37:48 2024 daemon.notice netifd: ovpnclient (20061): [!] Section @forwarding[1] is disabled, ignoring section
Sat Feb 17 22:37:48 2024 daemon.notice netifd: ovpnclient (20061): [!] Section wgclient2wan option 'src' specifies invalid value 'wgclient'
Sat Feb 17 22:37:48 2024 daemon.notice netifd: ovpnclient (20061): [!] Section wgclient2wan skipped due to invalid options
Sat Feb 17 22:37:48 2024 daemon.notice netifd: ovpnclient (20061): [!] Section lan2wgclient option 'dest' specifies invalid value 'wgclient'
Sat Feb 17 22:37:48 2024 daemon.notice netifd: ovpnclient (20061): [!] Section lan2wgclient skipped due to invalid options
Sat Feb 17 22:37:48 2024 daemon.notice netifd: ovpnclient (20061): [!] Section guest2wgclient option 'dest' specifies invalid value 'wgclient'
Sat Feb 17 22:37:48 2024 daemon.notice netifd: ovpnclient (20061): [!] Section guest2wgclient skipped due to invalid options
Sat Feb 17 22:37:48 2024 daemon.notice netifd: ovpnclient (20061): [!] Section @include[0] is not marked as compatible with fw4, ignoring section
Sat Feb 17 22:37:48 2024 daemon.notice netifd: ovpnclient (20061): [!] Section @include[0] requires 'option fw4_compatible 1' to be considered compatible
Sat Feb 17 22:37:48 2024 daemon.notice netifd: ovpnclient (20061): [!] Section nat6 option 'reload' is not supported by fw4
Sat Feb 17 22:37:48 2024 daemon.notice netifd: ovpnclient (20061): [!] Section swap_wan_in_conn_mark option 'reload' is not supported by fw4
Sat Feb 17 22:37:48 2024 daemon.notice netifd: ovpnclient (20061): [!] Section vpn_server_policy option 'reload' is not supported by fw4
Sat Feb 17 22:37:48 2024 daemon.notice netifd: ovpnclient (20061): [!] Section gls2s option 'reload' is not supported by fw4
Sat Feb 17 22:37:48 2024 daemon.notice netifd: ovpnclient (20061): [!] Section gls2s specifies unreachable path '/var/etc/gls2s.include', ignoring section
Sat Feb 17 22:37:48 2024 daemon.notice netifd: ovpnclient (20061): [!] Section glblock option 'reload' is not supported by fw4
Sat Feb 17 22:37:48 2024 daemon.notice netifd: ovpnclient (20061): [!] Automatically including '/usr/share/nftables.d/chain-pre/dstnat/00-dhcp-no-flow_offloading.nft'
Sat Feb 17 22:37:48 2024 daemon.notice netifd: ovpnclient (20061): [!] Automatically including '/usr/share/nftables.d/chain-pre/mangle_output/01-process_mark.nft'
Sat Feb 17 22:37:48 2024 daemon.notice netifd: ovpnclient (20061): [!] Automatically including '/usr/share/nftables.d/chain-post/mangle_output/out_conn_mark_restore.nft'
Sat Feb 17 22:37:48 2024 daemon.notice netifd: ovpnclient (20061): Failed to parse json data: unexpected character
Sat Feb 17 22:37:48 2024 daemon.notice netifd: ovpnclient (20061): cat: can't open '/tmp/run/ovpn_resolved_ip': No such file or directory```

The NordVPN OVPN credentials differ from the normal login ones.
You will find them in your NordVPN dashboard.

Are you sure you use the correct ones?


Using NordVPN from countries like China or Iran or some other states that don’t allow VPN won’t work - but I guess you know that?

Hi admon,

Thanks for getting back, yes, I was using the non-email format login credential provided by NordVPN when the login prompt showing up, however, it was just keep connecting (yellow window) without any error. Should I get any error if the credential is incorrect? Please see the attached logs.

Btw, I was using the VPN service from Canada and United States.

Full logs
Sun Feb 18 11:19:44 2024 daemon.notice netifd: ovpnclient (15038): [!] Section @forwarding[1] is disabled, ignoring section
Sun Feb 18 11:19:44 2024 daemon.notice netifd: ovpnclient (15038): [!] Section wgclient2wan option 'src' specifies invalid value 'wgclient'
Sun Feb 18 11:19:44 2024 daemon.notice netifd: ovpnclient (15038): [!] Section wgclient2wan skipped due to invalid options
Sun Feb 18 11:19:44 2024 daemon.notice netifd: ovpnclient (15038): [!] Section lan2wgclient option 'dest' specifies invalid value 'wgclient'
Sun Feb 18 11:19:44 2024 daemon.notice netifd: ovpnclient (15038): [!] Section lan2wgclient skipped due to invalid options
Sun Feb 18 11:19:44 2024 daemon.notice netifd: ovpnclient (15038): [!] Section guest2wgclient option 'dest' specifies invalid value 'wgclient'
Sun Feb 18 11:19:44 2024 daemon.notice netifd: ovpnclient (15038): [!] Section guest2wgclient skipped due to invalid options
Sun Feb 18 11:19:44 2024 daemon.notice netifd: ovpnclient (15038): [!] Section @include[0] is not marked as compatible with fw4, ignoring section
Sun Feb 18 11:19:44 2024 daemon.notice netifd: ovpnclient (15038): [!] Section @include[0] requires 'option fw4_compatible 1' to be considered compatible
Sun Feb 18 11:19:44 2024 daemon.notice netifd: ovpnclient (15038): [!] Section nat6 option 'reload' is not supported by fw4
Sun Feb 18 11:19:44 2024 daemon.notice netifd: ovpnclient (15038): [!] Section swap_wan_in_conn_mark option 'reload' is not supported by fw4
Sun Feb 18 11:19:44 2024 daemon.notice netifd: ovpnclient (15038): [!] Section vpn_server_policy option 'reload' is not supported by fw4
Sun Feb 18 11:19:44 2024 daemon.notice netifd: ovpnclient (15038): [!] Section gls2s option 'reload' is not supported by fw4
Sun Feb 18 11:19:44 2024 daemon.notice netifd: ovpnclient (15038): [!] Section gls2s specifies unreachable path '/var/etc/gls2s.include', ignoring section
Sun Feb 18 11:19:44 2024 daemon.notice netifd: ovpnclient (15038): [!] Section glblock option 'reload' is not supported by fw4
Sun Feb 18 11:19:44 2024 daemon.notice netifd: ovpnclient (15038): [!] Automatically including '/usr/share/nftables.d/chain-pre/dstnat/00-dhcp-no-flow_offloading.nft'
Sun Feb 18 11:19:44 2024 daemon.notice netifd: ovpnclient (15038): [!] Automatically including '/usr/share/nftables.d/chain-pre/mangle_output/01-process_mark.nft'
Sun Feb 18 11:19:44 2024 daemon.notice netifd: ovpnclient (15038): [!] Automatically including '/usr/share/nftables.d/chain-post/mangle_output/out_conn_mark_restore.nft'
Sun Feb 18 11:19:45 2024 daemon.notice netifd: ovpnclient (15038): Failed to parse json data: unexpected character
Sun Feb 18 11:19:45 2024 daemon.notice netifd: ovpnclient (15038): cat: can't open '/tmp/run/ovpn_resolved_ip': No such file or directory

Thanks,
Nick

I am a bit confused because the log says that the openvpn client has issues - but the log line later talks about WireGuard. Might be just some strange log acting here, maybe depening on the firmware.

Are you behind some other router which might block the necessary ports?

Thanks for the prompt reply, I am using the GL-MT3000 in a hotel and I am able to connect to a VPN server by using the Mac client provided by NordVPN. The log was retrieved from the view log link in the client section, please see the screenshot.
Wondering what is the issue from the OpenVPN client? Is there any potential solution for it?

The VPN client stuck in the following state for a long time

Mostly, the clients on PCs (or Mac) will act entirely different - they often use some more obfuscation.
Can’t you try WireGuard for example?

Thanks for replying, I actually tried the WireGuard option with the Surfshark, but have another issue that you also replied.

Wondering if someone from gl.inet could help with the issue or I need to submit a support ticket? Thanks.