Can connect with other FTP clients, but not Cyberduck #16882
Unanswered
carlssonsweden
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Short story:
I am able to connect to an FTP server with other FTP clients, but not Cyberduck. I can see that it logs in, but after saying "Listing Directory" for appr 20 seconds a dialogue tells me that the connection failed.
Long story:
We have a Filezilla FTP server on a Windows Server 2022. The server is a data centre server that is hosted by our IT supplier.
Yesterday a client told us that he couldn't connect with FTP anymore. We tried with a couple of FTP clients and none worked.
Today I logged in to the server itself, and tried to open the Filezilla Admin centre. Couldn't connect.
Talked to the supplier, that could log in Filezilla, but with a different port (why was the port different?).
They looked at it, and after a while it worked. But not with Cyberduck!?
I can connect from Finder in macOS and with the app Transmit, but with Cyberduck I get some kind of timeout. Looking at the logs tells me something about directory paths. But why does it work with Transmit?
Something tells me that the supplier have made some changes (why did it suddenly stop working, and why was the port number for Filezilla changed?), but they will of course not admit that.
Can someone please tell me why it doesn't work with Cyberduck? Log extract is attached.
Thanks,
Andreas
cyberduck_log.txt
Beta Was this translation helpful? Give feedback.
All reactions