Testing a connection and reading its log
Check that a connection works, read what happened to it, and what Folia Files does when a server drops or slows down.
The Mac App Store edition is coming soon. The website edition has everything. Compare the editions
Test a connection
In the Connections window, Test Connection (under the editor) tries the connection without mounting it. The result shows under the options, in green or in red, with the reason in plain words: login refused, port closed, server not answering, address not found, a key that can't be read, TLS required… The test is offered for the connections made through rclone (SFTP, FTP, S3, clouds); SMB, WebDAV, NFS and AFP shares are tested by mounting them.
The connection's log
Every connection keeps a log of what Folia Files did and saw: mounts and how long they took, unmounts, remounts, checks that were slow or got no answer, the network going and coming back, the Mac sleeping and waking, tests, files sent back to the server, copies interrupted. For connections made through rclone, rclone's own lines are mixed in.
Open it:
- right-click the connection in the sidebar or in the Connections window › Connection Log;
- or click Log under its editor.
It opens in a tab of the window. There:
- Copy Log puts it on the clipboard, to send it to us or to your server's administrator;
- rclone Log in Finder shows rclone's log file;
- Detailed rclone log: rclone also logs what it reads, writes and retries. It applies from the next mount.
The log of the previous mount is kept too, so what happened before a drop is still there after the connection came back. The log keeps the last 500 lines per connection, until you quit Folia Files.
When a connection drops
A server or a cloud can stop answering for a while: a network hiccup, a server under load, a cloud slowing down. Here is what happens:
- If a mount doesn't answer, Folia Files waits and checks again 20 seconds later before deciding it's dead: a busy server is never cut off during a long copy.
- macOS itself gives up on a mount that stays silent too long (30 seconds for a server, 2 minutes for a cloud) and removes it. Folia Files then mounts it again by itself, quietly, and says « Reconnected to “…” ».
- If the server stays out of reach, you're told once; Folia Files tries again at the next wake or network change.
Folia Files never waits for a frozen server on its own window: the server's folders load in the background, and the rest of the app stays responsive.
Common causes
- « Permission denied » on a folder or a file: the server refuses your user. It's not a dropped connection.
- A mount that takes long to appear: a cloud gets 60 seconds to mount (a server 25). Large Google Drive accounts can be slow the first time.
- Changes made elsewhere don't show: servers send no change notifications; press ⌘R to read the folder again.
- A VPN: if the server is only reachable through it, let the connection open the VPN first.