Hello
I’ve been using the RMS VPN service for more than a year since it was introduced at a real estate company.
There was one issue with it at the start where I had to re-create the whole HUB after a couple of months due to changes in the RMS VPN service from Teltonika, but other than that it has worked great, up until now.
The RMS VPN is dead after the new year.
There has been no change whatsoever in the environment with the customers RMS VPN and when I’m logging in to the HUB router I find that the Open VPN configuration lists this as an error;
Thu Jan 9 12:54:21 2025 daemon.notice openvpn(rms_Tu2oYns7uoKbWxAh)[5857]: TCP/UDP: Preserving recently used remote address: [AF_INET]x.x.x.x:34773
Thu Jan 9 12:54:21 2025 daemon.notice openvpn(rms_Tu2oYns7uoKbWxAh)[5857]: UDP link local: (not bound)
Thu Jan 9 12:54:21 2025 daemon.notice openvpn(rms_Tu2oYns7uoKbWxAh)[5857]: UDP link remote: [AF_INET]3.69.106.81:34773
Thu Jan 9 12:55:21 2025 daemon.err openvpn(rms_Tu2oYns7uoKbWxAh)[5857]: TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Thu Jan 9 12:55:21 2025 daemon.err openvpn(rms_Tu2oYns7uoKbWxAh)[5857]: TLS Error: TLS handshake failed
Thu Jan 9 12:55:21 2025 daemon.notice openvpn(rms_Tu2oYns7uoKbWxAh)[5857]: SIGUSR1[soft,tls-error] received, process restarting
Thu Jan 9 12:55:26 2025 daemon.warn openvpn(rms_Tu2oYns7uoKbWxAh)[5857]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Thu Jan 9 12:55:27 2025 daemon.warn openvpn(rms_Tu2oYns7uoKbWxAh)[5857]: WARNING: Your certificate has expired!
Since these tunnels were configured automatically with the Teltonika RMS VPN HUB setup, I wonder how I can solve it without needing to remove the whole HUB and start over again.
And, If I once again have to remove it, how can you at Teltonika prevent it from happening every 12 months if these certificates expire?
I would prefer that the service be consistent and functional year after year.