CLI option does not work for RUTX50

Hello,

In RUTX50 gui page, CLI from System - Maintenance - CLI does not work if https is used to access the admin page. It shows an empty box. Actually it has never worked with https for as long as I had the RUTX50. Are there any settings that I need to have in place for CLI to work with https?

You need to have a valid trusted SSL certificate. If you ignore the SSL certificate warning, CLI is not going to work.

Can you please give some more details? So RUTX50 needs a valid cert that the browser trusts?

The device you are connecting from needs to trust the certificate of the RUTX. This can be achieved in multiple ways. For example if you have a public IP address you could setup DDNS and use let’s encrypt service (or any other SSL provider) to generate a trusted SSL certificate that will be accepted by every device. Tutorial for this method can be found here Eliminating HTTPS Warnings: Using Let's Encrypt - Teltonika Networks Wiki

Or you could self generate your own certificates and make your devices trust them. There is a tutorial for this here Removing HTTPS Warnings with Device-Generated Certificates - Teltonika Networks Wiki

Great! Thank you

1 Like

Here’s the ‘Bluffer’s Guide’ …



You can then export the CA certificate to your Windows PC by navigating the menu structure to SYSTEM > ADMINISTRATION > CERTIFICATES > CERTIFICATE MANAGER > CERTIFICATES and against ‘ca.cert.pem’ select ‘Export’.

Then import the certificate into your OS / Browser e.g. for Windows …

In the ‘Windows Search Box’, bottom-left of screen, search for ‘manage computer certificates’ and open the Control Panel ‘certlm’.

Select ‘Certificates’ under Local Computer > Trusted Root Certification Authorities, and go through the process of importing.

NOTES
Backup your certificates as they do not persist after a Factory Reset. After a Factory reset, the only certificate that is instated is the default ca-certificates.crt. You will need to import them, back into the RUTX, via Certificates Manager.

Also note that should you change your IP’s to different subnets, you will need to regenerate the certificates, if using on a LAN or a LAN extended via VPN.

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.