After updating my Teltonika RUTX50 router to firmware version RUTX_R_00.07.14.2, released on May 9, 2025, the device experiences a critical problem: every few minutes it loses recognition of the inserted SIM card, causing temporary mobile connectivity interruptions.
I have tested the SIM card on other devices without any issues and performed all standard troubleshooting steps, including router reboot. However, the problem persists and severely affects connection stability.
During these interruptions, I am unable to access the router management interface to review logs or gather further diagnostics.
This firmware version is recent and has been withdrawn due to critical issues, but previous firmware versions are no longer publicly available for downgrade.
I’ve sent you a form to fill out so we can continue the conversation in private, as I will need a troubleshooting file from the device in order to pass it to our R&D for analysis.
In the “ticket ID” field, please enter the thread number 13845
I have a similar experience .
From the event log: “Mobile data disconnected (internal modem)”
I get this every 20-30 minutes, and it takes quite some time to reconnect.
I downgraded firmware to 7.12.3, which seems to have resolved the issue.
I’ve sent you both instructions as well, in the ticket ID, enter the same ID of this thread, which is 13845, and we’ll continue communication from there. As it looks like this issue is repeated for more than one user, we will have to analyse this via the troubleshooting files from your devices. Once you fill out the form, I’ll reach out to both of you.
in the end I also opted for a downgrade to that version. The latest is unstable, by installing the old version my RUTX50 started working correctly again, when I was contacted by phone this morning by support I limited myself to asking for the possible release date of a fix, I await an answer.
Just checking in once again - I’ve sent all 3 of you a form to fill out so we can continue communicating through e-mails. To be specific, we would need all three of your troubleshooting files from the Teltonika devices while the issue is present so we would be able to analyse said files to see what is really happening. You can generate a troubleshooting file under System → Maintenance → Troubleshoot
Once again, the ticket ID should be the same as the thread ID, which is 13845 - will be waiting for you guys!
Hello,
we have a similar problem. We use the TRB255/TRB256 devices, and the error also appears occasionally (SIM not inserted in the logs). The device is no longer registered for a few days or weeks. Then the problem resolves itself, and it works as before. The problem is that the devices are installed at customers, so we can’t establish physical contact with the device, and reading the logs isn’t that easy.
Have you found a solution or the cause of the problem?
Could you possibly share the information here as well.
Unfortunately, none of the three users have filled the form out, so no further communication has been done regarding the issue. If you’d like to contribute to this, I’ve sent you the form as well, in the Ticket ID section, enter the ID of the thread, which is 13845.
Make sure to generate a troubleshooting file while the issue is active, and make sure that you haven’t restarted the device so the logs stay in place. Once you fill the form out, I’ll reach out to you via e-mail and request for the file.
Hello,
thanks for the reply. Unfortunately, no device is currently displaying this error, and it’s not easy to get the logs since the devices are then no longer accessible from outside. I’ve already opened a Support ticket for this issue ID:#465645. I wanted to ask if this problem has been resolved for others or if others are also unable to get detailed logs. (Since the error isn’t occurring at the moment) However, we can’t guarantee that the problem won’t recur after a while.
I see, since you have a ticket in our ticketing system directly (I assume you’re a direct client), I guess we’ll have to wait and monitor the responsible engineers + R&D findings and see what the resolution is. I’ll make sure to keep an eye out and update anyone and everyone once I have any information.
Hello,
thanks Matas for helping us with this issue and looking up for information. The devices can be different, and the causes may also be different, but the errors are described in a way that applies to our case as well. I have another thread that’s already closed (“13128”). Perhaps there’s an answer to the cause there. It would be nice if there was information on how the error was resolved. Are the information also shared in the tread if the Tickets are created and solved?
Thank you for any information helping to sove this issue.
Checked through, and it looks like the issue was that there was no custom APN set, although it was required for the user to do so, and they were also running an older firmware version. After updating both the firmware, and changing the APN to a custom one that’s required by the operator, the connection looks to be stable, although the user is still monitoring it.