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

5.3.0 closing connections #9805

Closed
cyberduck opened this issue Jan 12, 2017 · 10 comments
Closed

5.3.0 closing connections #9805

cyberduck opened this issue Jan 12, 2017 · 10 comments

Comments

@cyberduck
Copy link
Collaborator

cyberduck commented Jan 12, 2017

6662a50 created the issue

Listing directory current failed.

Broken pipe (Write failed). The connection attempt was rejected. The server may be down, or your network may not be properly configured.

I am getting this message whenever I try to access a directory that has been left open for more than a couple of minutes. This is new behaviour on 5.3.0

@cyberduck
Copy link
Collaborator Author

cyberduck commented Jan 13, 2017

@dkocher commented

Thanks for the issue report. What protocol do you connect with?

@cyberduck
Copy link
Collaborator Author

cyberduck commented Jan 13, 2017

6662a50 commented

FTP, sorry should have mentioned that.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Jan 13, 2017

@dkocher commented

Can you check you are running snapshot build 5.3.0.23440 or later.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Jan 13, 2017

6662a50 commented

I had reverted to 5.2.2 so I just downloaded a new copy. It's 5.3.0 (22987). Below your recommendation.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Jan 13, 2017

@dkocher commented

In 8172834. We have just pushed a new snapshot build. Please try to update and let us know if that build resolves the issue.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Jan 13, 2017

6662a50 commented

Same problem, I'm afraid.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Jan 16, 2017

@ylangisc commented

Fixed in e78a463.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Jan 16, 2017

6662a50 commented

23112 has just gone up but no 23556 yet.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Jan 16, 2017

@dkocher commented

Replying to [comment:14 rogjack]:

23112 has just gone up but no 23556 yet.
The build numbers do not match. Please test with 5.3.0.23112.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Jan 17, 2017

6662a50 commented

OK, that seems to have fixed it, thanks.

@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.
Projects
None yet
Development

No branches or pull requests

2 participants