Why my droples's ssh key changed?

Why my droples’s ssh key changed? Changed in April 11, 18:49.


Show comments

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

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.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

@neveralso57aff03a4fe5d19bf This is the community forum, there’s no “you” here.

@neveralso57aff03a4fe5d19bf @tlowrey Have you tried creating an support ticket to get an official answer? Please report back here with the answer.

For anyone in the SFO2 region asking about the key update, there was an outage in the SFO2 region (April 11 2017) and the remote host identification error you are seeing is normal. The host key was updated due to cloud-init as a part of the outage.

You will want to remove the offending line from your ~/.ssh/known_hosts file so that the new key can be accepted.

@AliceLovesReptiles Power outages do not cause SSH host keys to reset. It would be one thing if this was shared hosting, but theres are virtual machines, no?