So I've started developing a project that will run on rPi-3B+. I've run into a problem with SSHFS.
Right now I'd really like to be able to edit, and commit, the git repo stored on the Pi from my text editor, atom, on my laptop over SSHFS.
The first time I mounted the file system it worked fine running this command:
sudo sshfs -o allow_other email@example.com: ../../mnt/ceresPi2/
Then I started getting this error in terminal:
read: Connection reset by peer
This thread in this forum from a few years ago was all I found but then I noticed a comment on it from less than a month ago: Connection reset by peer using sshfs
I've done all the steps suggested by everyone in that thread and am still getting the same result.
The second to last comment, by eddygeek, talks about a debug command which gave me the same result as their self:
sshfs -odebug,sshfs_debug,loglevel=debug -o Ciphers=arcfour -o Compression=no -o allow_root -o transform_symlinks localhost:/ /mnt/your_mount_point
command-line line 0: Bad SSH2 cipher spec 'arcfour'. read: Connection reset by peer
They claim this doesn't happen in fedora but does in ubuntu without an explanation.
I can't seem to find a reason for that online. Would any of you have encountered this recently on Ubuntu or know of a solution?
What's stranger is that I have a second pi running different software but I can mount it to '/mnt/ceresPi1/' without a problem. I can mount it to the same '/mnt/ceresPi2/' pount as well. The Pi giving the issues won't mount to the 'ceresPi1' mount point either, nor to a fresh one @'/mnt/ceresPi3'.
It doesn't even get to the point of asking me for the user password, as I'm not using the saved keys at the moment, since that's just another failure point while I figure this part out.
My stop gap measure is to push a commit to my gitHub repo and then pull it down to the pi server since SSH still works but not SSHFS. obviously this is not ideal.