sshfs - transport endpoint is not connected
After reinstalling the server I can not mount it
sshfs root@domain.com:/var /remote_mount
fuse: bad mount point `/remote_mount': Transport endpoint is not connected
update
# ssh root@domain.com
The authenticity of host 'domain.com (xxx.xxx.xxx.xxx)' can't be established.
ECDSA key fingerprint is 57:b6:bd:76:17:80:73:85:4a:14:8a:6f:dc:fa:fe:7c.
Are you sure you want to continue connecting (yes/no)?
ssh sshfs
edited Aug 31 '15 at 22:22
Gilles
539k12810921606
asked Aug 31 '15 at 8:48
clarkkclarkk
56451224
|
show 1 more comment
After reinstalling the server I can not mount it
sshfs root@domain.com:/var /remote_mount
fuse: bad mount point `/remote_mount': Transport endpoint is not connected
update
# ssh root@domain.com
The authenticity of host 'domain.com (xxx.xxx.xxx.xxx)' can't be established.
ECDSA key fingerprint is 57:b6:bd:76:17:80:73:85:4a:14:8a:6f:dc:fa:fe:7c.
Are you sure you want to continue connecting (yes/no)?
ssh sshfs
edited Aug 31 '15 at 22:22
Gilles
539k12810921606
asked Aug 31 '15 at 8:48
clarkkclarkk
56451224
Post output ofssh -v root@domain.com?
– BAR
Aug 31 '15 at 8:58
question updated..
– clarkk
Aug 31 '15 at 9:03
Typeyesand try again.
– BAR
Aug 31 '15 at 9:04
@BAR, after I didssh root@domain.comI deleted the old RSA key and now it works again.. (The server got a new IP address) Create an answer :)
– clarkk
Aug 31 '15 at 9:20
Good to know it worked for you!
– BAR
Aug 31 '15 at 9:21
|
show 1 more comment
After reinstalling the server I can not mount it
sshfs root@domain.com:/var /remote_mount
fuse: bad mount point `/remote_mount': Transport endpoint is not connected
update
# ssh root@domain.com
The authenticity of host 'domain.com (xxx.xxx.xxx.xxx)' can't be established.
ECDSA key fingerprint is 57:b6:bd:76:17:80:73:85:4a:14:8a:6f:dc:fa:fe:7c.
Are you sure you want to continue connecting (yes/no)?
ssh sshfs
edited Aug 31 '15 at 22:22
Gilles
539k12810921606
asked Aug 31 '15 at 8:48
clarkkclarkk
56451224
After reinstalling the server I can not mount it
sshfs root@domain.com:/var /remote_mount
fuse: bad mount point `/remote_mount': Transport endpoint is not connected
update
# ssh root@domain.com
The authenticity of host 'domain.com (xxx.xxx.xxx.xxx)' can't be established.
ECDSA key fingerprint is 57:b6:bd:76:17:80:73:85:4a:14:8a:6f:dc:fa:fe:7c.
Are you sure you want to continue connecting (yes/no)?
ssh sshfs
ssh sshfs
edited Aug 31 '15 at 22:22
Gilles
539k12810921606
asked Aug 31 '15 at 8:48
clarkkclarkk
56451224
edited Aug 31 '15 at 22:22
Gilles
539k12810921606
asked Aug 31 '15 at 8:48
clarkkclarkk
56451224
edited Aug 31 '15 at 22:22
Gilles
539k12810921606
edited Aug 31 '15 at 22:22
Gilles
539k12810921606
edited Aug 31 '15 at 22:22
Gilles
539k12810921606
539k12810921606
asked Aug 31 '15 at 8:48
clarkkclarkk
56451224
asked Aug 31 '15 at 8:48
clarkkclarkk
56451224
asked Aug 31 '15 at 8:48
clarkkclarkk
56451224
56451224
Post output ofssh -v root@domain.com?
– BAR
Aug 31 '15 at 8:58
question updated..
– clarkk
Aug 31 '15 at 9:03
Typeyesand try again.
– BAR
Aug 31 '15 at 9:04
@BAR, after I didssh root@domain.comI deleted the old RSA key and now it works again.. (The server got a new IP address) Create an answer :)
– clarkk
Aug 31 '15 at 9:20
Good to know it worked for you!
– BAR
Aug 31 '15 at 9:21
|
show 1 more comment
Post output ofssh -v root@domain.com?
– BAR
Aug 31 '15 at 8:58
question updated..
– clarkk
Aug 31 '15 at 9:03
Typeyesand try again.
– BAR
Aug 31 '15 at 9:04
@BAR, after I didssh root@domain.comI deleted the old RSA key and now it works again.. (The server got a new IP address) Create an answer :)
– clarkk
Aug 31 '15 at 9:20
Good to know it worked for you!
– BAR
Aug 31 '15 at 9:21
Post output of
ssh -v root@domain.com?– BAR
Aug 31 '15 at 8:58
Post output of
ssh -v root@domain.com?– BAR
Aug 31 '15 at 8:58
question updated..
– clarkk
Aug 31 '15 at 9:03
question updated..
– clarkk
Aug 31 '15 at 9:03
Type
yes and try again.– BAR
Aug 31 '15 at 9:04
Type
yes and try again.– BAR
Aug 31 '15 at 9:04
@BAR, after I did
ssh root@domain.com I deleted the old RSA key and now it works again.. (The server got a new IP address) Create an answer :)– clarkk
Aug 31 '15 at 9:20
@BAR, after I did
ssh root@domain.com I deleted the old RSA key and now it works again.. (The server got a new IP address) Create an answer :)– clarkk
Aug 31 '15 at 9:20
Good to know it worked for you!
– BAR
Aug 31 '15 at 9:21
Good to know it worked for you!
– BAR
Aug 31 '15 at 9:21
|
show 1 more comment
4 Answers
4
active
oldest
votes
Your SSHd has not been setup.
Do that first and try again.
answered Aug 31 '15 at 9:04
BARBAR
1348
What do you mean? It has been installed on the server withapt-get install sshfs
– clarkk
Aug 31 '15 at 9:13
@clarkk sshd is totally different. This is your ssh daemon, your ssh server. The machine you are ssh-ing to needs to have sshd properly configured. Only then will sshfs work properly. Were you able to connect usingssh root@domain.com?
– BAR
Aug 31 '15 at 9:14
Ohh.. Didn't notice it was you who answered the question.. but it worked after I didssh root@domain.comand it gave me an warning about DNS.. Then I deleted the old RSA key in the cache... and now it works.. The server got a new IP address
– clarkk
Aug 31 '15 at 9:22
add a comment |
After using sshfs on and off for years just got this error for the first time and found this page. All the "setup sshd" wasn't much of a help as ssh has been working.
However, a bit of testing found the solution. The problem occurred after a failed sshfs mount request with a bad hostname in it. As ls -l $mountpoint failed with this error I tried clearing the trouble with fusermount -u $mountpoint, and it worked!
After the failure I got the error on a simple ls $mountpoint after the failed ssshf.
answered Jul 27 '16 at 18:25
GilbertGilbert
46445
That was the problem here too.
– Dan Dascalescu
Jan 18 '17 at 22:04
This helped.. but first I had to kill a process that had the mount point openlsof | grep $mountpoint
– jsj
Nov 13 '17 at 0:08
@jsj that can be a good point.
– Gilbert
Nov 19 '17 at 0:39
add a comment |
I had this problem after using sshfs for some time. This answer is relevant only for situations where sshfs was already used successfully prior to the problem.
What usually causes this problem is that you terminated the connection sometime ago, and the system still has the /remote_mount mounted. First try doing:
sudo umount /remote_mount
and then attempt to connect again.
edited Sep 26 '16 at 8:39
countermode
5,28842044
answered Sep 26 '16 at 8:11
krsnik93krsnik93
12112
Why was this downvoted? That made it for me, thank U !!
– Campa
Feb 20 '18 at 11:47
This answer was the right one for me too
– CharlesB
Mar 30 '18 at 8:05
add a comment |
sudo umount /remote_mount - This worked. Thanks
answered 15 mins ago
meeeeeeeemeeeeeeee
1
New contributor
meeeeeeee is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f226546%2fsshfs-transport-endpoint-is-not-connected%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
Your SSHd has not been setup.
Do that first and try again.
answered Aug 31 '15 at 9:04
BARBAR
1348
What do you mean? It has been installed on the server withapt-get install sshfs
– clarkk
Aug 31 '15 at 9:13
@clarkk sshd is totally different. This is your ssh daemon, your ssh server. The machine you are ssh-ing to needs to have sshd properly configured. Only then will sshfs work properly. Were you able to connect usingssh root@domain.com?
– BAR
Aug 31 '15 at 9:14
Ohh.. Didn't notice it was you who answered the question.. but it worked after I didssh root@domain.comand it gave me an warning about DNS.. Then I deleted the old RSA key in the cache... and now it works.. The server got a new IP address
– clarkk
Aug 31 '15 at 9:22
add a comment |
Your SSHd has not been setup.
Do that first and try again.
answered Aug 31 '15 at 9:04
BARBAR
1348
What do you mean? It has been installed on the server withapt-get install sshfs
– clarkk
Aug 31 '15 at 9:13
@clarkk sshd is totally different. This is your ssh daemon, your ssh server. The machine you are ssh-ing to needs to have sshd properly configured. Only then will sshfs work properly. Were you able to connect usingssh root@domain.com?
– BAR
Aug 31 '15 at 9:14
Ohh.. Didn't notice it was you who answered the question.. but it worked after I didssh root@domain.comand it gave me an warning about DNS.. Then I deleted the old RSA key in the cache... and now it works.. The server got a new IP address
– clarkk
Aug 31 '15 at 9:22
add a comment |
Your SSHd has not been setup.
Do that first and try again.
answered Aug 31 '15 at 9:04
BARBAR
1348
Your SSHd has not been setup.
Do that first and try again.
answered Aug 31 '15 at 9:04
BARBAR
1348
answered Aug 31 '15 at 9:04
BARBAR
1348
answered Aug 31 '15 at 9:04
BARBAR
1348
answered Aug 31 '15 at 9:04
BARBAR
1348
1348
What do you mean? It has been installed on the server withapt-get install sshfs
– clarkk
Aug 31 '15 at 9:13
@clarkk sshd is totally different. This is your ssh daemon, your ssh server. The machine you are ssh-ing to needs to have sshd properly configured. Only then will sshfs work properly. Were you able to connect usingssh root@domain.com?
– BAR
Aug 31 '15 at 9:14
Ohh.. Didn't notice it was you who answered the question.. but it worked after I didssh root@domain.comand it gave me an warning about DNS.. Then I deleted the old RSA key in the cache... and now it works.. The server got a new IP address
– clarkk
Aug 31 '15 at 9:22
add a comment |
What do you mean? It has been installed on the server withapt-get install sshfs
– clarkk
Aug 31 '15 at 9:13
@clarkk sshd is totally different. This is your ssh daemon, your ssh server. The machine you are ssh-ing to needs to have sshd properly configured. Only then will sshfs work properly. Were you able to connect usingssh root@domain.com?
– BAR
Aug 31 '15 at 9:14
Ohh.. Didn't notice it was you who answered the question.. but it worked after I didssh root@domain.comand it gave me an warning about DNS.. Then I deleted the old RSA key in the cache... and now it works.. The server got a new IP address
– clarkk
Aug 31 '15 at 9:22
What do you mean? It has been installed on the server with
apt-get install sshfs– clarkk
Aug 31 '15 at 9:13
What do you mean? It has been installed on the server with
apt-get install sshfs– clarkk
Aug 31 '15 at 9:13
@clarkk sshd is totally different. This is your ssh daemon, your ssh server. The machine you are ssh-ing to needs to have sshd properly configured. Only then will sshfs work properly. Were you able to connect using
ssh root@domain.com?– BAR
Aug 31 '15 at 9:14
@clarkk sshd is totally different. This is your ssh daemon, your ssh server. The machine you are ssh-ing to needs to have sshd properly configured. Only then will sshfs work properly. Were you able to connect using
ssh root@domain.com?– BAR
Aug 31 '15 at 9:14
Ohh.. Didn't notice it was you who answered the question.. but it worked after I did
ssh root@domain.com and it gave me an warning about DNS.. Then I deleted the old RSA key in the cache... and now it works.. The server got a new IP address– clarkk
Aug 31 '15 at 9:22
Ohh.. Didn't notice it was you who answered the question.. but it worked after I did
ssh root@domain.com and it gave me an warning about DNS.. Then I deleted the old RSA key in the cache... and now it works.. The server got a new IP address– clarkk
Aug 31 '15 at 9:22
add a comment |
After using sshfs on and off for years just got this error for the first time and found this page. All the "setup sshd" wasn't much of a help as ssh has been working.
However, a bit of testing found the solution. The problem occurred after a failed sshfs mount request with a bad hostname in it. As ls -l $mountpoint failed with this error I tried clearing the trouble with fusermount -u $mountpoint, and it worked!
After the failure I got the error on a simple ls $mountpoint after the failed ssshf.
answered Jul 27 '16 at 18:25
GilbertGilbert
46445
That was the problem here too.
– Dan Dascalescu
Jan 18 '17 at 22:04
This helped.. but first I had to kill a process that had the mount point openlsof | grep $mountpoint
– jsj
Nov 13 '17 at 0:08
@jsj that can be a good point.
– Gilbert
Nov 19 '17 at 0:39
add a comment |
After using sshfs on and off for years just got this error for the first time and found this page. All the "setup sshd" wasn't much of a help as ssh has been working.
However, a bit of testing found the solution. The problem occurred after a failed sshfs mount request with a bad hostname in it. As ls -l $mountpoint failed with this error I tried clearing the trouble with fusermount -u $mountpoint, and it worked!
After the failure I got the error on a simple ls $mountpoint after the failed ssshf.
answered Jul 27 '16 at 18:25
GilbertGilbert
46445
That was the problem here too.
– Dan Dascalescu
Jan 18 '17 at 22:04
This helped.. but first I had to kill a process that had the mount point openlsof | grep $mountpoint
– jsj
Nov 13 '17 at 0:08
@jsj that can be a good point.
– Gilbert
Nov 19 '17 at 0:39
add a comment |
After using sshfs on and off for years just got this error for the first time and found this page. All the "setup sshd" wasn't much of a help as ssh has been working.
However, a bit of testing found the solution. The problem occurred after a failed sshfs mount request with a bad hostname in it. As ls -l $mountpoint failed with this error I tried clearing the trouble with fusermount -u $mountpoint, and it worked!
After the failure I got the error on a simple ls $mountpoint after the failed ssshf.
answered Jul 27 '16 at 18:25
GilbertGilbert
46445
After using sshfs on and off for years just got this error for the first time and found this page. All the "setup sshd" wasn't much of a help as ssh has been working.
However, a bit of testing found the solution. The problem occurred after a failed sshfs mount request with a bad hostname in it. As ls -l $mountpoint failed with this error I tried clearing the trouble with fusermount -u $mountpoint, and it worked!
After the failure I got the error on a simple ls $mountpoint after the failed ssshf.
answered Jul 27 '16 at 18:25
GilbertGilbert
46445
answered Jul 27 '16 at 18:25
GilbertGilbert
46445
answered Jul 27 '16 at 18:25
GilbertGilbert
46445
answered Jul 27 '16 at 18:25
GilbertGilbert
46445
46445
That was the problem here too.
– Dan Dascalescu
Jan 18 '17 at 22:04
This helped.. but first I had to kill a process that had the mount point openlsof | grep $mountpoint
– jsj
Nov 13 '17 at 0:08
@jsj that can be a good point.
– Gilbert
Nov 19 '17 at 0:39
add a comment |
That was the problem here too.
– Dan Dascalescu
Jan 18 '17 at 22:04
This helped.. but first I had to kill a process that had the mount point openlsof | grep $mountpoint
– jsj
Nov 13 '17 at 0:08
@jsj that can be a good point.
– Gilbert
Nov 19 '17 at 0:39
That was the problem here too.
– Dan Dascalescu
Jan 18 '17 at 22:04
That was the problem here too.
– Dan Dascalescu
Jan 18 '17 at 22:04
This helped.. but first I had to kill a process that had the mount point open
lsof | grep $mountpoint– jsj
Nov 13 '17 at 0:08
This helped.. but first I had to kill a process that had the mount point open
lsof | grep $mountpoint– jsj
Nov 13 '17 at 0:08
@jsj that can be a good point.
– Gilbert
Nov 19 '17 at 0:39
@jsj that can be a good point.
– Gilbert
Nov 19 '17 at 0:39
add a comment |
I had this problem after using sshfs for some time. This answer is relevant only for situations where sshfs was already used successfully prior to the problem.
What usually causes this problem is that you terminated the connection sometime ago, and the system still has the /remote_mount mounted. First try doing:
sudo umount /remote_mount
and then attempt to connect again.
edited Sep 26 '16 at 8:39
countermode
5,28842044
answered Sep 26 '16 at 8:11
krsnik93krsnik93
12112
Why was this downvoted? That made it for me, thank U !!
– Campa
Feb 20 '18 at 11:47
This answer was the right one for me too
– CharlesB
Mar 30 '18 at 8:05
add a comment |
I had this problem after using sshfs for some time. This answer is relevant only for situations where sshfs was already used successfully prior to the problem.
What usually causes this problem is that you terminated the connection sometime ago, and the system still has the /remote_mount mounted. First try doing:
sudo umount /remote_mount
and then attempt to connect again.
edited Sep 26 '16 at 8:39
countermode
5,28842044
answered Sep 26 '16 at 8:11
krsnik93krsnik93
12112
Why was this downvoted? That made it for me, thank U !!
– Campa
Feb 20 '18 at 11:47
This answer was the right one for me too
– CharlesB
Mar 30 '18 at 8:05
add a comment |
I had this problem after using sshfs for some time. This answer is relevant only for situations where sshfs was already used successfully prior to the problem.
What usually causes this problem is that you terminated the connection sometime ago, and the system still has the /remote_mount mounted. First try doing:
sudo umount /remote_mount
and then attempt to connect again.
edited Sep 26 '16 at 8:39
countermode
5,28842044
answered Sep 26 '16 at 8:11
krsnik93krsnik93
12112
I had this problem after using sshfs for some time. This answer is relevant only for situations where sshfs was already used successfully prior to the problem.
What usually causes this problem is that you terminated the connection sometime ago, and the system still has the /remote_mount mounted. First try doing:
sudo umount /remote_mount
and then attempt to connect again.
edited Sep 26 '16 at 8:39
countermode
5,28842044
answered Sep 26 '16 at 8:11
krsnik93krsnik93
12112
edited Sep 26 '16 at 8:39
countermode
5,28842044
edited Sep 26 '16 at 8:39
countermode
5,28842044
edited Sep 26 '16 at 8:39
countermode
5,28842044
5,28842044
answered Sep 26 '16 at 8:11
krsnik93krsnik93
12112
answered Sep 26 '16 at 8:11
krsnik93krsnik93
12112
answered Sep 26 '16 at 8:11
krsnik93krsnik93
12112
12112
Why was this downvoted? That made it for me, thank U !!
– Campa
Feb 20 '18 at 11:47
This answer was the right one for me too
– CharlesB
Mar 30 '18 at 8:05
add a comment |
Why was this downvoted? That made it for me, thank U !!
– Campa
Feb 20 '18 at 11:47
This answer was the right one for me too
– CharlesB
Mar 30 '18 at 8:05
Why was this downvoted? That made it for me, thank U !!
– Campa
Feb 20 '18 at 11:47
Why was this downvoted? That made it for me, thank U !!
– Campa
Feb 20 '18 at 11:47
This answer was the right one for me too
– CharlesB
Mar 30 '18 at 8:05
This answer was the right one for me too
– CharlesB
Mar 30 '18 at 8:05
add a comment |
sudo umount /remote_mount - This worked. Thanks
answered 15 mins ago
meeeeeeeemeeeeeeee
1
New contributor
meeeeeeee is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
sudo umount /remote_mount - This worked. Thanks
answered 15 mins ago
meeeeeeeemeeeeeeee
1
New contributor
meeeeeeee is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
sudo umount /remote_mount - This worked. Thanks
answered 15 mins ago
meeeeeeeemeeeeeeee
1
New contributor
meeeeeeee is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
sudo umount /remote_mount - This worked. Thanks
answered 15 mins ago
meeeeeeeemeeeeeeee
1
New contributor
meeeeeeee is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 15 mins ago
meeeeeeeemeeeeeeee
1
New contributor
meeeeeeee is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 15 mins ago
meeeeeeeemeeeeeeee
1
answered 15 mins ago
meeeeeeeemeeeeeeee
1
1
New contributor
meeeeeeee is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
meeeeeeee is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
meeeeeeee is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f226546%2fsshfs-transport-endpoint-is-not-connected%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
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
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Post output of
ssh -v root@domain.com?– BAR
Aug 31 '15 at 8:58
question updated..
– clarkk
Aug 31 '15 at 9:03
Type
yesand try again.– BAR
Aug 31 '15 at 9:04
@BAR, after I did
ssh root@domain.comI deleted the old RSA key and now it works again.. (The server got a new IP address) Create an answer :)– clarkk
Aug 31 '15 at 9:20
Good to know it worked for you!
– BAR
Aug 31 '15 at 9:21