DUX50 with mobile connection issue

[kamcio]

Dear Community,

I’m having an issue with my DUX50 and its mobile connection. I’m not sure whether the problem is related to the hardware or the location where I’m currently using it.
The modem frequently loses connection — please see the attached log.

Can you help me resolve the problem?

Thank You in advance,
kamil

|2025-07-22 01:00:08|WiFi|connections|notice|Luisa II: WiFi client connected: 60:F8:1D:B5:CB:7C|
| — | — | — | — | — |
|2025-07-22 01:00:09|DHCP|network|info|Leased 192.168.1.111 IP address for client 60:f8:1d:b5:cb:7c - Kamils-MBP-2 in WiFi|
|2025-07-22 06:47:23|Mobile Data|network|info|Mobile data disconnected (internal modem)|
|2025-07-22 06:47:25|Mobile Data|network|info|Mobile data disconnected (internal modem)|
|2025-07-22 06:47:55|Mobile Data|network|info|Mobile data disconnected (internal modem)|
|2025-07-22 06:48:00|Health checker|network|notice|IPv4 connectivity started to fail|
|2025-07-22 06:48:21|Health checker|network|notice|DNS resolution started to fail|
|2025-07-22 06:48:42|Mobile Data|network|info|Mobile data connected (internal modem)|
|2025-07-22 06:48:42|Network Type|network|info|Joined 5G-NSA network (internal modem)|
|2025-07-22 06:48:42|Network Operator|network|info|Connected to 26002 operator (internal modem)|
|2025-07-22 06:49:21|Health checker|network|notice|IPv4 connectivity restored|
|2025-07-22 06:49:24|Health checker|network|notice|DNS resolution restored|
|2025-07-22 07:01:45|Mobile Data|network|info|Mobile data disconnected (internal modem)|
|2025-07-22 07:02:01|Health checker|network|notice|IPv4 connectivity started to fail|
|2025-07-22 07:02:03|Mobile Data|network|info|Mobile data disconnected (internal modem)|
|2025-07-22 07:02:22|Health checker|network|notice|DNS resolution started to fail|
|2025-07-22 07:02:43|Mobile Data|network|info|Mobile data connected (internal modem)|
|2025-07-22 07:02:43|Network Type|network|info|Joined 5G-NSA network (internal modem)|
|2025-07-22 07:02:43|Network Operator|network|info|Connected to 26002 operator (internal modem)|
|2025-07-22 07:03:22|Health checker|network|notice|IPv4 connectivity restored|
|2025-07-22 07:03:26|Health checker|network|notice|DNS resolution restored|
|2025-07-22 07:16:32|Mobile Data|network|info|Mobile data disconnected (internal modem)|
|2025-07-22 07:16:34|Mobile Data|network|info|Mobile data disconnected (internal modem)|
|2025-07-22 07:16:52|Mobile Data|network|info|Mobile data disconnected (internal modem)|
|2025-07-22 07:17:06|Health checker|network|notice|IPv4 connectivity started to fail|
|2025-07-22 07:17:27|Health checker|network|notice|DNS resolution started to fail|
|2025-07-22 07:18:42|Health checker|network|notice|DNS resolution restored|
|2025-07-22 07:18:46|Mobile Data|network|info|Mobile data connected (internal modem)|
|2025-07-22 07:18:46|Network Type|network|info|Joined 5G-NSA network (internal modem)|
|2025-07-22 07:18:46|Network Operator|network|info|Connected to 26002 operator (internal modem)|
|2025-07-22 07:19:42|Health checker|network|notice|IPv4 connectivity restored|
|2025-07-22 07:22:47|Mobile Data|network|info|Mobile data disconnected (internal modem)|
|2025-07-22 07:22:49|Mobile Data|network|info|Mobile data disconnected (internal modem)|
|2025-07-22 07:22:54|Health checker|network|notice|IPv4 connectivity started to fail|
|2025-07-22 07:23:06|Mobile Data|network|info|Mobile data disconnected (internal modem)|
|2025-07-22 07:23:15|Health checker|network|notice|DNS resolution started to fail|
|2025-07-22 07:23:54|Mobile Data|network|info|Mobile data connected (internal modem)|
|2025-07-22 07:23:54|Network Type|network|info|Joined 5G-NSA network (internal modem)|
|2025-07-22 07:23:54|Network Operator|network|info|Connected to 26002 operator (internal modem)|
|2025-07-22 07:24:15|Health checker|network|notice|IPv4 connectivity restored|
|2025-07-22 07:24:18|Health checker|network|notice|DNS resolution restored|
|2025-07-22 07:28:07|Mobile Data|network|info|Mobile data disconnected (internal modem)|
|2025-07-22 07:28:09|Mobile Data|network|info|Mobile data disconnected (internal modem)|
|2025-07-22 07:28:31|Health checker|network|notice|IPv4 connectivity started to fail|
|2025-07-22 07:28:38|Mobile Data|network|info|Mobile data disconnected (internal modem)|
|2025-07-22 07:28:52|Health checker|network|notice|DNS resolution started to fail|
|2025-07-22 07:31:34|Health checker|network|notice|DNS resolution restored|
|2025-07-22 07:31:38|Mobile Data|network|info|Mobile data connected (internal modem)|
|2025-07-22 07:31:38|Network Type|network|info|Joined 5G-NSA network (internal modem)|
|2025-07-22 07:31:38|Network Operator|network|info|Connected to 26002 operator (internal modem)|
|2025-07-22 07:32:34|Health checker|network|notice|IPv4 connectivity restored|
|2025-07-22 07:47:04|Mobile Data|network|info|Mobile data disconnected (internal modem)|
|2025-07-22 07:47:06|Mobile Data|network|info|Mobile data disconnected (internal modem)|
|2025-07-22 07:47:21|Health checker|network|notice|IPv4 connectivity started to fail|
|2025-07-22 07:47:23|Mobile Data|network|info|Mobile data disconnected (internal modem)|
|2025-07-22 07:47:42|Health checker|network|notice|DNS resolution started to fail|
|2025-07-22 07:48:03|Mobile Data|network|info|Mobile data connected (internal modem)|
|2025-07-22 07:48:03|Network Type|network|info|Joined 5G-NSA network (internal modem)|
|2025-07-22 07:48:03|Network Operator|network|info|Connected to 26002 operator (internal modem)|
|2025-07-22 07:48:42|Health checker|network|notice|IPv4 connectivity restored|
|2025-07-22 07:48:45|Health checker|network|notice|DNS resolution restored|
|2025-07-22 08:46:24|Mobile Data|network|info|Mobile data disconnected (internal modem)|
|2025-07-22 08:46:26|Mobile Data|network|info|Mobile data disconnected (internal modem)|
|2025-07-22 08:46:45|Mobile Data|network|info|Mobile data disconnected (internal modem)|
|2025-07-22 08:46:49|Health checker|network|notice|IPv4 connectivity started to fail|
|2025-07-22 08:47:10|Health checker|network|notice|DNS resolution started to fail|
|2025-07-22 08:47:33|Mobile Data|network|info|Mobile data connected (internal modem)|
|2025-07-22 08:47:33|Network Type|network|info|Joined 5G-NSA network (internal modem)|
|2025-07-22 08:47:33|Network Operator|network|info|Connected to 26002 operator (internal modem)|
|2025-07-22 08:48:10|Health checker|network|notice|IPv4 connectivity restored|
|2025-07-22 08:48:13|Health checker|network|notice|DNS resolution restored|
|2025-07-22 09:12:37|Mobile Data|network|info|Mobile data disconnected (internal modem)|
|2025-07-22 09:12:57|Mobile Data|network|info|Mobile data connected (internal modem)|
|2025-07-22 09:12:57|Network Type|network|info|Joined 5G-NSA network (internal modem)|
|2025-07-22 09:12:57|Network Operator|network|info|Connected to 26002 operator (internal modem)|
|2025-07-22 09:33:24|WiFi|connections|notice|Luisa II: WiFi client connected: 16:BC:FF:8E:C8:D6|
|2025-07-22 09:37:47|Web UI|connections|notice|User “admin” successfully authenticated on HTTP from 192.168.1.146 to 192.168.1.1|
|2025-07-22 09:39:05|WiFi|connections|notice|Luisa II: WiFi client connected: CC:D4:2E:D2:94:4C|
|2025-07-22 09:39:13|DHCP|network|info|Leased 192.168.1.152 IP address for client cc:d4:2e:d2:94:4c - LGwebOSTV in WiFi|
|2025-07-22 09:39:27|Mobile Data|network|info|Mobile data disconnected (internal modem)|
|2025-07-22 09:39:46|Health checker|network|notice|IPv4 connectivity started to fail|
|2025-07-22 09:39:48|Mobile Data|network|info|Mobile data disconnected (internal modem)|
|2025-07-22 09:40:07|Health checker|network|notice|DNS resolution started to fail|
|2025-07-22 09:40:36|Mobile Data|network|info|Mobile data connected (internal modem)|
|2025-07-22 09:40:36|Network Type|network|info|Joined 5G-NSA network (internal modem)|
|2025-07-22 09:40:36|Network Operator|network|info|Connected to 26002 operator (internal modem)|
|2025-07-22 09:41:07|Health checker|network|notice|IPv4 connectivity restored|
|2025-07-22 09:41:10|Health checker|network|notice|DNS resolution restored|

[Matas]

Hello,

A few notable things I’d like to know are:

1. Who’s the provider & what country are you based in? (If you’re comfortable sharing this information.)
2. What’s the firmware of the device? If not the latest, could you try upgrading to 7.16.1? The firmware download page can be found here: RUTX50 Firmware Downloads - Teltonika Networks Wiki
3. What’s the environment that the device is being used in & what is the use case?
4. What signal strengths are you getting? This can be checked under Status → Network → Mobile
5. Try following the instructions from this response: RUT240 Mobile connection drops every 2 hours - #12 by Marija

Regards,
M.

[kamcio]

Hello M,

Thank you for your quick response.

1. I’m currently using T-Mobile Poland in SIM slot 2. SIM slot 1 has a 1&1 card from Germany, but I don’t use it while in Poland.

2. Since yesterday evening, the device is running the latest firmware, but I haven’t noticed any difference compared to the previous version.

3. The device is placed on the windowsill.

4. Please see the attachments. Also screenshots after lose the connection.
   

   
   
   
   
   
   
   
   
   
   

5. Okay, I’ll try to do that.

EDIT: I tried the solution for the RUT240 and added the configuration line to the second SIM card (which is the one I actually use). Unfortunately, the issue still persists.

Best regards,
kamil

[kamcio]

Update.
The RUTX50 lose once again the connection. After about 10 minutes I logged to RUTX50 and I so this:

I don’t understand why should I unlock manually the sim card when the pin code is putted in the configuration. Ok, I have unlocked the sim-card manually and got after some seconds this error (although I didn’t manually rebooted the modem)

[Matas]

Hello,

Looks like the problem is a bit more serious than anticipated. I’ve sent you a form to fill out so we can continue our conversation in private, to avoid accidentally leaking any sensitive information. In the Ticket ID field, simply enter the thread’s number, which is 14759.

Thank you,
M.