Mario Vale

This is what they said, they are unable to support it. Does the latest test firmware support OVPN 2.4?

I'll get right on that, I think I saw a bit saying to contact them if there are issues connecting, was just hoping it was me doing something stupid on the router and not a deeper issue.

These are the only files I know of https://nordvpn.com/ovpn/

Yes I tried a few different ones with both UDP and TCP and nothing worked. Yes, these are the credentials.

I thought I provided it in the initial post, but it doesn't appear to be there. I have attached the ovpn being used to connect. This is the current Log shown in Hybrid VPN Wed Jun 2 07:25:56 2021 OpenVPN 2.3.4 mips-openwrt-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [MH] [IPv6] built on Nov 4 2018 Wed Jun 2 07:25:56 2021 library versions: OpenSSL 1.0.1h 5 Jun 2014, LZO 2.06 Wed Jun 2 07:25:56 2021 WARNING: --ping should normally be used with --ping-restart or --ping-exit Wed Jun 2 07:25:56 2021 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Wed Jun 2 07:25:56 2021 Control Channel Authentication: tls-auth using INLINE static key file Wed Jun 2 07:25:56 2021 Outgoing Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication Wed Jun 2 07:25:56 2021 Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication Wed Jun 2 07:25:56 2021 Socket Buffers: R=[163840->131072] S=[163840->131072] Wed Jun 2 07:25:56 2021 UDPv4 link local: [undef] Wed Jun 2 07:25:56 2021 UDPv4 link remote: [AF_INET]194.35.233.51:1194 Wed Jun 2 07:25:56 2021 TLS: Initial packet from [AF_INET]194.35.233.51:1194, sid=2fd9315d 79ce13d3 Wed Jun 2 07:25:56 2021 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this Wed Jun 2 07:26:56 2021 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity) Wed Jun 2 07:26:56 2021 TLS Error: TLS handshake failed Wed Jun 2 07:26:56 2021 SIGUSR1[soft,tls-error] received, process restarting Wed Jun 2 07:26:56 2021 Restart pause, 2 second(s) Wed Jun 2 07:26:58 2021 WARNING: --ping should normally be used with --ping-restart or --ping-exit Wed Jun 2 07:26:58 2021 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Wed Jun 2 07:26:58 2021 Socket Buffers: R=[163840->131072] S=[163840->131072] Wed Jun 2 07:26:58 2021 UDPv4 link local: [undef] Wed Jun 2 07:26:58 2021 UDPv4 link remote: [AF_INET]194.35.233.51:1194 Wed Jun 2 07:26:58 2021 TLS: Initial packet from [AF_INET]194.35.233.51:1194, sid=abec0f10 48ed8cbf uk2091.nordvpn.com.udp1194.ovpn

All it ever says is "Status" "connecting" and yes the credentials are correct, they are copied directly from the Nord VPN configuration page.

I'm trying to connect to Nord VPN for the first time and it doesn't want to connect. I am on Firmware version R1 2.1.3.29. This is the log shown on the VPN page Mon May 31 19:37:31 2021 OpenVPN 2.3.4 mips-openwrt-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [MH] [IPv6] built on Nov 4 2018 Mon May 31 19:37:31 2021 library versions: OpenSSL 1.0.1h 5 Jun 2014, LZO 2.06 Mon May 31 19:37:31 2021 WARNING: --ping should normally be used with --ping-restart or --ping-exit Mon May 31 19:37:31 2021 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Mon May 31 19:37:31 2021 Control Channel Authentication: tls-auth using INLINE static key file Mon May 31 19:37:31 2021 Outgoing Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication Mon May 31 19:37:31 2021 Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication Mon May 31 19:37:31 2021 Socket Buffers: R=[163840->131072] S=[163840->131072] Mon May 31 19:37:31 2021 UDPv4 link local: [undef] Mon May 31 19:37:31 2021 UDPv4 link remote: [AF_INET]194.35.233.51:1194 Mon May 31 19:37:31 2021 TLS: Initial packet from [AF_INET]194.35.233.51:1194, sid=b0ac8bf9 e0cc872f Mon May 31 19:37:31 2021 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this Mon May 31 19:38:31 2021 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity) Mon May 31 19:38:31 2021 TLS Error: TLS handshake failed Mon May 31 19:38:31 2021 SIGUSR1[soft,tls-error] received, process restarting Mon May 31 19:38:31 2021 Restart pause, 2 second(s) Mon May 31 19:38:33 2021 WARNING: --ping should normally be used with --ping-restart or --ping-exit Mon May 31 19:38:33 2021 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Mon May 31 19:38:33 2021 Socket Buffers: R=[163840->131072] S=[163840->131072] Mon May 31 19:38:33 2021 UDPv4 link local: [undef] Mon May 31 19:38:33 2021 UDPv4 link remote: [AF_INET]194.35.233.51:1194 Mon May 31 19:38:33 2021 TLS: Initial packet from [AF_INET]194.35.233.51:1194, sid=c7dc19f0 2936e08a Mon May 31 19:39:33 2021 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity) Mon May 31 19:39:33 2021 TLS Error: TLS handshake failed Mon May 31 19:39:33 2021 SIGUSR1[soft,tls-error] received, process restarting Mon May 31 19:39:33 2021 Restart pause, 2 second(s) Mon May 31 19:39:35 2021 WARNING: --ping should normally be used with --ping-restart or --ping-exit Mon May 31 19:39:35 2021 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Mon May 31 19:39:35 2021 Socket Buffers: R=[163840->131072] S=[163840->131072] Mon May 31 19:39:35 2021 UDPv4 link local: [undef] Mon May 31 19:39:35 2021 UDPv4 link remote: [AF_INET]194.35.233.51:1194 Mon May 31 19:39:35 2021 TLS: Initial packet from [AF_INET]194.35.233.51:1194, sid=40fd7192 492067a1 Mon May 31 19:40:35 2021 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity) Mon May 31 19:40:35 2021 TLS Error: TLS handshake failed Mon May 31 19:40:35 2021 SIGUSR1[soft,tls-error] received, process restarting Mon May 31 19:40:35 2021 Restart pause, 2 second(s) Mon May 31 19:40:37 2021 WARNING: --ping should normally be used with --ping-restart or --ping-exit Mon May 31 19:40:37 2021 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Mon May 31 19:40:37 2021 Socket Buffers: R=[163840->131072] S=[163840->131072] Mon May 31 19:40:37 2021 UDPv4 link local: [undef] Mon May 31 19:40:37 2021 UDPv4 link remote: [AF_INET]194.35.233.51:1194 Mon May 31 19:40:37 2021 TLS: Initial packet from [AF_INET]194.35.233.51:1194, sid=41bb860b 493954d9 This is the configuration for uk2091.nordvpn.com I have also tried TCP as well as other server regions, but none of them will connect.

I have yet to see an error code since I installed the new modem, so please close this issue!

I purchased the DrayTek Vigor 130 and I've been testing my connection with it since Saturday. So far it has yet to fail with an error code and the ping monitor graph I have has been impeccable. I guess the modem in the Nighthawk is way better than the cheap Netgear modem I bought to use with the Netduma. I will keep testing for a bit, but based on my current results I don't think I will see an error code again (unless it is Bungie's fault like earlier tonight).

Yes, I'm still getting error codes, especially in the Tower / social spaces, so I think I will have to do an experiment and either use the Nighthawk as the modem or buy a better quality modem. Anyone know of any good quality VDSL modems?

Thanks for checking the configuration Chive, I'll test it this week and a lot more this weekend. Any reason for adding 443 TCP as hypertraffic but not port forwarding it?

Yes, I believe it is a problem with the modem, as restarting that only usually resolves the issues. I just need to figure out what to do, perhaps it needs re-configuring before putting it into modem mode, however I didn't think any settings applied before putting it into modem mode would actually remain when in modem mode.

Yes, that is correct. I am not using it most of the time because I fear it will cause more error codes until I figure out why this happens. Before playing tonight I hard reset the modem, Netduma and console to ensure the best connection and I was able to play for about 4 hours tonight with no issues and no error codes in the Tower (was there for about 10-20 minutes).

Just logged in for the first time today (didn't reboot the modem or Netduma), went to the Tower and got error code beetle, which kicked me to orbit and gave me error code bee. I'm trying to go to the Tower again to see what else happens. I did get error code bee again, but now I'm in the Tower, so I shall see how long I can remain in there!

Yes, I've sent you the details.