I've just tested using the latest FileZilla server (0.9.39 beta) and the latest version of wyBuild (2.6.14) and the uploads work fine.
Have you tried uploading to other servers? Does this error happen there as well?
After uploading a large (15mb) wyu file (endobiz3.3test.all.to.3.3.6.wyu) to the server the file fully uploads then all it has left to upload is the "wyserver.wys" file, which is a tiny file, that file upload fails, I am using a filezilla server, the latest version, I have set all timeouts on the server to 0 (infinite). When I try to perform the same ftp transfer using my filezilla *client* it works fine. So I guess its an in issue with the ftp client you are using. The filezilla server log just says that the client disconnected, not that it timed out. Any ideas?
I've just tested using the latest FileZilla server (0.9.39 beta) and the latest version of wyBuild (2.6.14) and the uploads work fine.
Have you tried uploading to other servers? Does this error happen there as well?
Ok, I dont know why, but it seems that I managed to fix the issue by going to user settings on the FileZilla server admin console and setting "Speed Limits" to no limit and also "Bypassing server download\upload speeds"
The strange thing is that the file was always uploading, but just after it finished uploading this large 13mb it would fail, so I think its some kind of timeout which I managed to slip under, but it could be that I did something else. Any suggestions\explanations would be appreciated.
The other thing worth mentioning is that I was always able to upload the same file using the filezilla client
Could it be that the wyBuild software has a timeout somewhere when uploading? Or could it be that something restricts large FTP uploads?
Can you tell me what speed limit you set it to get the upload to fail? Also, I can't find the "Bypassing server download\upload speeds" option in the FileZilla server.
Its under user settings\speed limits, I previously had it on default settings.
Also if you are testing it, then I would suggest you test using on offsite FTP, since the issue only started to occur when I switched from our in-house server to on offsite one.