Linux – sshfs is failing with “remote host has disconnected”

centoslinuxsftpsshsshfs

I'm running sshfs with the following:

sshfs basicuser@192.168.1.111:/var/www/myapp /home/basicuser/code -o sftp_server="/usr/bin/sudo /usr/libexec/openssh/sftp-server"

I have also created RSA keys so I can log in via ssh without password prompt (I tested this and it works).

I have also added the user to the sudoers file to run the sftp-server without a password:

basicuser  ALL=(ALL)  NOPASSWD:  /usr/libexec/openssh/sftp-server

What could be causing this error? How do I figure that out?

Edit

I am trying to mount a folder on the local computer from the remote server. On the remote server, only root has read/write permissions to that folder.

Remote folder: /var/www/myapp (is root only read/write)

Best Answer

You get a lot more information about the failure if you run sshfs as:

sshfs -odebug,sshfs_debug,loglevel=debug user@host ...

Usually this will give you something a lot more helpful to debug the problem.

Related Solutions

What’s missing from the sftp chroot setup

Looks like the ChrootDirectory should point to one level ABOVE the home directory.

So since guest's home is /var/www/uploads/guest, then the ChrootDirectory should point to /var/www/uploads

That's a MAYBE.... another thought occurred to me:

You manually installed the newer openssh, did you remove the old version? Where did the new version get installed? sometimes, if you're not careful, new stuff will get installed into /usr/local/ instead of /usr, meaning the sftp enabled server is reading its config files from /usr/local/etc/ssh/... instead of the expected /etc/ssh/...

Something to check at least.

Debian – chrooted sftp user with write permissions to /var/www

What I've done is to chroot my users to their home directories and then used mount --bind to create a link to it in their home directories.

I then used setfacl to make sure www-data maintans write permissions on new files in the directory. This effect will recurse into /var/www, which is what you want to do.

By setting g+s on the directory, all new files and directories created within it will inherit the group ownership from its parent.

useradd someuser
mkdir -p /home/someuser/www
mount --bind /var/www /home/someuser/www
chmod g+s /home/someuser/www
chown -R someuser:www-data /home/someuser/www
setfacl -d -m g::rwx /home/someuser/www

That should do the trick.

Make your mounts persistent

Obviously you want your mounts to still be there when you reboot the server. It's as simple as adding the mounts to your /etc/fstab. Not all providers let you touch this file, but most do.

Just add lines like this:

/var/www        /home/someuser/www        none        bind        0        0

You might want to reboot to make sure it works.

Best Answer

Related Solutions

What’s missing from the sftp chroot setup

Debian – chrooted sftp user with write permissions to /var/www

Make your mounts persistent

Related Question