Turbocapitalist knows more about Cyberduck and the mac than I do so I will leave things in his capable hands. I will issue a caution, though, Adirondacks. It sounds to me as if you may be making some assumptions that may or may not be correct. If you are, this can bite you big time. I think you are at the point that you need to learn how to turn logging on, where the logs will be, and how to interpret them. You should be able to do that through your documentation and your friendly google searches. I know you are frustrated but part of that comes from what you don't know which makes it hard for someone to help you without actually sitting beside you. Once you have your logs available then carefully go through the exercise of trying to send/receive a file and immediately look at your logs. Somewhere there is at list a hint if not the answer itself. In linux it is possible to watch a log real time as it is being written. For example, you can monitor the system log by opening a terminal and entering assuming that is the path to the log and the filename. You may have to use sudo depending on permissions. To stop the real time monitoring press Ctl-C. There is no reason you cannot have two or three separate terminals open monitoring different log files if you need/want to. For that matter if you can ssh into the remote machine you could monitor the logs at both ends. Whether the mac has the same facilities I don't know. But I wish you good luck. And you might want to keep some notes about what you learn and find out. It is amazing how something will crop up again after you have forgotten how you fixed it. Something about Murphy.

1 members found this post helpful.

Um. ssh keys are specific to a machine. That's what they do. They say, in effect, that this Mac is "known" to the host. That's why the file at ~/.ssh/known_hosts on the server has that name...

If you try to connect from a different Mac machine, you'll be prompted for the remote user password, because you've not set up the ssh key for that machine.

Every machine you want to connect to your VPS with without a password will need a key pair set up and installed.

Yes.


Legacy??

I am trying to learn more command-line, but am overwhelmed with non-Linux stuff...


I'll have to find time to learn about sudo and related things first.

Yes I would like to learn more what you describe above...

As far as using CyberDuck, I have basically accepted defeat. :-(

On the afflicted Macintosh, it would be best to look at the CyberDuck logs.

However, if that is not an option then one random, flailing action would be to start fresh. Close CyberDuck and then go find something like ~/Library/Application Support/CyberDuck or whatever the right name is and rename it to ~/Library/Application Support/not.CyberDuck Then start CyberDuck again and add your settings. Like I said, it's been ages so I hope things have not moved much.

I did something similar the other night and deleted what appeared to be the CyberDuck preferences folder. Restarted CyberDuck and no luck.

So then I deleted all preference/config files I could find, plus the application, emptied my trash, rebooted, and then re-installed CyberDuck.

Can you believe I ran into the SAME problems just when trying to connect to the one VPS?

At this point it seems to me that CyberDuck is really CyberF***ed...

I had worried about it once they started using M$ languages in their code. It appears to be a signal that the rest may be (or has become) poor also.

I'm not sure if it would help but there is a graphical wrapper for the shell-based utilities called Fugu, but is is a little underloved these days.

The other graphical alternative would be FileZilla.

Then there are still the underlying OpenSSH utilities, which can be scripted either via the shell or Quartz.

1 members found this post helpful.

Are you saying that CyberDuck is written in some Microsoft-based language? If so, how is that possible if the client is designed for Linux and Macs?


I tried installing that, but got some JRE error and consdiering that running Java can be a security threat, I prefer not to leave it running. That and the website and codebase looked like things have been let go...


I would never use a product where the creator stores SSH passwords in plaintext because he doesn't think that's a security issue!


I broke down and spent $50 on Transmit 5, and so far it works. Although I'm not creazy about proprietary software.

Will have to see if things stay unbroken, but CyberDuck just went from "hero" to "zero" in my books!!

Not entirely. The Wikipedia page makes it look like some of it is, which is where I saw that, but it may be just the Windows client is infected:

https://github.com/iterate-ch/cyberd...r/osx/src/main
https://github.com/iterate-ch/cyberd...ndows/src/main

Otherwise, it looks like it is written in Java for the most part which should run fine on all systems.

M$ languages have only partial language support. M$ had found saboteurs willing to port some of one of their language to Linux and Mac. Some. It's a long story involving partial support, broken tools, and software patents. Yes the software patents remain relevant in spite of the empty noise about joining LOT and OIN.

Software patents aside, it's their typical ploy: make it look enough like it is about to work that it convinces ignorant managers to buy in. They buy in and then after they feel committed then they say that it only has the full set of functions on Windoze.

A wrapper for the normal OpenSSH clients in Qt might be possible to use to make a portable, graphical SFTP client and there is a need but maintaining it would be a chore. Or there is libssh2. But I digress. None of that solves the immediate problem of looking for a graphical SFTP client.