I haven’t done much in server (last thing I was configureing was WireGuard tunnels between my homes).
But I just discovered that my bridge screen has screen full of errors, telling that all the bridge ports are not running. Addded a screenshot. And wondering what happened and what is wrong?
Anything in logs regarding bridge or its ports?
Are ports, marked as “not running”, connected to devices which are powered up?
It’s not “all ports”. Some are active.
What client are you using to represent this info ?
Which ROS version ?
Is something plugged in on those ports ?
If not, that may be the reason together with the new style info is being represented in Winbox4/Webfig (7.17beta/rc)
I am seeing this too when using Webfig or Winbox4 towards RB5009 using 7.17beta6 on ports where nothing is plugged in.
Rather annoying, if you ask me.
While my two esteemed colleagues, okay they are professionals, Im just the floor washer in their office, jump around like frogs, please provide the config.
/export file=anynameyouwish (minus router serial number, any public WANIP info, keys etc.. )
Also if you are wireguarding to another device, also provide the config as above. ( if not MT but some other thing, at least provide wireguard settings, keeping keys and public IP hidden)
Now you’re using a canon to kill a mosquito …
Config export is not needed here if it is a mere representation issue.
Sorry, but ASSUME is not in my vocabulary…
I have one size HAMMER… it works 95% of time… the other 5%, is when you and mkx get lucky first, on the whackamole game you like to play.
I see the same behavior in Winbox4 or Webfig on RB5009 (7.17b6) and Hex Refresh (7.17rc1) for ports with no cable in it.
So big possibility it’s just that and nothing else.
Or you want my config as well ? 
Post your own thread instead of hijacking this one! ;-PPP
Already reported here.
Thanks for the feedback.
This was intended as a visual improvement introduced in RouterOS v7.17:
*) bridge - added message for inactive port reason;
The feature shows why bridge ports become inactive, and in most cases, it’s because the interface isn’t running. However, this change appears to be causing more pain than good, we plan to filter out the “not running” reason and only keep the message for rarer, more specific cases.
Thank you, @EdPa. I was not looking forward to needing to filter these useless comments from my text backups, and I found no use for these inconsequential complaints in WinBox for each of my currently-unused ports.
While I fully understand the rationale for this message in my view the problem here is not the message itself but the fact it currently looks too much like an error (which it is not for a lot of cases, certainly not when no cable or active connection is present).
There is also a partially double presentation of info since there is already a capital “I” being shown just below (which means Inactive, so it’s already clear that it is not running)
Maybe it could be changed from “not running” (that does sound like there is a problem with the interface) to something like “no connection” (that would mean both an empty port or a port connected to a device that is off)? 