Uploaded files at 0 bytes

Need help with FileZilla Client? Something does not work as expected? In this forum you may find an answer.

Moderator: Project members

Post Reply
Message
Author
SteeleR
500 Command not understood
Posts: 2
Joined: 2019-04-10 14:48

Uploaded files at 0 bytes

#1 Post by SteeleR » 2019-04-10 14:53

Hello, since yesterday filezilla started uploading the files at empty. What I found so far under Windows 10 64 bit:

- works with files less that 100 byes or of the sort
- tried on several hostings and it has the same problem everywhere
- other FTP programs work correctly
- tried another network connection and the problem persists
- downgraded from 3.41.2 to 3.41.1 and the problem persists
- tried disabling NOD32 and the problem persist
- windows defender is disabled
- tried active/passive mode and forced UTF-8 and the problem persists

when the file is uploaded it does not give any errors but a success:
Status: File transfer successful, transferred 13,655 bytes in 1 second

when the file is slightly bigger I get an error and still a 0 bytes file after several confirmation messages:
Response: 150 Accepted data connection
Error: Received TLS alert from the server: Bad record MAC (20)
Response: 226-Error during read from data connection
Response: 226 Transfer aborted


any ideas of what the issue might be or how to fix it?

User avatar
botg
Site Admin
Posts: 31982
Joined: 2004-02-23 20:49
First name: Tim
Last name: Kosse
Contact:

Re: Uploaded files at 0 bytes

#2 Post by botg » 2019-04-10 21:49

The server is on the fritz. Reply codes starting with 2 mean success, yet the text sent by the server accompanying this success speaks of an error.

Contact your server administrator or server hosting provider and demand to have the server fixed.

SteeleR
500 Command not understood
Posts: 2
Joined: 2019-04-10 14:48

Re: Uploaded files at 0 bytes

#3 Post by SteeleR » 2019-04-10 22:30

this happens on several servers and only with filezille for the last 2 days. Other FTP programs work so it doesn't seem like a server related issue.
I haven't updated any of the setting of the filezilla before that. Probably just the latest update was installed - 3.41.2

Post Reply