FOR TIPS, gUIDES & TUTORIALS

subscribe to our Youtube

GO TO YOUTUBE

14455 questions

17168 answers

28195 comments

0 members

We are migrating to our new platform at https://community.teltonika.lt. Moving forward, you can continue discussions on this new platform. This current platform will be temporarily maintained for reference purposes.
0 votes
517 views 1 comments
by anonymous
RUTX11 webui throws me out (logs me out)  The point where it happens usually is Networking/Wireless then any action that involves the wifi (scan, save&apply), my best guess is that there's an exception handling error, because parallel to this logouts I see in the logs reinitialization of interfaces as well.

Additionally, which is probably an independent error,  after some auto logout / login, won't let me in again with the correct credentials. When this happens for a few cycles of throw out re-login I can still log in from the other channel (5G / 2,4G), but after a few cycles credentials aren't recognized again.

Sometimes (can't repeat the behavior) it let's me in again after a few minutes, other times even after hours won't.

SSH works always fine, it doesn't disconnect me even when the webui throws me out, so it's not physical or TCP related.

Rebooting the device helps, then the error appears again.

So...

1) it would be great to understand which service to restart to reset the webui to startup state without rebooting the whole device

2) it would be great to have a decent logfile of the uhttpd / webui, because it's impossible to debug this way, and I can't even post it here for you guys to debug

2 Answers

0 votes
by anonymous

Hello,

From a ssh console, you can try a /etc/init.d/uhttpd restart to reinitialize the webui server.

For the logs, look at System->Administration->Troubleshoot->System log, or redirect the logs to a remote syslogd server.

Regards,

by anonymous
Restarting the uhttpd doesn't resolve the login issue, neither is clearing client side cache... so the question is still open, where does the webui store login information

Obviously I checked logs, but syslog doesn't say anything about httpd access / errors.

Nevertheless, I downgraded to RUTX_R_00.02.06.1 and the problem is gone.
0 votes
by anonymous

Ok, so if anyone comes here with the same problem, downgrading to RUTX_R_00.02.06.1 solves the issue in a stable way.

Until now I haven't seen any downside of the older firmware (apart of having to reconfigure everything).