Upgraded a test unit and getting “Failed to load OpenVPN status data” popups and the config is showing no ip’s or rx/tx.
I can get to it though.. just a heads up in case anyone was going roll it out.
I will try and debug when I have time 
I ran into the same issue just a moment ago. Updated my RUTX50 from 7.16.1 to 7.18. RUTX50 running a OpenVPN client. After update, the client still works and VPN-tunnel is connected, but the GUI is showing the error “Failed to load OpenVPN status data”. Also the device log shows every few seconds: 998 Thu Oct 2 09:02:30 2025 kern.err /usr/lib/lua/api/services/openvpn: attempt to index a nil value
Hello,
I have reported this issue to our RnD team. As soon as I receive feedback from them, I will let you know.
Thank you for your patience.
Best regards,
1 Like
Here’s the steps I followed, nothing special. I’ll mention that my device has not been factory defaulted in ages. The device is pretty much as old as a RUTX50 can be, but it has been updated regularly and is working just fine. Modem has the newest fw aswell.
My device had a OpenVPN client configured from the GUI (not using config file) and fw 7.16.1 before I updated it. As soon as I updated it to 7.18 and the device had rebooted, I logged in to the GUI and the notification popped up pretty much instantly. If I keep the GUI open, I get the same notification (Failed to load OpenVPN status) frequently.
Hello @AVi,
Thank you for sharing the steps. Could you also specify which authentication method you are using: TLS, TLS/Password, Password, or Static key?
Best regards,
We were on 17.2 and upgraded, OpenVPN config we are using below, obfuscated names and IP:
config openvpn ‘UNIQUENAME’
option keepalive ‘10 120’
option _name ‘UNIQUENAME’
option nobind ‘1’
option dev ‘tun_c_UNIQUENAME’
option status ‘/tmp/openvpn-status_UNIQUENAME.log’
option verb ‘5’
option type ‘client’
option proto ‘udp’
option port ‘1193’
option comp_lzo ‘yes’
option auth_mode ‘tls’
option resolv_retry ‘infinite’
option tls_security ‘none’
option tls_client ‘1’
option client ‘1’
option enable ‘1’
option auth ‘sha1’
option cipher ‘AES-256-CBC’
list data_ciphers ‘AES-256-CBC’
option name ‘UNIQUENAME’
list network ‘11.22.33.0/20’
list remote ‘host.UNIQUENAME.com’
option configuration ‘manual’
list extra ‘persist-key’
option ca ‘/etc/certificates/cbid.openvpn.UNIQUENAME.caca.crt’
option cert ‘/etc/certificates/cbid.openvpn.UNIQUENAME.cert.crt’
option key ‘/etc/certificates/cbid.openvpn.UNIQUENAME.key.key’
We’re using TLS-authentication.
Hello,
Unfortunately, we were not able to replicate the issue, and everything works as expected on our end. To troubleshoot further, we will need some sensitive information from your devices, such as troubleshoot files.
I have sent a form to the email address you used to register on the community forum. Once you fill out the form, we will contact you privately.
For the ticket ID, please use:
Thank you.
Best regards,
Done Marija.
Thansk
Darren
This topic was automatically closed after 60 days. New replies are no longer allowed.