We bundle edtFTPnet/PRO into our automated deployment product, Octopus Deploy. A number of customers have reported problems with our FTP sync feature when using Windows Azure websites with FTPS.
I've posted a gist containing:
1) The code to reproduce (just enter a license key and change the sync directory) - I even included credentials for an active Azure website so you can fully reproduce
2) The output I get (with logging enabled)
https://gist.github.com/PaulStovell/22a ... 9d64ca24a5
It seems like when issuing the LIST commands, connections eventually time out. Sometimes they work, but if I terminate the app part way through the connection, then run it again, I'm able to reproduce it 9 times out of 10.
Now I don't think this is limited to edtFTPnet/PRO, as FileZilla encounters similar sporadic errors when uploading files, and freezes when listing sometimes.
Response: 550 The supplied message is incomplete. The signature was not verified.
Error: File transfer failed after transferring 2,076,672 bytes in 26 seconds
Using FTP instead of FTPS also seems to be fine, so I'm assuming this is a problem with the FTP server that Windows Azure use for website publishing. But I wanted to share it with you in case there's a magical setting I can set that will make it "just work" :)
Some more info on what errors people are seeing is here:
https://octopus-deploy.tenderapp.com/di ... o-redeploy
And a question: we currently set an 8-hour Timeout on the FTP connection's sockets, the assumption was if people were uploading large files we'd want to give them plenty of time. But this means that failures like the ones above result in our app appearing to "hang" rather than timeout. Is it safe to set the Timeout property to a small value, say 10 minutes, without it preventing file transfers that might take an hour to complete?
