Support guide
macFUSEGui Troubleshooting
Use this page when a mount refuses to connect, a previously healthy remote becomes stale after sleep, or macOS blocks the app on first launch. The goal is to isolate whether the failure is in prerequisites, auth, mount state, or recovery behavior.
1. Prerequisite failures
If the app cannot mount anything, verify that both macFUSE and sshfs are installed. The app depends on them for the actual filesystem and transport work.
brew install --cask macFUSE
brew install gromgit/fuse/sshfs-mac2. First-launch approval problems
Unsigned public builds require a one-time approval. If the app bounces or appears blocked, open it from Finder with right-click or Control-click and choose Open.
Then inspect System Settings > Privacy & Security for the approval prompt.
3. Authentication and host problems
- Confirm hostname, username, and remote path are correct.
- Retest credentials from the app instead of assuming an old saved remote still matches the server.
- If you pasted a password, resave it cleanly so you are not debugging a copied typo.
4. Mount-point conflicts
A healthy SSH connection can still fail if the local mount point collides with another remote or points at a stale mount path. Use a unique local mount directory for each remote and disconnect stale mounts before retrying.
5. Sleep, wake, and network recovery issues
macFUSEGui is designed to recover desired remotes after sleep, wake, or network restoration. If a remote stays stale, disconnect it, verify the network path is actually back, then reconnect.
If the problem repeats, capture diagnostics so you can see which recovery stage failed.
6. Stale or broken mounts
If Finder shows a remote but the path no longer responds, treat it as a stale mount problem. Disconnect from the app first. If that does not clear it, re-open the app, verify the mount state, and avoid deleting the remote until the stale mount is gone.
7. Use diagnostics before guessing
The diagnostics snapshot exists to replace guesswork. Copy it when you hit repeated failures so you can see environment readiness, remote state, and recent mount or recovery events in one place.