Transport endpoint is not connected in SSHFS

Question

After reinstalling the server I can not mount it:

sshfs [email protected]:/var /remote_mount
fuse: bad mount point `/remote_mount': Transport endpoint is not connected

When I SSH, I get an error:

# ssh [email protected]
The authenticity of host 'example.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)?

@BAR, after I did `ssh [email protected]` 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 09:20
Same error here, but `ssh [email protected]` works flawlessly, so sshd seems to be set up properly. Any ideas? — fbmd, Jun 27 '16 at 19:06

Gilbert · Answer 1 · 2021-12-21T01:35:44.330

63

This error popped up for me after I had been using sshfs on and off for years. A search found this page but all the "setup sshd" answers were not much help as sshfs had been working well until it suddenly didn't and ssh worked just fine to other locations.

However, after a bit of frustrating poking and testing I found the solution. The problem started with a sshfs mount failing from a bad hostname in it. As ls -l $mountpoint failed with this error I tried clearing the trouble with fusermount -u $mountpoint, and the mount started to work again!

Even a simple ls $mountpoint made the error after the failed sshfs.

edited Dec 21 '21 at 01:35

answered Jul 27 '16 at 18:25

Gilbert

814
6
6

1

That was the problem here too. – Dan Dascalescu Jan 18 '17 at 22:04
2

This helped.. but first I had to kill a process that had the mount point open `lsof | grep $mountpoint` – jsj Nov 13 '17 at 00:08
@jsj that can be a good point. – Gilbert Nov 19 '17 at 00:39

score 30 · Answer 2 · edited Sep 26 '16 at 08:39

30

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 08:39

countermode

7,373
5
31
58

answered Sep 26 '16 at 08:11

krsnik93

411
4
3

2

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 08:05
This makes sense and worked for me, I got the same error when clicking the mounted directory in Nautilus "Files" Browser. I ran the umount command and it reset the state so it could be mounted again! – Elijah Lynn Oct 29 '19 at 21:30
Great answer. Thanks ! – Ahmed Abdelazim Jan 06 '20 at 14:03
This is resonable and correct i think – munish May 28 '20 at 11:40
umount: /remote_mount: target is busy – Rudy A. Hernandez Jan 01 '23 at 22:32

Transport endpoint is not connected in SSHFS

2 Answers2