Both of my MikroTik devices were messed up by this update. QuickSet page is gone.. login page randomly refreshes..
Cleared cache and cookies.. this is a huge mess. What the heck is happening here? I have two very different devices running different architectures and both of them are experiencing the exact same issue.
Need a fix.
No need to write again what others have already written and what has been confirmed by MikroTik (@EdPa )
Fix: downgrade to 7.20.2 or whatever version you had before. Lesson: first read the forum before you upgrade when a version has been released that same day.
@EdPa please put āwebfig is broken in this version, when you require it donāt upgrade yetā or some such message in the change notes, so not everyone has to find that by themselves.
No, I have only IPv4 in AFI. Also, even if I replace routing route with ip route Iāll get the same result.
That script works fine prior 7.20.
Mikrotik devs, how is possible totally bugged build like this one to be marked as "stable" ? Basic things like Webfig are totally broken. Pls test better before release to public as "stable".
My question is simpler: isnāt possible to test everything BY THE DEVS before posting it as āstable releaseā?
Or the only way to test is to pass this task to the customers ?
Most users think that āstableā means: works well, does not crash, all features OK.
However, that is not the case. āstableā means āno new release every week, only apparent problems will be fixed as .releases of this versionā (7.xx.1, 7.xx.2)
However, MikroTik does not really adhere to that. New features are introduced in .releases and new bugs are thus unavoidable to be introduced. And .releases are not first released as beta either, so a 7.20.4 release that first sees the light of day on November 6th will immediately be labeled āstableā, misleading uses into thinking that it will be stable software that is a good idea to install.
It would be better when it was first released as 7.20.4beta and then the beta is removed after one or two weeks of āno major problem reportsā, but alas it is not done that way.
So the rule of thumb is and remains: do NOT install upgrades within a week of release and ALWAYS first look in the release topic on the forum, when you consider your device operation important and your time (or travel) expensive. āstableā does NOT mean the software is stable, that is a misunderstanding.
They dont test, for sure.
We are their QA department which is really unprofessional ā¦
I am still running 7.19.6 and I am afraid to upgrade
Testing is a very broad field.
QA department?
It seems more like rat labs.
Once again I want to express all my personal admiration for the people that have the guts to test these new releases on real production devices and report the issues.
@infabo
Sure, very broad, but Webfig access?
Come on ...
It is disappointing to read people here berating QA people and generally denegrating the hard working staff members at Mikrotik. It is not hard to be civil, and remain professional on a community forum regardless of what issues you face. The purpose of a community forum is to help others, not to attack individuals who are here to support us.
I have unfortunately experienced issues with 7.20.4 upgrade as well on my two CRS326-24S+2Q+ switches. MLAG was broken, and logs indicated that the MLAG peers were unreachable. Downgrading back to 7.19.6 resolved the issue. SUP-203801 has been raised for this.
Hi all, just upgrade my hap-ax-lite-lte6 router and i canāt see the options to choose bands or upgrade firmware for the modem anymore in the web interface.
Is it moved to another location?
I was responding to this:
I wanted to emphasize that testing is not solely the responsibility of developers. A release cycle involves many people, and issues such as a broken WebFig Quickset or other affected areas should have been noticed by someone along the way.
And the strangest thing is that there's only this one bugfix related to WebFig:
webfig ā fixed button handling in skin designer;
You wouldn't expect that such a unrelated bugfix change could break core parts of WebFig. I can only hope this issue was introduced with version 7.20.4. As a customer, I really wouldn't want to buy a new device and find that the factory-installed firmware (7.20.3) already includes these WebFig issues - that would be a serious loss of trust.
Please read other articles above first. The web interface is broken in this version, use commandline or winbox instead.
Has anyone tried importing a script in system/script directory? Am I losing my mind? I tried importing but it load and executes. I just want to import the script.
Dear pe1ch1,
Some people in here, are normal people with normal jobs. We dontā have the time or energy to read a whole bunch of forum comments before install a stable version.
I never install a x.x.0 version. Always a x.x.4 and above. Despite that, this 7.20.x is completely broken.
We just want something to work out of the box when the label āstableā is there. Otherwise, it is not stable, it is something else.
Also in normal companies there is a line of releases that has only security fixes and well tested features, named long term release. We are in 7.20 release and NO ONE version is long term version.
This tells a lot about the philosophy of this company.
You cannot just āimport a scriptā, you need to import it in the form that export uses for stored scripts.
So: /system script add name=āscriptnameā source=āyour script here, in \-escaped formā
When you just want to save a script that you have as plain source, easiest is to paste it into a winbox ānew scriptā window, or same in webfig (in an older version, in current version webfig is broken).
Then please donāt install āstableā versions released one or two days before! I explained it already above but you are too busy to read it.
Thank youā¦ It was driving me crazy, since I did this in the past.
Must be my old ageā¦ lol
**Note**
I already know about the broken webfig. Iāve submitted numerous support tickets about webfig being broken on each update MT put out, including beta. When I find more things broken.
I check MT support portal and MT deleted them all.
I had 2 pppoe-client connectivity situations since updating to 7.20.4 which caused repeating pppoe dropout sequences. As thereās no clear way to pinpoint the issue at this moment I just downgraded to 7.20.2 to see if similar situation will reappearā¦