Getting Cyberduck working again without a reinstall

When Cyberduck stops working on a Mac, the fastest fix is almost never a reinstall. Cyberduck keeps its preferences in ~/Library/Preferences/ch.sudo.cyberduck.plist and its bookmarks and history in a separate support folder, and dragging the app to the Trash leaves both in place. A fresh copy reads the same settings and fails the same way. The better order is: work out which of four faults you have, read the log Cyberduck is already writing, run the transcript if it is a connection problem, and then apply the fix that matches. As of October 9, 2026, the current release on the Cyberduck download page is version 9.5.4, which requires macOS 10.13 or later. Everything below is drawn from Cyberduck's own help pages, checked on that date.

Sort the symptom first

"Not working" covers four problems that share nothing except the app name. Each has a different first move.

What you see Most likely area First thing to check
Nothing happens when you open the app, or it quits at once Launch, preferences, conflicting software Crash report, then preferences
The bookmark spins and fails, or the password is rejected Login, keys, server settings Transcript and sftp from Terminal
It connects, but uploads stall or fail partway Connect mode, timeouts, server limits Log file and connection settings
Names show odd characters, or folders look wrong Text encoding, server listing Text encoding setting

If the app opens and a different server works fine, the problem is almost certainly not Cyberduck itself. It is the server, the account, or something in between. The help documentation says as much on its support page: if you have trouble connecting or your login credentials are not valid, the hosting provider is the right place to ask. That one test, trying a second server or a second protocol, saves a lot of time.

Read what Cyberduck already wrote down

Cyberduck logs constantly, and most people never look. On macOS the log lives at ~/Library/Logs/Cyberduck/cyberduck.log. The support page lists two quick ways to reach it.

  • In Cyberduck, open Preferences, then Connection, and use the Show button next to the log setting.
  • Open Console, then go to Reports, Log Reports, and pick cyberduck.log.

The same page notes that Cyberduck keeps the current log plus compressed copies of the last five cycled logs, named cyberduck-*.log.zip. That matters when the failure happened yesterday and the current log has already moved on.

If the default log is too thin, turn on Enable debug log in Preferences, Connection. Reproduce the failure once, then read the end of the file. Turn debug logging off again afterwards, because the file grows quickly.

For an app that will not open at all, the log may be empty. In that case the crash report is the evidence. Cyberduck's documentation gives the location as ~/Library/Logs/DiagnosticReports/, with files named Cyberduck_*.ips on macOS 12 and later. If a fresh file appears there each time you try to open the app, the crash is real and repeatable, and the top of that report usually names the part that failed.

Run the transcript for connection problems

The log tells you what Cyberduck decided. The transcript tells you what the server actually said. Cyberduck's support page gives the exact command. Open Terminal and run:

log stream --predicate '(process == "Cyberduck") && (category == "transcript")' --level info

Leave that Terminal window open, switch to Cyberduck, and try the connection again. Every request and response is printed in the window. You are looking for the last line before things go wrong: a refused password, a rejected key, a timeout, a certificate warning.

Next, take Cyberduck out of the picture. The SFTP section of the documentation suggests verifying access with the plain sftp command:

sftp username@example-host

If this also fails, the problem is the account or the server, and no setting in Cyberduck will fix it. If sftp connects and Cyberduck does not, the difference is in how Cyberduck is configured, and the next sections apply.

Login and key failures with known fixes

The SFTP page of the Cyberduck documentation has a Known Issues section. Four of its entries account for a large share of "cannot connect" reports.

Too many authentication failures

If you run an SSH agent with many keys loaded, Cyberduck may offer every key in turn until the server gives up with "Too many authentication failures". The documented fixes are:

  • Select the specific key in the bookmark under SSH Private Key.
  • Add IdentitiesOnly yes for that host in ~/.ssh/config, so only the named key is tried.
  • On the server side, raise MaxAuthTries, if you control the server.

Invalid packet, indicated length too large

An error like "Invalid packet: indicated length 1114795883 too large" usually means something on the server is printing text when the session starts. The documentation lists the common causes: an echo line in a shell start-up file such as .bashrc, a server message telling you to log in as a different user, or an account that has no SSH access at all. Check the user name first, then any start-up script that prints output.

Kex timeout

This appears when connecting for the first time to a device with a slow processor, such as a small NAS. The documented fix is to raise the value in Preferences, Connection, Timeout.

Malformed known_hosts

Cyberduck refuses to connect if your ~/.ssh/known_hosts file contains malformed entries. The documentation suggests renaming the file so it is recreated, or editing it to remove the broken lines. Renaming is safer than deleting, because you can put it back.

Transfers that start and then fail

When the connection works but transfers stall, the cause is usually in the path between you and the server rather than in Cyberduck.

For plain FTP, the connect mode matters. The FTP page explains that you can choose Active (PORT) or Passive (PASV) mode per bookmark or when opening a connection. Many firewalls and home routers only allow one of the two, so a listing that loads but a transfer that never starts is a classic sign of the wrong mode. Switch it in the bookmark and try again.

The same page has two other details that explain a lot of failures:

  • Cyberduck supports FTP with explicit TLS. Implicit FTPS with no negotiation is not supported.
  • TLS 1.0 and 1.1 are not supported from Cyberduck 8.1.0 onwards. An old server that only offers those versions will fail to connect from a current release.

If file names appear with broken characters on an FTP server, that is a separate issue. The documentation suggests changing the text encoding under View, Text Encoding, or per bookmark, and trying UTF-8, ISO-8859-1 and Windows-1252 in turn.

Two features described on the Cyberduck home page help with flaky transfers. You can limit the number of concurrent transfers, and you can resume both interrupted downloads and uploads. Some shared hosting plans cap how many connections one account may open at once. When Cyberduck opens several connections in parallel, the extra ones are refused and those files fail while others succeed. Lowering the number of concurrent transfers to one or two is a quick way to test this. If a single large file keeps dropping, resuming it from the transfer window avoids starting again from zero.

For large uploads that fail partway, check the debug log for the exact point of failure. A timeout, a disconnect from the server, and a quota error all look like "the upload failed" in the transfer window, but they need different fixes.

Reset settings without losing your bookmarks

If the app crashes on launch or behaves strangely across every server, the preferences file is the next suspect. The Cyberduck FAQ gives the two locations that matter:

  • Preferences: ~/Library/Preferences/ch.sudo.cyberduck.plist
  • Bookmarks, history and connection profiles: ~/Library/Group Containers/G69SCX94XU.duck/Library/Application Support/duck/

The FAQ also notes that the second folder is shared with Cyberduck CLI and Mountain Duck. That is worth knowing before you delete anything there.

A careful reset looks like this. Quit Cyberduck first, then in Terminal:

defaults export ch.sudo.cyberduck ~/Desktop/cyberduck-prefs-backup.plist
defaults delete ch.sudo.cyberduck

The first line saves a copy of your current preferences. The second clears them, so Cyberduck starts with defaults next time. Using defaults rather than deleting the file in Finder avoids a common trap where macOS keeps serving a cached copy of the old settings. Your bookmarks are not touched, because they live in the other folder.

If the app now opens, add your custom settings back one at a time. If it still crashes, the preferences were not the cause, and the crash report from the earlier section is the thing to send with a bug report.

Conflicts with other software

The FAQ includes a short Incompatibilities list. As of October 9, 2026 it names three items:

  • WindowDragon, which Cyberduck is not compatible with.
  • Sophos Anti-Virus on-access scanning.
  • Browser Chooser 2, which stops the browser step of OAuth sign-in from working.

If any of these are installed, test with them disabled before changing anything else. The OAuth case is easy to miss. If signing in to a cloud service such as Google Drive or Dropbox opens no browser window, or the window never hands control back to Cyberduck, a browser-picker utility is a likely reason.

It also helps to know which version you have. The FAQ explains that the Mac App Store copy is sold at a fixed price with no donation prompt, while the website version is free and asks for an optional donation. On October 9, 2026 the Mac App Store listing showed $23.99. Both are the same software, but they update through different channels, so compare the version number with 9.5.4 before assuming you have the latest fixes.

When to change versions, and what to send for help

Only after the steps above does a version change make sense. Preferences, Update lets you switch the update feed to snapshot or beta builds, according to the FAQ. That is useful when a fix for your exact problem has landed but not yet been released. Going back to the last version that worked for you is the other option. Before doing that, search the public issue tracker on GitHub for your error message, because a known regression is often already reported there with a workaround.

If you need to ask for help, the useful package is small:

  • The Cyberduck version and your macOS version.
  • The relevant part of cyberduck.log with debug logging on.
  • The transcript lines from the failed attempt, with passwords removed.
  • The crash report, if the app is crashing.

The support page also points out that people using the free download without a registration key get best-effort support. Clear evidence makes that effort go much further.

What to change first

Start with the transcript and a plain sftp test. Together they tell you in two minutes whether the fault is the server or Cyberduck. If you find yourself switching between Finder, Terminal and an FTP client for every check, a file manager with a built-in terminal lets you run those commands next to the folders you are moving, and Atriens shows how that kind of tool compares with others.

Frequently asked questions

Why does reinstalling Cyberduck not fix the problem?

Removing the app does not remove its settings. Preferences stay in ~/Library/Preferences/ch.sudo.cyberduck.plist and bookmarks stay in the Group Containers support folder. A new copy reads the same files and behaves the same way. Reset the preferences with defaults delete ch.sudo.cyberduck after exporting a backup instead.

Where is the Cyberduck log file on a Mac?

The log is at ~/Library/Logs/Cyberduck/cyberduck.log. You can reveal it from Preferences, Connection, or find it in Console under Reports, Log Reports. Cyberduck also keeps compressed copies of the last five cycled logs in the same folder.

Cyberduck says "Too many authentication failures". What does that mean?

Your SSH agent is offering several keys, and the server stops accepting attempts before the right one is tried. Choose the correct key in the bookmark under SSH Private Key, or add IdentitiesOnly yes for that host in ~/.ssh/config. If you manage the server, raising MaxAuthTries also helps.

Is the Mac App Store version of Cyberduck different from the free download?

The software is the same. The website version is free with an optional donation, and the Mac App Store version is sold at a fixed price without a donation prompt, which was $23.99 on October 9, 2026. They update through different channels, so check the version number when comparing behavior.

Why does Cyberduck connect to an FTP server but never finish a transfer?

The most common cause is the FTP connect mode. Many firewalls allow only Active or only Passive mode, so the folder listing loads but the data connection for the transfer fails. Change the connect mode in the bookmark, and check the debug log for the exact error if switching does not help.

Back to all posts