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

Could not parse response code. Server Reply: 50 #9775

Closed
cyberduck opened this issue Dec 2, 2016 · 1 comment
Closed

Could not parse response code. Server Reply: 50 #9775

cyberduck opened this issue Dec 2, 2016 · 1 comment
Labels
bug ftp high priority thirdparty

Comments

@cyberduck
Copy link
Collaborator

cyberduck commented Dec 2, 2016

b325f33 created the issue

I had to reinstall cyberduck and when trying to connect to server that worked before i get the error
Could not parse response code. Server Reply: 50

with

SYST
215 UNIX Type: L8
TYPE I
200 Type set to I
PASV
227 Entering Passive Mode (37,228,219,97,217,248).
RETR <DIR>
PORT <IP>,217,120
TYPE I
200 Type set to I
PASV
227 Entering Passive Mode (37,228,219,97,219,14).
RETR <DIR>
PORT <IP>,122
QUIT
QUIT
221 Goodbye.
QUIT
451 Transfer aborted. Broken pipe
QUIT
200 PORT command successful

@cyberduck
Copy link
Collaborator Author

cyberduck commented Jan 10, 2017

@dkocher commented

This looks like a firewall in your network is blocking the file transfer initiated in passive mode from the server.

@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 ftp high priority thirdparty
Projects
None yet
Development

No branches or pull requests

1 participant