Contrary to screen log, file log is not enabled by default. Since version 3.2.0-rc1, FileZilla includes the possibility of logging to a file. Using the Debug menu in the FileZilla settings, you can adjust the verbosity in five levels (0-4) and enable the display of raw directory listings.

Only change it if you're asked for it, change it back after the problem has been solved. Please don't change the verbosity of the logs for normal operation of FileZilla. Please note that the last two only appear if verbose logs are activated (using the Debug menu, see below)

Log text: Commands sent, status messages and moreīy default the log pane is located directly below the QuickConnect bar, but you can adjust the location using the interface settings:.

Description: Status, Command, Response, Trace etc.

To show complete, unabbreviated logs, you can right-click the log and select 'Show detailed logs'. Logs are usually abbreviated unless an error occurs. Please note that the screen log is limited to a finite number of lines displayed, long logs may scroll out of the screen and can't be recalled.

It is always enabled, but the pane can be hidden using the View menu. The first logging type is the screen log. The following chapters will shortly explain, what you'll need to do if you're asked to 'Please post a log'. FileZilla includes two ways of logging all communication with the server, which essentially consists of commands sent by the client and server replies.

Filezilla command line new tab