RUTM52 not connecting to RMS

Dear Teltonika,

I was guided here on the phone by one of your customer services helpdesk people.

I bought a RUTM52 a few weeks ago, installed a sim and established a network. This all went well, and I have been able to connect to the internet ever since. I have two devices on the network – a Swann camera system and a Victron energy system. I can access both remotely. The RUTM52 was able to connect to the RMS with the month free period and I was able to monitor remotely. I decided to purchase a 10 year package from Capestone, assigned this to the router, and at that point the RUTM52 was no-longer able to connect to RMS. Whenever I pressed the “Connect” button on the Cloud solutions-RMS page it would say “Connection attempt intiated” but would never connect and the “Connection state” was always “Down (other error)”. I have communicated quite a bit with Capestone and tried various bits of troubleshooting such as removing and re-adding my device to the online internet RMS page but this did not change things. Eventually I decided to do a factory reset. This changed things a little, in that when I now click the local UI “Connect” button, it says “New connection initiation attempt was successful”. The connection status briefly switches to “connected” but the goes to “reconnecting” and then after a few seconds “down” again.

When I look at the online RMS logs for the device, I see a long list of “Authentication was success. Waiting for reconnection…” but it never achieves a connection.

Please help!

Many thanks,

Simon

As an update - about six hours after posting this, the device connected. So am not sure if Teltonika fixed something, or whether doing the factory reset sorted things, which took a while to propagate through the system. So now I wish I new why it started working, as well as wanting to know why it stopped working. I guess I’ll never know…

Hello,

I’m glad to hear that the device is now connected to RMS and the issue is resolved. Unfortunately, to determine the root cause, we would have needed to troubleshoot the device while it was in the disconnected state, so at this point, it is difficult to say what caused the issue.

If you experience the same issue again, please feel free to reach out on the community forum, and we will be happy to help you troubleshoot it.

We appreciate your understanding.

Best regards,

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