How to reset SSH connection to a peer?
SSHFS version 2.8 FUSE library version: 2.9.7 nullpath_ok: 0 nopath: 0 utime_omit_ok: 0 executing < -x> <-a> <-oClearAllForwardings=yes> <-ologlevel=debug> <-oIdentityFile=~/.ssh/id_rsa> <-oCiphers=arcfour> <-oCompression=no> <-2> < -s> command-line line 0: Bad SSH2 cipher spec ‘arcfour’. read: Connection reset by peer
Why is ARCFOUR disabled in recent versions of SSH?
Usually after reinstalling raspbian. What’s strange is that my known hosts was accepted when just running normal ssh to the same host. That part I still don’t get. arcfour has been disabled by default in recent versions of SSH. Thanks for contributing an answer to Unix & Linux Stack Exchange!
What should I do if my SSH connection fails?
Since this error message is the default one when ssh connection fails, the most generic answer (per @peterph comment) is to investigate using at least -odebug: sshfs -odebug,sshfs_debug,loglevel=debug
Is there a problem with sshfs on atom?
Hellow world! 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:
What to do if SSH connection does not work?
A good test is to ssh to the machine before running the sshfs command, if that does not even work sshfs will not work either. I got this error and tried the methods above and failed at making it work. The problem was the server was not accepting ssh at port 22.
How to fix SSH connection reset with fstab?
You can fix this by telling fstab what identity file/ssh key to use while trying to connect: To get real debug output you need to add both sshfs_debug and debug options to the mount: In my case I discovered that my machine was only listed in .ssh/config, so it was unresolvable for root.
Why is my SSH connection reset after 30 seconds?
In my case it was the server interface not being up after a long time on startup. The server is connected to a Cisco switch port with trunk mode. Since any trunk port will do various checks before actually become UP (usually more than 30 seconds), this has resulted in the above connection reset error message.
Do you need ssh port to use SSHFS?
Rule of thumb: if ssh works, sshfs will work. The easiest way is to make sure that ~/.ssh/config has an entry for the remote host with the user, port, etc provided. I figure out that I needed to use the ssh port, oh wow stupid me.