Why does Cyberduck FTP keep disconnecting on my Mac? I was uploading 37 image files to a client folder, and the transfer stopped twice after the screen went dark. The server still appears in my bookmarks. Is there a Mac sleep or Cyberduck setting I should check?
The common mistake is to consider the FTP support on the macOS as the question of what application is better in a universal sense. I do not think that it is a useful distinction. Both approaches are capable of doing the same fundamental job, but the procedure for accessing and managing the files differs.
For repeated access, I would also consider Finder CloudMounter. It mounts the remote storage as a drive, which means the files can be reached through Finder rather than through a dedicated FTP client window. That changes the working method, not the underlying purpose.
Establish the basic FTP procedure
Cyberduck is adequate for simple FTP needs of a regular macOS user. I would start by launching New Connection and choosing the FTP option. What I would have to enter are the simple fields such as server address, username, and password. After filling these in and establishing the connection, I would be able to see the remote folders in Cyberduck’s window.
What follows is the standard file management procedure. I would browse the folder structure and transfer the files from my computer to the remote server and vice versa. There is nothing in this process that would make me feel that the remote storage has to be mounted within Finder’s window. Instead, I keep it opened in Cyberduck, which is a standalone utility for handling file transfers.
I would also check the connection type that the server offers to establish before proceeding. If the server supports TLS, it is possible to use the secure FTPS standard instead of regular FTP. It is up to the server to support this type of connection, so the responsibility is not on the client-side.
This much is sufficient for the occasional file transfer. The procedure is clear-cut, the connection data is entered in one place, and remote folders are kept strictly in another area of the macOS’s native file management utility. How convenient this is to organize depends on how often the connection is established.
Compare the daily file workflow
For a more frequent FTP user, my consideration would turn to the daily file management workflow and what would be more convenient in the long term. In this regard, CloudMounter’s main advantage is represented by the possibility to access the remote files as if they were located on a local drive. This way, the remote storage can be manipulated directly within Finder’s interface.
This might be more convenient for some workflows where FTP is integrated into the daily file management operations. Instead of using a separate utility every time I need to access, browse, and transfer the files between servers, I would be able to use the unified interface of Finder that also handles macOS’s local storage.
The way I would organize my file management workflows would depend on my estimated frequency of use. If I were to open an occasional FTP or FTPS connection to transfer files, Cyberduck would suffice with a minimal learning curve. Meanwhile, for a daily user, CloudMounter’s ability to act as Finder extension would be more convenient than managing another separate utility.
If transfers stop only when the Mac sleeps, macOS is suspending network activity; if they stop while you’re working, suspect Wi-Fi or a server timeout. A bookmark only saves connection details, so keep the Mac awake during uploads; for recurring transfers, I’d use CloudMounter.
The bookmark is a red herring. It stores the login details and server address, not a live connection, so it will remain there after a transfer dies.
A dark screen does not always mean the Mac is asleep, but your timing strongly points to idle sleep. Run the same upload while preventing sleep temporarily. The quickest test is Terminal:
caffeinate -i
Leave that window open during the transfer, then press Control-C when finished. The display can still switch off, but the Mac should remain awake. If the upload completes, you have found the cause without changing your power settings permanently.
In Cyberduck, open the Transfers window and resume the interrupted job instead of starting the whole batch again. FTP can resume partial uploads, although the server has to support it. Check the destination afterward because a failed transfer can leave a partial file with the correct name.
If it disconnects even with caffeinate running, then look elsewhere:
- Enable repeated attempts for failed network tasks in Cyberduck’s Connection preferences.
- Increase the connection timeout modestly. A huge timeout only hides problems.
- Try Ethernet or another Wi-Fi network to rule out a brief wireless drop.
- Ask the host whether it limits session length or simultaneous FTP connections.
- Use SFTP if the server offers it. Do not simply select it in Cyberduck unless the host has actually enabled it.
I still reach for CloudMounter when several remote accounts need to stay organized, but it is not a cure for this problem. macOS sleep can interrupt its connections too, and background copies may make it less obvious whether every file has finished. First run the awake test. That will tell you whether you need a different client at all.
A dark display is only a clue, so check Cyberduck’s transfer log after the next failure. If the server is closing the session, CloudMounter is excellent at reconnecting the remote mount after a brief network drop, though no FTP client can keep uploading while the Mac is fully asleep.
Changing FTP clients is premature. First check whether the transfer stops on the same filename each time. If it does, the dark screen may be a coincidence. A problematic filename, server quota, folder permission, or file-size rule can stop a batch at a repeatable point.
Try this in order:
- Plug the Mac into power and temporarily prevent automatic sleep in System Settings under Battery. The display may turn off without affecting the upload, but the computer itself must stay awake.
- Upload the batch again and note the last completed file plus any FTP error shown in Cyberduck’s transfer details.
- If it fails on a different file, check Wi-Fi stability and server timeouts. If it fails on the same file, rename that file using plain letters and numbers, then upload it separately.
- If individual files work but the batch does not, ask the host whether the account has a storage quota, connection limit, or FTP session timeout.
Pay attention to the server response rather than the bookmark. Messages such as “quota exceeded,” “permission denied,” or “too many connections” point to the hosting account. A generic lost-connection message that occurs only after actual system sleep points back to macOS power settings.
CloudMounter changes how you reach the server, but it will not bypass quotas, permissions, or a sleeping Mac. I would identify whether the failure follows the Mac’s sleep state or follows a particular file before installing anything else.
Don’t assume the dark screen is the cause just because the timing matches. FTP usually creates a separate data connection for each file, so a batch of many images can expose router, firewall, or hosting limits that a single large transfer would not.
As a comparison test, put copies of the images into one ZIP archive and upload that while the Mac stays awake. If the archive succeeds but the individual files fail, look at passive FTP settings, connection limits, or server-side filtering. If both transfers stop when the computer sleeps, it is a macOS power issue rather than Cyberduck.
Switching to CloudMounter would change the interface, but it would still use the same server and network path. The more useful comparison is FTP versus SFTP, if the host supports SFTP. SFTP uses a different connection model and is generally less troublesome through modern routers. Keep Cyberduck, select the protocol the host actually provides, and compare the results before installing another client.
Nobody’s asked whether Cyberduck was actually the front app during the upload or whether you switched to Mail, a browser, whatever, while it ran. That matters more than people think. macOS has App Nap, which throttles apps it decides are idle in the background, and a long upload window sitting behind other apps is exactly the kind of thing it targets. If you kick off the batch and then go do something else, the transfer can crawl or drop even with the Mac wide awake. Open Cyberduck in Finder, hit Get Info, and there’s a checkbox to prevent App Nap for that app. Worth ruling out before you touch power settings.
The caffeinate suggestion from @capt_owl is solid and I’d run it, but pair it with the App Nap check because they cover two different failure modes. One keeps the machine awake, the other stops the OS from starving the client while it’s out of focus. And @kate_x’s point about watching whether it stops on the same file is the smartest thing in this thread, honestly. A batch dying at a repeatable spot is almost never a sleep issue.
For what it’s worth, when I’ve got a folder I keep pushing to the same server, I mount it with CloudMounter and copy through Finder instead of babysitting a transfer window. Doesn’t fix a sleeping Mac or a server quota, but it takes the ‘did the client fall asleep’ question off the table since you’re just doing a normal file copy. Sort out the sleep and App Nap behavior first though, otherwise you’re just moving the same problem to a different interface.