Fixing SSHFS in Mac OS X El Capitan (10.11)

If you are like me and use SSHFS everyday, you’ve recently noticed that it stopped working on OS X El Capitan. The problem is that fuse4x is no longer supported, and does not work in this new version. The solution is to get rid of fuse4x and install OSXFUSE with its own version of SSHFS. Another issue is that macports also stops working with the update, so we have to fix macports before we can get rid of the old fuse4x and SSHFS ports. If you doing a clean install on El Capitan, just skip to step 3. If you’re updating from Yosemite or earlier, start here:

Step 1: Make macports work again:

Follow Chris Knight’s instructions for reinstalling macports on El Capitan:

https://www.ghostwheel.com/merlin/Personal/notes/2015/09/14/installing-macports-on-os-x-10-11-el-capitan/

Step 2: Uninstall sshfs and fuse4x from macports:

Step 3: Install OSXFuse and SSHFS:

Just go over to http://osxfuse.github.io/ and grab both packages It might be necessary to reboot to make SSHFS start working.

You’re done!

  • Marco

    Could you setup auto-mount of SSHFS mount point on El Captain? I am struggling with this…

    • I have never used auto-mount, so I’m afraid I can’t help out

    • Odinsey

      use automator to mount your sshfs @ login
      create an application started when opening your session

    • Matthew

      Auto-mount via this article (https://superuser.com/questions/830746/how-to-use-etc-fstab-and-or-automount-with-sshfs-on-osx) worked on Yosemite, but on El Capitan, it breaks, even when using the same OSXFUSE/SSHFS modules. On El Capitan, I just have a shell script to manually mount my SSHFS mounts, and use a temporary file buffer so it is run only once in my bashrc. Miguel’s suggestion would also work. Also, using automator or my approach resolves issues where only root can access the mounts, even when “allow_other,defer_permissions” flags are set. Don’t waste your time with auto_master/auto-mount.