Skip to main content

WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED

When you try to ssh into a instance and it failed giving errors which says remote host identification changed, possibly you have tried to ssh into that earlier but either it's been mapped to a IP or dns name has been assigned to that instance.you can resolve this issue ..

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@    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
36:85:1f:c0:7c:b6:d3:65:3c:2c:06:7a:20:25:c7:1d.
Please contact your system administrator.
Add correct host key in /home/bijendra/.ssh/known_hosts to get rid of this message.
Offending ECDSA key in /home/bijendra/.ssh/known_hosts:23
  remove with: ssh-keygen -f "/home/bijendra/.ssh/known_hosts" -R ec2-46-137-194-78.ap-southeast-1.compute.amazonaws.com
ECDSA host key for ec2-46-137-194-78.ap-southeast-1.compute.amazonaws.com has changed and you have requested strict checking.
Host key verification failed.

In case you see these messages while you ssh into the server, the identity of that instance has changed. Clear your home_folder/.ssh/known_hosts with the entry of the instance and now ssh. Accept the new identification. Known_hosts is a file which keeps track of the remote servers which you access and enters automatically for the next time.

Comments

Popular posts from this blog

Cannot allocate memory error while computing files - Setup Swap space

ActionView::Template::Error (Cannot allocate memory - nodejs /tmp/execjs20131021-26716-fckzo3.js 2>&1
Nodejs is used to compile javascript at runtime. In RoR applications, this error comes when server is started in production mode which compiles the assets or while running rake assets:precompile.
check for swap space and allocate

upload images to AWS::S3 in ruby using aws sdk gem

Using gem aws-sdk for a ROR application for uploading images to s3
Uploading images to a fixed bucket with different folders for each object or application. The s3 keeps a limitation on the number of buckets creation whereas there is no limitation for content inside a bucket. This code will upload image for a user to s3 using aws-sdk gem. The bucket and the image uploaded are made public, so that the images uploaded are directly accessible. The input is takes is the image complete path where it is present, folder in which it should be uploaded and user_id for whom it should be uploaded. def save_screenshot_to_s3(image_location, folder_name,user_id) service = AWS::S3.new(:access_key_id => ACCESS_KEY_ID, :secret_access_key => SECRET_ACCESS_KEY) bucket_name = "app-images" if(service.buckets.include?(bucket_name)) bucket = service.buckets[bucket_name] else bucket = service.buckets.create(bucket_name) …