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

Error opening data socket #5168

Closed
cyberduck opened this issue Sep 9, 2010 · 15 comments
Closed

Error opening data socket #5168

cyberduck opened this issue Sep 9, 2010 · 15 comments
Labels
bug duplicate ftp FTP Protocol Implementation
Milestone

Comments

@cyberduck
Copy link
Collaborator

c548095 created the issue

After uploading the recent update, I'm being prompted constantly about certificate issues with my server. After clicking that I do want to continue the upload it cranks for awhile, and then I get the following message:

FTP Error: Upload failed
I won't open a connection to 192.168.1.102 (only to 24.147.240.17)

Being stubborn, I keep clicking Try Again, and eventually it goes, but it's extremely frustrating (particularly when on a deadline).

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Try to change the FTP connect mode to passive.

@cyberduck
Copy link
Collaborator Author

cb14edc commented

Replying to [comment:1 dkocher]:

Try to change the FTP connect mode to passive.

This problem is not closed yet. I and others have the same problem. See ticket #5179.

What is the solution? Hitting try again time and time again is not a solution I intend to use.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

#5179 closed as duplicate.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

#5167 closed as duplicate.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Many having issues with this. Have to look into it.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

See also #5200, #5198, #5179, #5199, #5195, #5139.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

It looks like this issue is caused when changing the connection protocol to FTP-TLS instead of plain FTP.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:9 dkocher]:

It looks like this issue is caused when changing the connection protocol to FTP-TLS instead of plain FTP.

Some people are possibly hitting a interoperability issue with ProFTPD documented in #5087. Opening the data socket using passive connect mode (PASV) fails and the fallback to active mode (PORT) fails for most configurations. Hence the error message. Users should switch back to plain FTP connections. Choose FTP (File Transfer Protocol) in the bookmark protocol setting. Most users hit by this compatibility issue have been asked to secure the connection because support for TLS was detected upon negogiating the connection. Refer to switch to secure connection prompt.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

If the above does not apply, make sure to check you have checked Use Passive FTP Mode (PASV) in the system preferences. Refer to FTP Connect Mode in the wiki.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Closing as duplicate for #5087 as the root cause of the issue.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

As of a9e0ef6 the original error is reported and not the error from the fallback mode.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

#5138 closed as duplicate.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

#5285 closed as duplicate.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

#5209 closed as duplicate.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Duplicate for #5385. Will add proper fallback logic if the server denies PORT command.

@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 duplicate ftp FTP Protocol Implementation
Projects
None yet
Development

No branches or pull requests

1 participant