It doesn't look to be connected. Can you scroll down in the status panel at the top?If you look at the last line in the output on the top, it DOES say connected for the last status message.
This is a joke right?If you highly need sFTP did you try to run any Docker service for that?
I am having the same problem. Anyone resolve this?
No, it is not. It is not a joke.This is a joke right?
Just I see there a lot of user complains sFTP (server?!) is very hard to install on Mac now
There is zero configuration required to enable the built in sFTP server - just enable "Remote Login" in the Sharing pane of system preferences.so, Docker might be an option then.
This makes zero sense. The built in SSH server (which provides sftp) authenticates connections against the macOS user database.But in general isolated service (Docker virtualised container) is better (for your private use) than your Mac running sFTP (one more possible hole in security).
Yes there's clearly something else wrong for those who said they have a problem, and thus far there's zero evidence that the problem is anything other than their SFTP client software.Or there is also something else what I don't follow for sFTP.
What's that got to do with the price of fish?P.S. I'm running Nginx Docker image for a small project online and it deals quite good.
If that was simple to users that subject might not exist. But some users complained it didn't run smooth for them.There is zero configuration required to enable the built in sFTP server - just enable "Remote Login" in the Sharing pane of system preferences.
It grants access only to those files (mounted volumes). The other host's files are never accessible.Docker container to provide SFTP, with access to the Mac's files is running as "you" and gets access to those files
There is not a problem to mount host authorised ssh keys file to Docker container.built in SSH server (which provides sftp) authenticates connections against the macOS user database
The OP or others having a problem with an SFTP client is not necessarily indicative of any problem with the built in SFTP server. It's exactly the same SFTP server that would be running in any Docker image: OpenSSH.If that was simple to users that subject might not exist. But some users complained it didn't run smooth for them.
You missed the point I was making: the built in SFTP server uses the underlying filesystem permissions, so by default only your account has access to your home folder, for example, but it also allows access to anything you have access to.It grants access only to those files (mounted volumes).
That's a pretty ****ing exclusive Venn diagram you've got there, of people who know how use public/private key pairs, know how to use them within a Docker image, but also think using Docker instead of just working out why their SFTP client won't connect to the built in SFTP server is a good idea.There is not a problem to mount host authorised ssh keys file to Docker container.
Are you also using Filezilla? I've had no issues connecting to sftp servers either on a Mac or elsewhere using Cyberduck.My question has nothing to do with running an sFTP server locally (like in Docker). I am simply trying to connect to an sFTP server (1and1.com). It is funny though I can connect to another sFTP server and also do ssh to the other server. So it has something to do with 1and1 and Catalina and ssh (because I can't ssh into 1and1 either)