Question

How can i get rid of " WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! "

Posted March 20, 2013 164.4k views
Please someone with a solution for me. I just made a droplet from my work and now @ my home i can't access anymore and get this message :s @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ 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 RSA key sent by the remote host is
Add a comment
bizz.me88
By:
bizz.me88
Add a comment
2 comments
  • arduino731 January 28, 2015
    Reply Report

    @kamaln7 champion! its worked. after I deleted my old fingerprint and trying again root@ipaddress with new password from email and create on own prefer password.

  • TheDigitalOrchard December 5, 2015
    Reply Report

    I’ve been having this problem with a single droplet that has had SSL certificates installed. I have 20 other droplets that do not suffer from this problem. It seems that every time that I am on a different internet connection, which is very frequent in my travels, the server has a different host key. Clearing the lines from my known_hosts file does suppress the warning until the next time that I try to connect from a different IP address. Anybody have any ideas?

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
7 answers
javabytes March 22, 2013
You can just delete the line that have your current IP in the known_hosts file.
Reply Report
jstapels March 20, 2013
Sorry, my reply stripped out some text...

ssh-keygen -R [HOSTNAME]
ssh-keygen -R [IP_ADDRESS]

Alternatively, if you only SSH to a small set of known hosts, you can just delete your [HOME]/.ssh/known_hosts
Reply Report
jstapels March 20, 2013
This is happening because the ID for your hostname is not what your client expected. This can happen if you rebuilt your droplet from scratch, or if you recently pointed your hostname to a different server. The fix depends on your client.

If you're running a relatively common Linux distribution, you can usually run the following:
ssh-keygen -R
... OR/AND ...
ssh-keygen -R

Which will clear the corresponding entries in your .ssh/known_hosts file.
Reply Report
edgar22ronda July 3, 2014

Fixed, thanks dude!

Reply Report
baran May 26, 2015

I don’t understand…

Reply Report
bizz.me88 March 24, 2013
Thank you all, fixed!!!
Reply Report
seo September 7, 2014
[deleted]
Reply Report
nagarsuresh04 June 29, 2015

Issue fixed..Thanks a lot

Reply Report
Submit an Answer

Looking for something else?

Ask a new question Search for more help