Can't transfer files properly (0 bytes) and display issues

[gtilflm]

So, this is a new issue as of about 1 week ago. Up until this time, Filezilla has worked fine.

There are three issues here...
1.) When I upload a file, it uploads, but shows as having 0 bytes. There really is a file there and it really is 0 bytes because the file I just uploaded fails to work properly.
* I can download files without issue.
* I can upload files via the webhost's file manager.
* This happened before I updated to the newest version of FZ and also after I've upgraded.
* Webhost says windows firewall is the problem, but FZ has access through the firewall and port 21 is specifically open.

2.) When I download a file, sometimes it works properly and sometimes it only downloads part of the files. Interestingly, after a successful file download, I can then upload a file successfully. Overall, the upload/download issues seem to be intermittent.

3.) When I initially connect and also when I enter subdirs., not all the files and folders display.
* Upon one or more refreshes, they tend to show up.
* See attachments for a better understanding of this.

This is probably unrelated, but while trying to figure this out, I updated Notepad ++. After that, things worked for a short time, but then reverted back to failing.

I've also uninstalled and reinstalled FZ several times. Interesting thing about the reinstall process... Upon re-install, FZ somehow remembers my login information and sites in the site manager. If it was properly uninstalled, wouldn't it not know my previous login data?

Thanks.

[botg]

Can you please post a complete and unmodified Log of such an upload?

[gtilflm]

Well, after running CCleaner and Malwarebytes, it seems that the problem has resolved itself. I don't exactly know what the solution is/was, but if the issue returns, I'll update this post.

Thanks!

[gtilflm]

Well, I first posted about this about 1 year ago to the day and the issue has returned. I've run CCleaner and Malwarebytes and it doesn't seem to have fixed the issue this time. Below are a couple screenshots of message log data. The main thing is that the log records the data being uploaded, but the file shows as 0 bytes and it is in fact 0 bytes on the server.

Any thoughts on this?

[botg]

Look into the log. The server returns code 226, indicating success, yet the accompanying description says failure. In other words, the server is broken. Please contact your server administrator or server hosting provider for assistance so that the server can be replaced with a more compliant one.

[gtilflm]

Hi and thanks for replying. Here's some additional info...

1.) I had already called webhost and their people said they could use FZ just fine and upload/download to my site.
2.) I can successfully use FZ on a different computer.
3.) I can upload files successfully via the webhost's file manager in cPanel.

Therefore, it doesn't seem to be the server. Any other thoughts on this one? Need more logs?

Thanks again!

[boco]

1) and 2) They/you just don't trigger the bug in the FTP server that way. But that doesn't mean it's not there. The server is still broken; without a valid error reply code FileZilla will never notice the transfer failed, cause it cannot read the descriptions (these are for humans only). That will prevent it from taking appropriate action (retrying/resuming the transfer).

3) cPanel is not using FTP. Apples and oranges.

[gtilflm]

Ok. To help (maybe?), I've attached two additional log files in .txt format. I've also got my webhost looking into things.

log1.txt is from the computer I regularly use (a Vista machine).
log2.txt is from a different computer that has FZ installed on it (a Win. 7 machine).

Is this helpful at all?

[botg]

Nothing new in those logs. One shows the problem, the other doesn't. No indication why that is.

[gtilflm]

After consulting with a computer friend of mine, I have begun using SFTP and connecting via port 2222. That seems to be working at present. I'm still not sure why connecting via regular FTP is suddenly failing. Everything was fine on Dec. 3. Then I started having these issues on Dec. 6 (although the issue could have started anywhere in the range of Dec. 3 night to Dec. 6).

Does the fact that it seems to be working with SFTP give any further indication of what the problem may be?

Also, when I quick connect to the last server used, it will connect via regular FTP using port 21 instead of the newly specified settings of SFTP using port 2222. Any ideas on why the quick connect reverts to previous settings?

Thanks.

[botg]

Does the fact that it seems to be working with SFTP give any further indication of what the problem may be?

No.

Also, when I quick connect to the last server used, it will connect via regular FTP using port 21 instead of the newly specified settings of SFTP using port 2222.

How exactly are you performing that action?

[gtilflm]

How exactly are you performing that action?

I click the "R" button. See attached image.

[botg]

If you make changes to a saved site in the site manage, you need to connect through the site manager at least once. The reconnect button does not care about changes to stored sites, it always uses the last used parameters.

[gtilflm]

Right. Strangely, it seems to be working now when it wasn't earlier.

Thanks for the support!