We have a new RUT956 router and we are able to get it to talk to the RMS server. We have created a new device in RMS and have 12 credits to our disposal, We have connection to internet with the router but are not able to get it to connect to RMS.
Hello,
When you register a device to RMS, you should see it listed on the main RMS page. Next to the newly registered device, there should be a colored dot (gray or another color). Could you please move your mouse over that dot and let me know the status of the newly registered device?
Additionally, please log in to the device via WebUI, navigate to Services → Cloud Solutions → RMS, and let me know what is displayed next to “Connection state.”
From the same page, you can also click the “Connect” button to initiate the device’s connection to RMS manually.
Best regards,
This did not resolve the issue.
Hello,
Could you please provide this information:
Best regards,
root@RUT956:~# openssl s_client -connect rms.teltonika-networks.com:15009 </dev/null
4CBDE777:error:10080002:lib(32):BIO_lookup_ex:reason(524290):crypto/bio/bio_addr.c:738:Try again
connect:errno=22
I ran this line for testing: openssl s_client -connect 3.69.112.66:15009 </dev/null
But the error response is too long and it will not let me post it on this site.
Marija,
From what I can tell, the server is rejecting the certificates that are being sent from the RUT956. I confirm that I am able to get the RUT956 to communicate to the server.
How can I get updated certificates for the RUT956?
root@rms:~# openssl s_client -connect rms.teltonika-networks.com:15010 </dev/null 4C7DE577:error:80000092:lib(2):BIO_connect:reason(146):crypto/bio/bio_sock2.c:114:calling connect() 4C7DE577:error:10000067:lib(32):BIO_connect:reason(103):crypto/bio/bio_sock2.c:116: 4C7DE577:error:80000092:lib(2):BIO_connect:reason(146):crypto/bio/bio_sock2.c:114:calling connect() 4C7DE577:error:10000067:lib(32):BIO_connect:reason(103):crypto/bio/bio_sock2.c:116: connect:errno=146
Hello,
For troubleshooting purposes, we will require more sensitive information from your end, such as the troubleshoot file, which may contain passwords, public IP addresses, serial numbers, and such. To avoid leaking this information, we have sent you a form to fill out, which you will receive in your e-mail inbox that you have registered your account with in the forums. In the **Ticket ID** field of the form, please enter the ID of this thread, which is **16112**.
Thank you,
Hello,
I want to write a brief status update: the connection to RMS server was resolved after changing the DNS settings on the wired WAN interface.
Best regards,
Eimantas