[7.20] Web UI reload loop issue

RouterOS General
1

Anyone found a workaround for this Web UI issue?

  1. Device/CHR with RouterOS 7.20

  2. Edit an interface (e.g. ether1 or similar)

  3. Type in a change in the interface name (e.g. ether1-test)

  4. Press Apply

  5. Web UI goes in to refresh/reload loop

  6. Jump to Web UI terminal to see the bug effect clearly

After that you can see that everything just repeatedly reloads/refreshes preventing any modifications to UI and reverting any typed text on fields and in terminal.

I’ve tested this with ROS 7.20 on multiple platforms (CHR, various hardware) and with Chrome, Safari, Brave, Firefox browsers. Only common thing I’ve found in devices expericieng this issue the ROS v7.20.

So far I’ve been able to complete the required configuration changes using CLI, but this is really annoying.

2

Move back to 7.19.6 perhaps if it annoys you that much ?

Did you see this as well in beta/rc versions ? Or didn't you even look at those versions ?

Why did you move to 7.20 to begin with ? If you had followed the release thread for that version, you would have known already by now there is more then 1 thing not "on par" with that version.
Best to sit it out until the wrinkles have been ironed out.

Generally (especially for production or when you can not accept downtime) it's not a bad idea to wait at least for .1 or .2 version.
Or accept the bugs :grinning_face:

At home I follow most beta/rc versions, for production however I am a lot more cautious.

3

I run two non-critical test systems on rc/beta but I did not notice this issue even in the recent rc’s.

4

Just got response from Mikrotik Support to the issue ticket

We are aware of this problem and are fixing it right now. The fix should be available in the next stable version. Unfortunately, I cannot give an ETA.

Right now please use Winbox as a workaround for this issue.

5

As of the time of writing, I can confirm that 7.21beta2 has fixed this issue.

SUP-200627

6

Same probleme here, on CCR2116-12G-4S+

7

This bug is not device specific and is present in all RouterOS installations.

As said, it will be fixed in next stable release and is already fixed in 7.21beta2 testing release.