FileZilla failing after a macOS update
When FileZilla stops working on a Mac, check three things in this order: the version number, the last line of the Message log, and the protocol and port in Site Manager. The current stable release is 3.71.1, dated August 26, 2026, and its release notes list a fix for crashes on macOS 27 when the system language is not English. If FileZilla quits on launch after a macOS update, installing that version is the first step. If it launches but cannot connect, the Message log almost always names the stage where it stops, and each stage has a short list of causes.
This guide follows that order. Every version detail below comes from FileZilla's own version history, read on October 9, 2026.
Step one: check the version before anything else
Open FileZilla and choose About FileZilla from the FileZilla menu. Compare the number with the latest release on the macOS download page, which on October 9, 2026 showed 3.71.1 and the requirement "Requires macOS 10.13.2 or newer".
The version matters because several recent releases changed behavior that looks like a connection fault:
| Version | Date | Change that can look like "not working" |
|---|---|---|
| 3.71.1 | 2026-08-26 | Works around a macOS 27 bug where a non-English locale triggers crashes in AppKit |
| 3.71.0 | 2026-08-19 | Malformed paths on servers set to the DOS server type are now rejected early |
| 3.70.6 | 2026-06-04 | Automatic detection of the FTP server type was removed; unusual server types must be set by hand |
| 3.70.5 | 2026-05-07 | A compatibility flags page was added to Site Manager for SFTP |
| 3.70.0 | 2026-04-09 | SFTP now runs on the new fzssh library (introduced in the release candidates) |
If FileZilla crashes the moment it opens on macOS 27 and the Mac is set to Japanese, German, or any other non-English language, that is the AppKit issue fixed in 3.71.1. Reinstalling an older copy will not help. Download the current version and replace the app in the Applications folder.
If the problem began right after updating FileZilla itself, rather than macOS, look at the 3.70.x lines. A server that connected for years through automatic server type detection may now need its type set explicitly, and an old SFTP server may respond differently to the new SSH implementation. Both are covered below.
Read the Message log, not the error dialog
The pane at the top of the FileZilla window is the Message log. It records every step of the connection, and the last few lines say where it stopped. The pop-up error is usually the least specific part of the story.
| Last lines in the log | Stage that failed | Most likely causes |
|---|---|---|
| "Connection timed out after 20 seconds of inactivity" or "Could not connect to server" | Reaching the server | Wrong host or port, firewall, VPN, Local Network permission |
| "Connection refused by server" | Reaching the server | Wrong port or protocol, service not running |
| "Authentication failed" or "Critical error: Could not connect to server" right after login | Logging in | Wrong user name or password, key not accepted, account locked |
| Connected, then "Failed to retrieve directory listing" | Opening the data channel | Passive or active mode, firewall on the data ports |
| Listing shows strange paths or is empty | Reading the listing | Server type, path format |
The fix depends entirely on which row matches. A timeout and an authentication failure have nothing in common, and changing passive mode will not repair a wrong password. Copy the last ten lines of the log before changing any settings, so it is possible to compare after each change.
Cannot reach the server: protocol, port, and network
Most "could not connect" errors come from a mismatch between what the server offers and what FileZilla tries.
Protocol and port. Plain FTP and FTPS normally use port 21. SFTP is a different protocol that runs over SSH, normally on port 22. In Site Manager, the Protocol menu must match the server: choosing "FTP - File Transfer Protocol" against an SFTP-only server, or the reverse, ends in a refusal or a timeout. In the Quickconnect bar, typing sftp://example.com in the Host field forces SFTP. Hosting providers often state which one they use on their control panel; when in doubt, try SFTP on port 22 first, since many hosts have switched off plain FTP.
Too many connections. Some shared hosts allow only a few connections per user. FileZilla opens extra connections for transfers, and the server rejects the excess. In Site Manager, open the Transfer Settings tab, turn on "Limit number of simultaneous connections", and set it to 1 or 2 to test.
Firewalls and VPNs. A VPN client, a corporate network, or a security app can block outgoing ports other than web traffic. Disconnect the VPN and try again, or try from a different network such as a phone hotspot. If it works there, the network is the cause, not FileZilla.
Local Network permission. Since macOS added a Local Network privacy setting, apps need permission to reach devices on the same network, such as a NAS or a development server in the office. If FileZilla can reach internet servers but not a machine on the local network, open Apple menu > System Settings > Privacy & Security > Local Network and check that FileZilla is switched on. Apple describes this setting in Control access to your local network on Mac.
Connected, but the directory listing fails
When the log shows a successful login followed by "Failed to retrieve directory listing", the control connection worked and the data connection did not. FTP uses a second connection for listings and file transfers, and that second connection is the one firewalls and routers break.
Passive mode solves most of these cases, because the client opens the data connection outward instead of waiting for the server to connect back. Check it in two places:
- In the global settings: open Settings from the FileZilla menu, go to Connection > FTP, and choose Passive as the transfer mode.
- Per site: in Site Manager, open the Transfer Settings tab and set Transfer mode to Passive. A site set to Active overrides the global choice.
If passive mode still fails, the server's passive port range may be blocked by its own firewall. That is a server-side setting, so the host's support team needs to confirm the range is open.
A different symptom, a listing that appears but shows odd paths, empty folders, or names that cannot be opened, points to the server type. Since version 3.70.6, FileZilla no longer detects unusual server types automatically. For mainframe, VMS, or DOS-style servers, open Site Manager, select the site, go to the Advanced tab, and choose the correct Server type. Ordinary Linux and Windows hosting does not need this.
SFTP problems after FileZilla 3.70
FileZilla 3.70.0 moved SFTP onto a new library called fzssh, and the following releases added a series of compatibility fixes. The release notes describe them in plain terms: handling servers that send empty long names, servers that cannot cope with very large receive windows, and servers that "blatantly violate the SSH specifications".
In practice, an older or unusual SFTP server that worked with FileZilla 3.69 may fail with a recent version, and the fix is usually already in a newer release. Three things are worth doing:
- Update to 3.71.1. Version 3.71.1 improved how keyboard-interactive login requests are treated as a simple password prompt, and earlier 3.70.x releases fixed several authentication edge cases.
- Check the compatibility flags. Version 3.70.5 added a page of SFTP compatibility flags to Site Manager, and 3.70.6 added a flag to ignore invalid bits in file attribute flags from non-compliant servers. If the server is old embedded hardware, such as a router or a NAS, these flags are designed for it.
- Check the key format. Version 3.71.0 updated fzssh to support additional algorithms and key file formats. If a private key is rejected, confirm it is listed under Settings > Connection > SFTP, and that the server accepts that key type.
If SFTP works from Terminal but not from FileZilla, report the server's software and version on the FileZilla forum along with the Message log. The developers have been fixing these cases release by release.
Test the connection outside FileZilla
When it is unclear whether the problem is FileZilla, the Mac, or the server, Terminal answers it in a minute. macOS includes the tools.
Check that the port is reachable:
nc -vz example.com 22
"succeeded" means the network path is open. A timeout means something between the Mac and the server is blocking it, and no FileZilla setting will change that.
Then try an actual SFTP login:
sftp -P 22 [email protected]
If this logs in and ls lists files, the server and network are fine, and the problem is in the FileZilla site settings. Compare host, port, protocol, user name, and key one by one. If Terminal also fails, the cause is on the server or the account, and the host's support team can see the rejected attempts in their logs.
A local-side problem shows up differently. If the left pane in FileZilla cannot open Desktop, Documents, or Downloads, macOS is withholding access. Open System Settings > Privacy & Security > Files & Folders and allow FileZilla for those locations, as Apple explains in Control access to files and folders on Mac.
If you decide to switch clients
Sometimes the practical answer is a different tool, at least for one server. Prices below were read from each vendor's site on October 9, 2026.
| Client | Price | Requirements | Notes |
|---|---|---|---|
| FileZilla | Free (GPL) | macOS 10.13.2 or later | Version 3.71.1 is current |
| Cyberduck | Free (GPL), donations accepted | macOS or Windows | Also connects to cloud storage |
| Transmit 5 | $45 one-time | macOS 13.0 or later | Native Mac client from Panic |
| ForkLift 4 | From $19.95 (personal) | macOS 14.6 | Dual-pane file manager with SFTP and FTP |
Sources: Cyberduck, Transmit, ForkLift store.
There is also the route that skips a graphical client altogether. For people who already work in Terminal, sftp, scp, and rsync cover uploads and downloads, and a command-line AI agent can write the exact command when the syntax is not memorized. The friction then is keeping the local folder and the terminal in view together. A file manager with a built-in terminal ties each folder in its sidebar to its own terminal, so the upload command runs in the folder that is already open, and the file list stays visible beside it. The features page lists what that setup includes, and the comparison page is candid about what it does not replace.
What to change first
Update FileZilla to 3.71.1, reproduce the failure once, and read the last lines of the Message log to find the stage. If the server answers in Terminal but not in FileZilla, the problem is a site setting; if Terminal-based transfers turn out to be enough, keeping the folder and terminal together in Atriens removes the separate client entirely.
Frequently asked questions
Why does FileZilla crash immediately on macOS 27?
FileZilla 3.71.1, released on August 26, 2026, works around a macOS 27 bug in which a non-English system language causes crashes in AppKit. Earlier versions can quit on launch on a Mac set to another language. Download 3.71.1 from the official site and replace the old app.
What does "Failed to retrieve directory listing" mean?
The login worked, but the separate data connection used for listings did not. Set the transfer mode to Passive in Settings under Connection > FTP, and in the site's Transfer Settings tab in Site Manager. If it still fails, ask the host whether its passive port range is open.
Which port is right, 21 or 22?
Port 21 is for FTP and FTPS. Port 22 is for SFTP, which runs over SSH. The Protocol menu in Site Manager must match the port. If the host does not say which it supports, try SFTP on port 22 first, since many hosts have disabled plain FTP.
FileZilla connects to internet servers but not to a NAS on the same network. Why?
macOS requires apps to have permission to reach devices on the local network. Open System Settings > Privacy & Security > Local Network and turn FileZilla on. If FileZilla is not listed, connect once so macOS asks, then allow it.