/tool user-manager database rebuild :log info "user-manager database rebuild OK"
Sorry, that's not a solution. This isn't a Windows PC.i normally solve this problem by restarting the mikrotik router.
Stop for me also when I deleted customers , reset and reconfigure ... so Im not sure ... but maybe is also related to customers now only user is adminHello to All
I have same problem with x86,i think this problem is related to "customers" in UM
I delete other limited customer and reboot router, problem solved!
Now i have only one customer.
Maybe this be helpful for u...
System reset ... and then reconfigure all again ... keep configuration file and userman database ...Hi
can you describe please...
The problem is not solved in ROS 6.13A GOOD NEWS
Hello to those who have this problem
I sent an E-mail to mikrotik support and they replied:
Thank you very much for the report.
We are aware of the problem. It will be fixed in the upcoming RouterOS versions.
today RouterOS is 6.12 and date is 30 April 2014
how?Please Check your database file "um-before-migration" in location "Files"
Any word on if the 6.21 update did actually fix it?MK says is solved in 6.21
"userman - fix "Your session has been reset due to inactivity" error;"
that is not true. After upgrade to v6.22 is not reachable the sign up page, the database isUsin 6.22 here without problems. Session reset due to REAL inactivity.
If there was other problems related to the web sessions using admind and customers pages see 6.23rc2 changelog:
What's new in 6.23rc2 (2014-Nov-20 09:07):
*) fetch - allow checking certificate trust without crl checking;
*) userman - fix more web session problems when user uses
customer and administrator interfaces at the same time;
*) snmp - fix external storage info reporting;
*) snmp - fix bulk walk problem introduced in v6.20;
*) fix tunnels - keep keepalive disabled for existing tunnels when upgrading;
*) fix tunnels - mtu for eoip tunnels was not allowed to be set less than 1280 since 6.20;
I hope it helps.