Login WebUI error but ssh login OK

[VincentBlic]

Hello

Like in Can't login to webui, ssh is ok
I’m able to login to my RUT 951 via ssh but not via WebUI
Details :

 Teltonika RUT9M series 2024

---

Device: RUT951
Kernel: 5.15.165
Firmware: RUT9M_R_00.07.10.2
Build: 4d9eec5df81
Build date: 2024-10-30 10:52:42

Also, how do they change the MTU (if it is the solution) in the above mentionned topic ?
Note : the MTU is the same on all my devices, not sure it is the correct solution :
qmimux0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:
inet6 addr:
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1358 Metric:1
RX packets:117286 errors:0 dropped:0 overruns:0 frame:0
TX packets:136593 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:54415130 (51.8 MiB) TX bytes:25012979 (23.8 MiB)

Thanks and BR

[Marcelo.Barros]

Hi…

Can you try this? To change the mtu, using cli commands?

Error in system log: daemon uhttpd vuci: accepted login for admin from <ip>

Hello, The issue sounds like it could be related to the MTU size. I’ll ask you to log into the CLI of the device, and run the following commands: uci set network.[tunnel_name].mtu='1300' uci commit network /etc/init.d/network restart Replace the [tunnel_name] with the name of the WireGuard instance on the RUTX11. After restarting the network, the connection will be lost, but it will recover soon. Keep in mind, that this MTU only applies to the WireGuard tunnel, if you are experiencing issue…

Maybe you can try… Sample

network.mob1s1a1.mtu=‘1300’ or network.wan.mtu=‘1300’ …

[VincentBlic]

@Marcelo.Barros

network.mob1s1a1.mtu=‘1300’ or network.wan.mtu=‘1300’ …

Hi thanks @Marcelo.Barros
As this is on a distant machine (+500km), I don’t want to break anything
Any risk to set this option, even if I don’t see it running the following command ?
uci show network

Result :

network.loopback=interface
network.loopback.device='lo'
network.loopback.proto='static'
network.loopback.ipaddr='127.0.0.1'
network.loopback.netmask='255.0.0.0'
network.loopback._area_type='lan'
network.loopback.area_type='lan'
network.relayd=interface
network.relayd.disabled='1'
network.relayd.proto='relay'
network.relayd._area_type='wan'
network.relayd.area_type='wan'
network.globals=globals
network.globals.ula_prefix='fd72:1a2d:3daa::/48'
network._lan0=port
network._lan0.enabled='1'
network._lan0.autoneg='on'
network._lan0.role='lan'
network._lan0.port_num='0'
network._lan1=port
network._lan1.enabled='1'
network._lan1.autoneg='on'
network._lan1.role='lan'
network._lan1.port_num='1'
network._lan2=port
network._lan2.enabled='1'
network._lan2.autoneg='on'
network._lan2.role='lan'
network._lan2.port_num='2'
network._wan4=port
network._wan4.enabled='1'
network._wan4.autoneg='on'
network._wan4.role='wan'
network._wan4.port_num='4'
network.br_lan=device
network.br_lan.name='br-lan'
network.br_lan.type='bridge'
network.br_lan.ports='eth0.1'
network.br_lan.stp='0'
network.lan=interface
network.lan.device='br-lan'
network.lan._area_type='lan'
network.lan.proto='static'
network.lan.ipaddr='192.168.1.1'
network.lan.netmask='255.255.255.0'
network.lan.ip6assign='60'
network.lan.igmp_snooping='0'
network.lan.force_link='1'
network.lan.delegate='1'
network.lan.area_type='lan'
network.wan=interface
network.wan.device='eth0.2'
network.wan.proto='dhcp'
network.wan.metric='1'
network.wan._area_type='wan'
network.wan.area_type='wan'
network.wan6=interface
network.wan6.device='eth0.2'
network.wan6.proto='dhcpv6'
network.wan6.metric='2'
network.wan6._area_type='wan'
network.wan6.area_type='wan'
network.@switch[0]=switch
network.@switch[0].name='switch0'
network.@switch[0].reset='1'
network.@switch[0].enable_vlan='1'
network.@switch_vlan[0]=switch_vlan
network.@switch_vlan[0].device='switch0'
network.@switch_vlan[0].vlan='1'
network.@switch_vlan[0].vid='1'
network.@switch_vlan[0].ports='0 1 2 6t'
network.@switch_vlan[1]=switch_vlan
network.@switch_vlan[1].device='switch0'
network.@switch_vlan[1].vlan='2'
network.@switch_vlan[1].vid='2'
network.@switch_vlan[1].ports='4 6t'
network.mob1s1a1=interface
network.mob1s1a1.proto='wwan'
network.mob1s1a1.modem='1-1'
network.mob1s1a1.metric='3'
network.mob1s1a1.sim='1'
network.mob1s1a1.dhcpv6='0'
network.mob1s1a1.pdptype='ip'
network.mob1s1a1.method='nat'
network.mob1s1a1._area_type='wan'
network.mob1s1a1.auto_apn='0'
network.mob1s1a1.force_apn='-1'
network.mob1s1a1.username='xxxx'
network.mob1s1a1.apn='xxxxx'
network.mob1s1a1.password='xxxxx'
network.mob1s1a1.delegate='1'
network.mob1s1a1.force_link='0'
network.mob1s1a1.auth='pap'
network.mob1s1a1.pdp='1'
network.mob1s1a1.area_type='wan'
network.mob1s2a1=interface
network.mob1s2a1.proto='wwan'
network.mob1s2a1.modem='1-1'
network.mob1s2a1.metric='4'
network.mob1s2a1.sim='2'
network.mob1s2a1.dhcpv6='0'
network.mob1s2a1.pdptype='ip'
network.mob1s2a1.method='nat'
network.mob1s2a1.auth='none'
network.mob1s2a1.auto_apn='1'
network.mob1s2a1._area_type='wan'
network.mob1s2a1.area_type='wan'

Yes I’m trying to connect via network.mob1s1a1
Thanks and BR

[VincentBlic]

Hello

I did :

uci set network.mob1s1a1.mtu=‘1300’
uci commit network
/etc/init.d/network restart
Failed to set attribute: Invalid input data or parameter
Failed to set attribute: Invalid input data or parameter
Failed to set attribute: Invalid input data or parameter
Failed to set attribute: Invalid input data or parameter
{
        "state": "OK"
}

not better (and now login page is completelly blank).
I removed the mtu parameter

I also tried :

root@RUT951:~# uci set network.wan.mtu=‘1300’
uci: Entry not found

for information :

root@RUT951:~# ip a | grep mtu
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000
3: ip6tnl0@NONE: <NOARP> mtu 1452 qdisc noop state DOWN group default qlen 1000
4: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000
5: gre0@NONE: <NOARP> mtu 1476 qdisc noop state DOWN group default qlen 1000
6: gretap0@NONE: <BROADCAST,MULTICAST> mtu 1462 qdisc noop state DOWN group default qlen 1000
7: erspan0@NONE: <BROADCAST,MULTICAST> mtu 1450 qdisc noop state DOWN group default qlen 1000
8: ip6gre0@NONE: <NOARP> mtu 1448 qdisc noop state DOWN group default qlen 1000
9: wwan0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 4096 qdisc fq_codel state UNKNOWN group default qlen 1000
15: br-lan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
16: eth0.1@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-lan state UP group default qlen 1000
17: eth0.2@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
19: qmimux0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1358 qdisc noqueue state UNKNOWN group default qlen 1000

So wan is wwan?
Sorry, I’m not a network expert…
Thanks

[VincentBlic]

Hello
Just to share some information :

• this router is connected to the teltonika RMS
  • Tried to connect from there : get the login page, and same result : password accepted, no error displayed but I stay on the login page
• and there is a PC running teamviewer connected to one ot its LAN port
  • tried to connect from this PC so directly to basic adress 192.168.1.1 : idem can get the login page, then we can observe a blink of the page like it loads but no error and stay on the login page …
    It’s weird, seems there is something blocking the WebUI (cache inside the RUT itself)
    I also compared configurations (uci show basically) with a reference that present no issue ==> identical

Thanks

[Marcelo.Barros]

@VincentBlic

I don’t want to break anything

My device (RUT240) have a interface called mob1s1a1 and when I changed the MTU, I lost the connection for one minute.

@VincentBlic

uci show network

No mtu… Or… I am lost something…

@VincentBlic

root@RUT951:~#

when you are at dashboard of your rut951. Information about the LTE MODEM…
It is show? qmimux0 ? has a mtu of 1358

@VincentBlic

So wan is wwan?

wwan0 with a mtu of 4096… this is only valid for jumbo frame at lan side.

@VincentBlic

As this is on a distant machine

Maybe we are looking in wrong direction… maybe you need to do reset factory default on it.

[Marija]

Hello @VincentBlic,

Could you please confirm if the issue has been resolved, or do you still need any assistance with this?

Best regards,

[VincentBlic]

Hi
My issue is not solved because had to focus on other topics (and I missed answer from Marcelo, sorry)
@Marcelo.Barros : - yes no MTU set by default by the router, and I cannot access to the dashboard because WebUI is inaccessible. And I don’t want any factory reset : this router is used by a customer.
@Marija : any proposition ?
Before any reset or firmware change, is it possible to just reset the http server of the router ? PErhaps something is just corrupted ?
Thanks and BR

[Martynas]

Hello @VincentBlic,

Before considering a reset or firmware update, could you please try executing the following command:

rm /usr/share/vuci/menu.d/menu.json

Then, reboot the router (reboot) to check if makes any change logging to WebUI.

Additionally, you can try restarting the HTTP server service by running:

/etc/init.d/uhttpd restart

If the issue persists, please check the HTTP server service status with:

/etc/init.d/uhttpd status

Let me know if this improves the situation or if further assistance is needed.

Best regards,

[VincentBlic]

Great !
It works (event if some icon are still missing ?? ) by just deleting the menu.json

No perhaps I can proceed to an updgrade : just I note that HW revision is 0404 : the first one I see.
Thanks and BR

[Marija]

Hello @VincentBlic,

Could you please confirm if the issue is resolved or if you still need any assistance with it?

Best regards,

[VincentBlic]

Hi @Marija

Yes I confirm the issue is resolved
Thanks again