Filelog is disabled after a fresh installation and must be enabled first. The second logging possibility is logging to file. Closing the admin interface deletes the complete buffered log. There's no facility to turn it off or move it elsewhere. The screen log occupies the upper part of the admin interface window, directly below the toolbar. Note that additional internal status messages don't follow this scheme. Log text: Commands received, replies sent, status messages and more.User name of the account using this connection, (not logged in) is shown before the login process is completed.Connection ID (in brackets): every new connection will get a unique ID, this aids in tracking one special connection only.If you want logs when no user is logged on, don't want to leave the admin interface running or want to track large logs, you need to use file logging (see below). The screen log is enabled automatically when the admin interface is running, you don't have to do anything more. And, for performance reasons, there's only a finite number of lines logged.

1.2.5 Special case: Using log size limit and rotating logfiles togetherįileZilla Server, like the client, includes two means of logging, screen and file log.Īs FileZilla Server is split in two parts (service and administration interface), the screen log won't work if the admin interface isn't running, for example if no user is logged on.

Filezilla logs in but then disconnects