api stops working with "cannot get challenge" on 5.0rc7 x86

RouterOS General
1

hi all,
we have an x86 server where api stopped working after about 120 days of uptime.
we got the “cannot get challenge” error, so we rebooted, and yesterday, after 4 days, api died again.
Also telnet answered “connection refused”, so I disabled and enabled it and it worked; after some hours connection was closed before asking login.

cpu is running always under 10% load. we have a dual core intel processor and 2gb of ram, with an average of 1800mb free.
disk space is 97% available.

what can we do?

2

5.0rc7?
Good time to upgrade your router to MikroTik RouterOS v5.6!

3

that’s a bit risky during the week for a main router, is there something I can do to have api working again before upgrading?

4

Running a main router on a release candidate (which is a nice word for beta) is pretty much the ultimate risk. You should upgrade ASAP. Stuff’s broken in RCs, which is why they weren’t the main version.