-
Notifications
You must be signed in to change notification settings - Fork 55
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
Common client connection errors when using server getting started guide #108
Comments
Not sure if any windows clients have this error. Not sure what clients you use to test. I hope to get a chance to look into this at the weekend so I thought I'd document it here. But if anything jumps out you from the logs , that will be good. |
Interesting how they all seem to raise slightly different errors. |
Transmit:client:
server:
Unfortunately for transmit, multiline response is valid by ftp rfc's. So it is a transmit issue. Cyberduck:Looks like the same issue, but client tries to do same things twice (I don't know why). Finder:Looks like same thing, but we do not see finder logs though. Anyway it tries Filezilla:Probably the problem is in interpreting |
So, FileZilla will accept the connection when the server is as:
|
Yes, the problem with filezilla is that it looks like it does not respect |
Wouldn't I had a vague memory of this problem - that's why I spun up a VM on 172.16.11.120, to avoid the client and server being on the same IP. Anyway, that doesn't seem to have helped with transmit or Cyberduck (same errors when binding the server to 172.16.11.120 as I had with |
|
But, as I said before, |
Moving the commentary from #85 over here.
When I use the Getting started guide to spin up a server, the server isn't accessible from many common clients - particularly these MacOS ones.
Success cases
✅ - FTP CLI (on Ubuntu)
✅ - Firefox (72.0.2 (64-bit) on MacOS)
On Ubuntu 18.04 I've installed aioftp and am running
python -m aioftp --memory --family ipv4
to start ther server.ftp command line
The client outputs
and on the server I see:
Firefox
I can connect OK, the server shows:
Failure cases
❌ - FTP CLI (on MacOS)
❌ - Transmit (on MacOS)
❌ - Cyberduck (on MacOS)
❌ - Filezilla (on MacOS)
❌ - Finder (on MacOS)
Transmit
Client log:
And on the server side:
Cyberduck
Client log:
And on the server side:
Finder
The server log output:
And god knows where to look for the finder logs :)
Filezilla
The client reports:
While the server outputs:
The text was updated successfully, but these errors were encountered: