How to bypass remote login problem to CSS106-1G-4P-1S? - after few months I can’t login to few CSS106 with RIGHT password, because of SwOS bug. I know that after power reset - it will be possible to login, but I have a few CSS106 far away, and can’t power reset. So - is there any solution to reboot remotely this CSS106. I know password for 100%, but can’t login to that switch. SwOS 2.16.
Not likely a bug. I just confirmed that I have no issue logging into my CSS106-1G-4P-1S that has SwitchOS 2.16 with an uptime of something around a year and a half. No problem - never have had one.
There is a bug for 100%,because i have checked it. At one site i rebooted CSS106 (by powersing off an on) , and after that - I logged in. Before that it was the same problem with logging to switch.
Then you need to file a bug report with Mikrotik Support …
I hope it’s fixed at SwOS 2.18, but I can’t login to upgrade…
So, is there any solution to reboot it remotelly…?
I recognize that problem. I filed away the switch in the recycling bin very long ago, so I do not remember the details, but it surely is a bug.
I think sometimes it reverted to no (blank) password, you could try that.
Thank You, but not this time… I can’t login with good password, without password, with different browsers - nothing works. So, the only way is to unplug power, and turn it on.
Did you already contact support about it ?
No not yet, I thought before bothering them I first try here to see if someone has an obvious solution.
The same issue with CRS328-4C-20S-4S+ and CRS326-24G-2S+. Both of them were running SwOS 2.13 and until today they had 400+ days uptime . Recently I found out I was not able to login with the correct password on both of them.
After many attempts, I finally powered them down and up. After that the correct password I have tried multiple times before, works again.
Now I am upgrading them to SwOS 2.18.
If this happens again, what is the way to provide a log or anything to the support if I file a bug? How do I extract anything from SwOS while the device is basically locked down?