Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upload Failing & Losing Working File #7474

Closed
cyberduck opened this issue Oct 4, 2013 · 7 comments
Closed

Upload Failing & Losing Working File #7474

cyberduck opened this issue Oct 4, 2013 · 7 comments
Assignees
Labels
bug fixed ftp FTP Protocol Implementation
Milestone

Comments

@cyberduck
Copy link
Collaborator

d992de1 created the issue

Hey All, so every now and again (until the last few days, when it started happening several times an hour) Cyberduck gives me an Upload failed message when I save whatever file I'm editing with the message:

200TYPE is now 8-bit binary

NOOP
213 UTIME OK
TYPE I
200Zzz...
PASV 200 TYPE is now 8-bit binary

Hitting try again never works, so I hit cancel, close and reopen cyberduck, and all but the first 50-200 lines of the file I was working on are gone. This pretty much makes cyberduck unusable, but it seems to happen almost entirely on one server that I'm working in. (Using Brackets as my text editor by the way)

Any ideas? Let me know if there's more that I need to upload. It could totally be an issue with my server, but I'm pretty foreign to server management, so I really have no idea.

Transcript:

226-File successfully transferred
226 0.296 seconds (measured here), 193.41 Kbytes per second
NOOP
200 Zzz...
SITE CHMOD 644 /usm/wp-content/themes/usm/style.css
200 Permissions changed on /usm/wp-content/themes/usm/style.css
MFMT 20131004210353 /usm/wp-content/themes/usm/style.css
213 UTIME OK
NOOP
200 Zzz...
TYPE I
200 TYPE is now 8-bit binary
PASV
227 Entering Passive Mode (50,87,134,243,153,134)
STOR /usm/wp-content/themes/usm/style.css
150 Accepted data connection
ABOR
426 Transfer aborted
NOOP
226-Transfer aborted
226 0.043 seconds (measured here), 33.47 Kbytes per second
SITE CHMOD 644 /usm/wp-content/themes/usm/style.css
200 Zzz...
MFMT 20131004210356 /usm/wp-content/themes/usm/style.css
200 Permissions changed on /usm/wp-content/themes/usm/style.css
NOOP
213 UTIME OK
TYPE I
200 Zzz...
PASV
200 TYPE is now 8-bit binary

Apologies for the bad formatting too.

@cyberduck
Copy link
Collaborator Author

d992de1 commented

This probably isn't the right spot to post this either.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:1 mattgrosswork]:

This probably isn't the right spot to post this either.

That is the right place.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

In a7efc60. Please update to the latest snapshot build available.

@cyberduck
Copy link
Collaborator Author

d992de1 commented

Updating now, should I expect the issue to be fixed, or is this a testing and feedback thing?

Thanks

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:5 mattgrosswork]:

Updating now, should I expect the issue to be fixed, or is this a testing and feedback thing?

Thanks

It is expected to be fixed.

@cyberduck
Copy link
Collaborator Author

d992de1 commented

Well, it hasn't failed on me so far today. That's a good sign.

Thanks again.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:7 mattgrosswork]:

Well, it hasn't failed on me so far today. That's a good sign.

Thanks again.

Thanks for the feedback.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug fixed ftp FTP Protocol Implementation
Projects
None yet
Development

No branches or pull requests

2 participants