FileZilla Forums

FileZilla is not intended to be used for automated tasks. Use a scriptable ftp client like lftp, ftp.exe, Robo-FTP, ScriptFTP, etc.

You can use the built-in ftp command with a script and then use Task Scheduler to automate it:
http://support.microsoft.com/kb/96269

The admin interface protocol is undocumented and was never intended to be interfaced by anything other than the built-in widget. You'd have to examine and decipher the source code to determine the protocol for it. I believe botg has said that the networkable feature of the admin interface was added ...

Already requested. Implemented when time allows if the dev chooses to do so.

Note that user/password embedding in URIs is bad security practice, so will probably not be how the system works or how it works by default.

Are these text files that are being truncated? Try transferring in binary mode.

Do other FTP clients result in truncation?

Does the network configuration wizard complete without error?

If you're running into the PHP time-out, increase the time-out in php.ini.

This is a PHP problem. It's unrelated to FTP or FileZilla. This isn't the best place to ask this question.

First, clear the cache of the browser you're using. Next, try entering the specific page name in the address bar. The page is 'index.htm' that you're uploading. Make sure that there is no 'index.html', 'home.html', 'default.html' or other common default page. Technically, your page should be 'index....

Ah, no. FTP has no copy command. You can often move files (using the rename command) but file copying is right out.

You'd need an SFTP or SSH session to do more advanced file management. The latter is almost universally unavailable on a shared host.

FTP *does* allow for server-to-server transfers by use of FXP (file exchange protocol) which is mentioned in RFC 959 (it's most often used in FTP clustering, AFAIK). However, most servers have the feature disabled because of bounce attack issues. FileZilla Client doesn't support FXP mode transfers, ...

Actually, here, the CRC32 checks built into the archive file (.zip and .rar files have them) are your verification. Gzip, bzip2 and 7z files also have CRC32 information. Note that CRC32 verification is generally sufficient to detect inadvertent errors, but it's not sufficient to detect intended flaw...

The easiest way would be to find an FTP server and client that support the XMD5, XCRC, or XSHA command. FileZilla Server and Client don't support the command because they're not RFC standard. If the server supports it, then it should list this command in response to the FEAT command sent at login (c...

There's a problem on the server end or with the network. Confirm by trying a different PC or a different FTP client.

Honestly, I'd hope that by the time we no longer need UPnP or NAT-PMP that we're no longer using FTP. Even if there's an FTPv2 that uses a single port I'd be happy.

SFTP is as different from FTP or FTPS as it can get. They are completely unrelated protocols. I'd avoid FreeFTPd in favor of FreeSSHd. The former hasn't had a release in almost 3 years. It's dead. When FileZilla Server returns to active development, I can't say if it will be developed as an SFTP ser...

Most FTP daemons allow for directories to be set up for blind drop or blind get, but it's not always a feature. Often it's just an artifact of how permissions settings work. They can be made to function in that way, but it was never designed with that in mind. The primary problem with a blind drop i...

POSIX permissions are supported because originally all FTP systems were POSIX systems (Unix, Linux, BSD, etc.). That's what FTP was designed for. Actually, FTP predates POSIX by over a decade. Also, SITE CHMOD is not part of the FTP standard, strictly speaking FTP has no means at all to set file pe...