“Remote host identification has changed†on server preventing SSHing in
Clash Royale CLAN TAG#URR8PPP up vote
0
down vote
favorite
I just tried sshing into my server from my desktop after about a week of not having logged into it. I got the following message:
$ ssh me@192.168.x.xx
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ 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:xxxx/xxxx/xxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxx.
Please contact your system administrator.
Add correct host key in /root/.ssh/known_hosts to get rid of this message.
Offending ECDSA key in /root/.ssh/known_hosts:1
remove with:
ssh-keygen -f "/root/.ssh/known_hosts" -R 192.168.x.xx
ECDSA host key for 192.168.x.xx has changed and you have requested strict checking.
Host key verification failed.
But I'm confused, because I haven't made any changes to my server (Other questions here have stated that reinstalling an OS would yield this error.), and to my knowledge, my server isn't public facing. I had enabled ssh key-based authentication and disabled password authentication too.
I think I can just add the host key to my known hosts to get rid of the error, but I don't want to do that until I know what's the crux of the problem.
Any idea as to how this message randomly started appearing, how I can resolve this, and how I can secure my server better in the future?
THANKS!
networking server ssh security
asked Feb 10 at 21:46
sos
1
add a comment |Â
up vote
0
down vote
favorite
I just tried sshing into my server from my desktop after about a week of not having logged into it. I got the following message:
$ ssh me@192.168.x.xx
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ 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:xxxx/xxxx/xxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxx.
Please contact your system administrator.
Add correct host key in /root/.ssh/known_hosts to get rid of this message.
Offending ECDSA key in /root/.ssh/known_hosts:1
remove with:
ssh-keygen -f "/root/.ssh/known_hosts" -R 192.168.x.xx
ECDSA host key for 192.168.x.xx has changed and you have requested strict checking.
Host key verification failed.
But I'm confused, because I haven't made any changes to my server (Other questions here have stated that reinstalling an OS would yield this error.), and to my knowledge, my server isn't public facing. I had enabled ssh key-based authentication and disabled password authentication too.
I think I can just add the host key to my known hosts to get rid of the error, but I don't want to do that until I know what's the crux of the problem.
Any idea as to how this message randomly started appearing, how I can resolve this, and how I can secure my server better in the future?
THANKS!
networking server ssh security
asked Feb 10 at 21:46
sos
1
3
Is your server locked to a fixed address? If the server hasn't changed but its IP address has changed it'll cause this warning (as its signatures is 'known' for a different IP address and thus 'different' machine....)
– guiverc
Feb 10 at 21:56
@guiverc yup, I have a static IP address on the server.
– sos
Feb 10 at 22:15
Also: my client (desktop trying to access the server) has recently updated Windows... may that have caused the error to begin occurring?
– sos
Feb 10 at 22:42
Update: followed steps here to check to make sure that everything was safe. Still unsure why the error began occurring at all.
– sos
Feb 11 at 6:09
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I just tried sshing into my server from my desktop after about a week of not having logged into it. I got the following message:
$ ssh me@192.168.x.xx
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ 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:xxxx/xxxx/xxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxx.
Please contact your system administrator.
Add correct host key in /root/.ssh/known_hosts to get rid of this message.
Offending ECDSA key in /root/.ssh/known_hosts:1
remove with:
ssh-keygen -f "/root/.ssh/known_hosts" -R 192.168.x.xx
ECDSA host key for 192.168.x.xx has changed and you have requested strict checking.
Host key verification failed.
But I'm confused, because I haven't made any changes to my server (Other questions here have stated that reinstalling an OS would yield this error.), and to my knowledge, my server isn't public facing. I had enabled ssh key-based authentication and disabled password authentication too.
I think I can just add the host key to my known hosts to get rid of the error, but I don't want to do that until I know what's the crux of the problem.
Any idea as to how this message randomly started appearing, how I can resolve this, and how I can secure my server better in the future?
THANKS!
networking server ssh security
asked Feb 10 at 21:46
sos
1
I just tried sshing into my server from my desktop after about a week of not having logged into it. I got the following message:
$ ssh me@192.168.x.xx
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ 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:xxxx/xxxx/xxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxx.
Please contact your system administrator.
Add correct host key in /root/.ssh/known_hosts to get rid of this message.
Offending ECDSA key in /root/.ssh/known_hosts:1
remove with:
ssh-keygen -f "/root/.ssh/known_hosts" -R 192.168.x.xx
ECDSA host key for 192.168.x.xx has changed and you have requested strict checking.
Host key verification failed.
But I'm confused, because I haven't made any changes to my server (Other questions here have stated that reinstalling an OS would yield this error.), and to my knowledge, my server isn't public facing. I had enabled ssh key-based authentication and disabled password authentication too.
I think I can just add the host key to my known hosts to get rid of the error, but I don't want to do that until I know what's the crux of the problem.
Any idea as to how this message randomly started appearing, how I can resolve this, and how I can secure my server better in the future?
THANKS!
networking server ssh security
networking server ssh security
asked Feb 10 at 21:46
sos
1
asked Feb 10 at 21:46
sos
1
asked Feb 10 at 21:46
sos
1
asked Feb 10 at 21:46
sos
1
asked Feb 10 at 21:46
sos
1
1
3
Is your server locked to a fixed address? If the server hasn't changed but its IP address has changed it'll cause this warning (as its signatures is 'known' for a different IP address and thus 'different' machine....)
– guiverc
Feb 10 at 21:56
@guiverc yup, I have a static IP address on the server.
– sos
Feb 10 at 22:15
Also: my client (desktop trying to access the server) has recently updated Windows... may that have caused the error to begin occurring?
– sos
Feb 10 at 22:42
Update: followed steps here to check to make sure that everything was safe. Still unsure why the error began occurring at all.
– sos
Feb 11 at 6:09
add a comment |Â
3
Is your server locked to a fixed address? If the server hasn't changed but its IP address has changed it'll cause this warning (as its signatures is 'known' for a different IP address and thus 'different' machine....)
– guiverc
Feb 10 at 21:56
@guiverc yup, I have a static IP address on the server.
– sos
Feb 10 at 22:15
Also: my client (desktop trying to access the server) has recently updated Windows... may that have caused the error to begin occurring?
– sos
Feb 10 at 22:42
Update: followed steps here to check to make sure that everything was safe. Still unsure why the error began occurring at all.
– sos
Feb 11 at 6:09
3
3
Is your server locked to a fixed address? If the server hasn't changed but its IP address has changed it'll cause this warning (as its signatures is 'known' for a different IP address and thus 'different' machine....)
– guiverc
Feb 10 at 21:56
Is your server locked to a fixed address? If the server hasn't changed but its IP address has changed it'll cause this warning (as its signatures is 'known' for a different IP address and thus 'different' machine....)
– guiverc
Feb 10 at 21:56
@guiverc yup, I have a static IP address on the server.
– sos
Feb 10 at 22:15
@guiverc yup, I have a static IP address on the server.
– sos
Feb 10 at 22:15
Also: my client (desktop trying to access the server) has recently updated Windows... may that have caused the error to begin occurring?
– sos
Feb 10 at 22:42
Also: my client (desktop trying to access the server) has recently updated Windows... may that have caused the error to begin occurring?
– sos
Feb 10 at 22:42
Update: followed steps here to check to make sure that everything was safe. Still unsure why the error began occurring at all.
– sos
Feb 11 at 6:09
Update: followed steps here to check to make sure that everything was safe. Still unsure why the error began occurring at all.
– sos
Feb 11 at 6:09
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1004983%2fremote-host-identification-has-changed-on-server-preventing-sshing-in%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
3
Is your server locked to a fixed address? If the server hasn't changed but its IP address has changed it'll cause this warning (as its signatures is 'known' for a different IP address and thus 'different' machine....)
– guiverc
Feb 10 at 21:56
@guiverc yup, I have a static IP address on the server.
– sos
Feb 10 at 22:15
Also: my client (desktop trying to access the server) has recently updated Windows... may that have caused the error to begin occurring?
– sos
Feb 10 at 22:42
Update: followed steps here to check to make sure that everything was safe. Still unsure why the error began occurring at all.
– sos
Feb 11 at 6:09