Locked out hEX with ssh public key

Hi.
I added my SSH public key to my user on my hEX Router, which then apparently disabled password login. At the same time it will not accept my SSH private key for login. I have double checked my key pair, and they match, no doubt about it.

I can see my SSH client is trying to use the key, even specifying the private does not work.

ssh <username>@<ip> -i ~/.ssh/id_rsa

Has any one experienced this before ?

Hi,
you forgot to mention, which version of ROS you have, but I have just read this in 7.5beta4 relesae notes :

*) ssh - fixed importing of public keys;

Regards
W

I cant explicitly remember which version, but i did do a software update yesterday, so it must be the most reason version for the hEX PoE router.

Edit: Do you have a link to those release notes ?

Hmm it looks like I have to reset the router then.. Unless there’s some magical way of accessing the router ?

Well, if you have only ssh with public key allowed, then there is none. Otherwise you could use a WOOBM stick or telnet or Winbox…

Is telnet enabled by default ?

I´m not sure but you could give it a try as well for http(Webfig). RoMon & MacTelenet are also possible from another MT device.
Also you might have to consider a default firewall ruleset (don´t use the WAN port,but try LAN1).
I don´t know the defaults on hEX, that changes from device to device and from version to version.
There is some info here about defaults, but not much: https://help.mikrotik.com/docs/display/ROS/Default+configurations
Look here for every way of accessing that device:
https://help.mikrotik.com/docs/display/ROS/Management+tools

All access services are enabled by default, except api-ssl and www-ssl that require a certificate.

But they are all enabled only so that the first time you turn it on you can choose a (secure) access method and disable all the others that are unsafe or useless.

It looks like there’s a few options. I’ll just need to go ti the location to get on the LAN side.
Thank you for your inputs.