If you receive an error that looks like this when attempting to SSH into your Umbrel:
@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Don’t be alarmed! You don’t even need to SSH/use any advanced commands to resolve this issue.
This is a common error you just need to delete the known_hosts
file in this directory on your computer (this is how the computer your connecting from saves and authenticates with the device to SSH/Secure Shell into it):
As a note you are navigating to this folder just through your Finder on Mac or your Windows Explorer, you don’t need to do any commands here just navigate to the folder and delete it. Once these steps are complete for either Windows or Mac when you attempt to SSH again you can click “Yes” to confirm and sign in like normal!
------------------------------------------------------------------------------------------------------------
Steps for Mac:
A quick fix on Mac is to open the terminal app and you can run this command which will remove that known hosts folder:
sed -i '' '/^umbrel/d' ~/.ssh/known_hosts
You can copy that command above and hit enter and try to SSH into it again. This time you’ll be asked a question if you trust the host when you SSH in, just type ‘yes’ (without quotes) and you’d be good to go again…
Another method you can use is to remove these files manually:
Click your search icon on the top right menu of your Mac:
Then navigate to: `~/.ssh
` Once you type this
You’ll see this menu, click on the Folder:
Now just drag these files to your trash bin on your Mac
and then now when you attempt to SSH again you can click “Yes” to confirm and sign in like normal``
------------------------------------------------------------------------------------------------------------
Steps for Windows:
Navigate to this Directory, or you can click through your file explorer to get there:
`C:\users<your-windows-username>.ssh\
As shown:
Then delete both these files
As described above, just go ahead and SSH again and click Yes to reauthenticate your machine and now and you can login!