Servers

Commander opens FTP, FTPS and SFTP servers right in a panel. You browse, copy, rename and delete there with the same keys as on your disk, and copy between a server and your disk, or between two servers.

Adding a server

On Places, the + on the SERVERS header opens New server:

Field What it is
Type SFTP, FTPS or FTP
Host The server’s name or address
Port 22 for SFTP, 21 for FTP and FTPS, 990 for implicit FTPS
TLS For FTPS: Explicit or Implicit
Path The folder it opens in; empty, the top
User Your login; anonymous for public FTP
Password Optional; asked when needed if left empty
SSH key For SFTP; empty means the SSH agent, then ~/.ssh/id_*
Transfer mode For FTP and FTPS: Passive or Active
Bookmark name How it is listed; the host if left empty
  • Use ~/.ssh/config (SFTP) fills the fields from a host in your SSH config: its HostName, User, Port and IdentityFile. Commander doesn’t connect through ProxyJump or ProxyCommand.
  • Test connection connects and says how it got in, such as Connected to builds.example.com as deploy with the SSH agent. An empty Path is filled with the folder the server starts you in.
  • Add to Bookmarks saves the server without connecting.

For FTP, a grey line reminds you that FTP sends the password and the files unencrypted.

Connecting

Enter on a server in Places connects and opens its folder. The panel shows Reading… until the first answer, and the path shows the server’s name, with its address in the tooltip.

  • A password is asked in the status bar: builds.example.com needs a password:. Once the server accepts it, it is saved.
  • A key with a passphrase asks for the passphrase the same way, only when nothing else let you in. The passphrase is never saved; it lasts while the connection does.
  • Both panels on one server share one connection, and everything it has listed stays in memory while the connection lives. Going back into a folder shows it at once, then reads it again.
  • A lost connection reconnects by itself at the next thing you do. When that fails too, the panel keeps what it showed and the status bar says why.

The connection closes when no panel, tab or task shows the server any more.

Signing in

  • FTP and FTPS: user and password, or anonymous with an empty password.
  • SFTP tries, in this order: every key your SSH agent holds, then the key file you named (or ~/.ssh/id_ed25519, id_ecdsa and id_rsa), then the password. Key files in OpenSSH and PEM formats work, ed25519 included, on every system.

Commander answers a server’s sign-in questions with the password. A second factor, such as a one-time code, isn’t supported.

Trusting a server

FTPS checks the server’s certificate with your system. When the system doesn’t trust it, for example a certificate the server made for itself, Server certificate shows who it is for, who issued it, how long it is valid and its SHA-256 fingerprint, with what is wrong in red. Trust remembers it for that server; a certificate that changes later asks again.

SFTP checks the server’s key against your ~/.ssh/known_hosts and Commander’s own list. An unknown key shows its type and fingerprint, and Trust adds it to Commander’s list. Your own known_hosts is read, never written.

A key that changed is shown with the old one, and can’t be trusted from the dialog: a changed key can mean someone is in between. If you know the server was reinstalled, remove the old line from the file the dialog names.

Esc or closing the dialog doesn’t connect.

Passwords

Passwords are saved where only your computer can read them:

  • On a Mac, in the keychain, as Cuberact Commander. Preferences ▸ Data ▸ Passwords can keep them in Commander’s settings file instead.
  • On Windows and Linux, in Commander’s settings file, sealed with a key that belongs to this computer and this user. Copied to another computer, they can’t be opened; each password is asked once there.

Commander never shows a password: Detail says only in the keychain, sealed in places.properties or not saved. Passwords never go into the logs.

Working on a server

What works, as on your disk:

  • Browsing, with the columns Name, Ext, Size and Modified, and Perms over SFTP.
  • Copy and Move to and from your disk and between servers. A move within one server is a single rename.
  • Rename, Multi Rename, New Folder and New File.
  • Delete Permanently ⇧F8.
  • View F3, up to 16 MB, with Read all for more.
  • Find Files, by name and by content.
  • Compare Files and Compare and Synchronize.
  • Over SFTP, Detail ▸ Attributes sets permissions and the modified date.

What doesn’t:

  • Move to Trash: a server has no trash.
  • Open in Text Editor F4 and Open Terminal Here F9: they need a folder on this computer.
  • Compute Size, and New Symlink.
  • Archives on a server don’t open in the panel. Copy the archive to your disk first.
  • Enter on a file does nothing, except a picture, which opens in the viewer.

Folders on a server are not watched. A folder is read again when you go into it, or after Commander changed something in it. To see changes someone else made, go out and back in.

Transfers

  • Files are always sent in binary, byte for byte.
  • An interrupted file starts over; transfers don’t resume halfway. A connection lost in the middle of a file is retried once by itself.
  • SFTP keeps permissions and dates.
  • FTP keeps the date where the server allows it (ProFTPD, Pure-FTPd and FileZilla Server do, vsftpd doesn’t). Elsewhere an uploaded file takes the time of the upload.
  • Two copy tasks to one FTP server run side by side, each on its own connection.
  • File names go as UTF-8 where the server supports it.

Editing and removing a server

  • Detail ⌘I on the server shows its setup; Edit… opens the same form, with Save.
  • F2 renames its bookmark.
  • F8 reads Remove Bookmark. Its password goes from the keychain too, unless another bookmark of the same server still uses it. The trust you gave its certificate or key stays.
  • ⌘D inside a server’s folder adds a bookmark that opens right there.

A fresh Commander comes with one server, ftp.gnu.org, a public FTP server to try things on. Remove it whenever you like.

When something goes wrong

  • No answer: Commander waits 10 seconds for a connection and 30 seconds for each answer.
  • On a Mac, macOS may ask whether Commander may reach your Local Network the first time you connect to a server at home or at work. See macOS permissions.
  • Files missing on an FTP server: some servers leave names starting with a dot out of their listing.
  • Behind a router, passive mode, the default, works: Commander ignores the inner address a server behind NAT reports and uses the one it connected to.
  • FTPS to a Windows server slows down or drops after about a hundred files: Windows Defender Firewall’s FTP filter cuts long encrypted sessions. Commander logs in again by itself; on the server, Set-NetFirewallSetting -EnableStatefulFtp False in an administrator PowerShell fixes it.