Ok. Thanks.
I’ll read the post.
Ok, to me.
So does this mean we are going to see 7.22.1 stable soon 
And 7.22.2, 7.22.3, 7.22.4 and 7.22.5 ... at which point bug resolving will move over to 7.23rc and 7.24beta
In version 7.22 final, I'm still experiencing frequent routing freezes on both OSPF and BGP (in an MPLS OSPF+BGP environment). The symptom is that the /routing/route print command gets stuck and doesn't display any routes. The only effective workaround I've found is to enable/disable any bridge (either operational or dummy).
This issue is blocking me from utilizing the fix for bgp vpn4 advertise bgp multihop SUP-207808, which was resolved in 7.22. I've reported this issue (SUP-209164) since January 2026, including supout and video evidence, and it's affecting 4 different routers (all CCR 1009 and 1032). Please address this issue seriously.
No documentaion anywhere on
“progress: [error] ACME certificates have moved to 'certificate' component. Please use /certificate/add-acme command.”
I could not find documentation how to add Let's Encrypt services add-acme. Any hints?
thanks!
Did you encounter this on non TILE architecture?
Yes all 4 of them are tile CCR series.
Would you be able to reproduce this issue on none TILE architecture just like CCR2116?
Supout removed
@qatar2022 NOT ON FORUM
supout is only for:
You should never upload supout.rif to public site, you are basically giving away your configuration to everyone, imagine if there where passwords for your VPN etc... only send it to MiroTik support...
# 2026-03-13 20:56:53 by RouterOS 7.21.3
# software id = W1S4-2VEZ
#
# model = CRS328-24P-4S+
# ...
Supout file has been removed
Hi There,
Large network, mostly crs326 switches. All previously on 7.19.2, all accessed remotely.
Upgraded first at the edges, ok, then core switch - have lost all forms of remote access - zerotier, wireguard. I also have devices internally that poll an external IP and I can see that is not happening.
Those tunnels and the gateway are on a crs326.
At present this is either a complete upgrade failure or some form of gateway / firewall issue - but I can certainly say this is not a smooth upgrade for me - it is actually a deeply concerning nightmare. I am HOPING that the issue might be what some others have alluded to - that my default 0.0.0.0/0 route has somehow got broken during the upgrade.
I’m keeping my fingers crossed that internally the network is still passing traffic, but if not, I guess the calls will start soon…
M
After I updated my RB5009UPr+S+ router, the computers in my house started dropping off the network about every 5 minutes. They disconnect and then reconnect about 3 seconds later.
At first I thought the problem only happened when downloading large files, but that turned out not to be the case. I’ve seen the disconnects even when the network is almost idle.
If Winbox is open at that moment, it closes. I reset the device to factory defaults and configured it again from scratch, but the issue is still happening. The problem occurs both with and without any queue configuration. I tested both fq-codel and cake, and it’s still the same.
It looks like the router freezes for about 3 seconds. CPU usage never goes above 10%. The logs aren’t helpful, and during the outage I can’t really tell what exactly is wrong, because stats don’t show any drops etc.
Any troubleshooting tips?
I can say that my router config, as it stood at update, currently gets its wan ip via dhcp–
/ip dhcp-client
add interface=ether1-Wan.Access
Interface and VRF are gone from Winbox Ping and Traceroute utilities. Maybe from other places too, these stood out.
LE: NEVERMIND. It's a feature, not a bug.
Cli:
/ping 8.8.8.8%ether1@main
Probably the same format works for winbox.
I sure do wish they would document this.
Further - Client has just confirmed ALL layer 2 and layer 3 networking is down. switch is completely bricked. cant get in via direct connect romon. Romon shows neighbors, but wont connect.
Yes you can do that, but this doesn't mean there's no regression here, and most likely a bug.
Even in terminal the behaviour is weird, those two tools from 7.20.5:
/tool/ping
30:68:93:DF:DC:1E address interface src-address
3C:6A:D2:CA:18:8C arp-ping interval ttl
60:83:E7:57:5C:7C count proplist vrf
D8:44:89:53:56:A2 dscp size
/tool/traceroute
address duration max-hops protocol timeout
count freeze-frame-interval port size use-dns
dscp interface proplist src-address vrf
And from 7.22:
/tool/ping
04:7C:16:7F:F8:1C 04:7C:16:7F:F8:1E address count interval size ttl
04:7C:16:7F:F8:1D C4:AD:34:E3:F6:98 arp-ping dscp proplist src-address
and a 2nd "TAB":
/tool/ping
interface vrf
Same with traceroute, interface and vrf to show up require a 2nd TAB for some reason, and a list of interfaces is shown instead on the first TAB.
/tool/traceroute
bonding1 ether2 ether5 ether8 sfp-sfpplus1 vlan170 dscp max-hops protocol timeout
bridge ether3 ether6 lo vlan66 address duration port size use-dns
ether1 ether4 ether7 pppoe-out1 vlan99 count freeze-frame-interval proplist src-address
Weird.
LE: NEVERMIND. It's a feature, not a bug.