I ssh from my linux box or from another mikrotik. It ask for password but does not accept. Mikrotik do you see this problem?
I can freely ssh (by PuTTY) to x86 v5.0rc10, if you’re talking about that
after that, I can /sys ssh to itself w/o problem
don’t you have certificates added for the user?
I am using miple and mipbe. I haven’t tried sshing to itself yet.
I ssh to self and it won’t accept password still
do you have key assigned to the user you are trying to log on with?
if yes, then this is as designed - use key to authenticate, as password login is disabled as being less secure that use of key.
all my mikrotiks have default settings. Weird huh?
tried different routers with rc11 and i could log in into all of them
check
/user ssh-keys
maybe there lays the answer.
I checked. All my settings are defaulted. I dont change ssh settings. Mikrotik has a supout of one of my mikrotiks.
your username and/or password has something in it that RouterOS doesnt like. Change it and see if that has any effect. Also, is the ip that you are connecting to on a standard eth interface or some other type?
my pass is letters and numbers. I have 10.1.1.245 on eth0 that is it.
i changed password to asdf and it still didnt work. It just asks for another password.
Clearing the configuration of
/user ssh-keys
fixed the problem.
Yep it did. Thanks for all your support. I didnt know I had a key in there. I must of put that in there years ago. Thanks again.
Upgrade to 5.x, then downgrade to 4.17, then clear configuration
[admin@MikroTik] > /user ssh-keys print
USER KEY-OWNER
error - contact MikroTik support and send a supout file (2)
[admin@MikroTik] > ip service print detail
Flags: X - disabled, I - invalid
...
3 I name="ssh" port=22 address=0.0.0.0/0
...
How I can make ssh enabled?
have you tried 5.2, as there where some ssh fixes about exactly that, if i remember correctly.
Upgrade to 5.2 , then downgrade to 4.17 - fix the problem.
Thx.
yep i am working now. Thanks.