Closed electricJP closed 6 years ago
Did your SSH_KEY
/PUB_KEY
not change during the upgrade?
If you only use password, you might have to check your known_hosts
(or equivalent) file, this will most likely have changed and will prevent you from connecting
Hello, thank you for your advice. I was testing ssh connection from standard user not homeassistant. When I tried from it I got this error:
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the ECDSA key sent by the remote host is
SHA256:XkEERFCG7hZnSff1V49i2xqDHAPNRtl3wjzH0lXdEf0.
Please contact your system administrator.
Add correct host key in /home/homeassistant/.ssh/known_hosts to get rid of this message.
Offending ECDSA key in /home/homeassistant/.ssh/known_hosts:1
remove with:
ssh-keygen -f "/home/homeassistant/.ssh/known_hosts" -R 192.168.1.1
ECDSA host key for 192.168.1.1 has changed and you have requested strict checking.
Host key verification failed.
I had to reinstall from scratch to upgrade python, that's why the key changed. It could be useful to have a little more explicit error message in home-assistant.log.
The PR should help identifying these types of issues
Home Assistant release (
hass --version
): 0.63.3 Python release (python3 --version
): Python 3.5.3 Component/platform: Asuswrt Description of problem: After new merlin-firmware (branch 384)It was working just fine with older firmware (branch 380) which will be legacy soon
It is confirmed ssh is enabled and working on the router by establishing a connection from PI:
Using telnet as default protocol works: