OSX : Embedded iTerm Error

Hi,

What other settings do you have for the SSH?

Specifically, do you specify a username, password and/or private key file?

Thank you,

Richard

I just specify the IP, Port, Username & Password.

Tried the same when using iTerm standalone (on the 'Default' profile), and there was no issues.

Is there a way to turn on logging for what it's trying to do, so we can see the error properly ?

It's like it's not getting the space in /Applications/Remote Desktop Manager

i got the same issue, and i fixed this way.

Create the session name with the full server name you want to connect.

like myserver.domain.local

On general live the option at Command

On connection Tab type
ssh $name$

That would work.

Im new on mac and that is the way iterm is working for me.

Gustavo

Hi,

It looks like you are exactly correct: when you supply a username and password to the SSH connection, we use an embedded expect script to start SSH (so we can forward the password at the prompt).

There is a case where this path is not always quoted properly; it seems you are hitting that and it's causing the problem. I don't think the file system is related.

I will implement a fix for this. Sorry for the inconvenience.

Richard

Hi

It's a good idea but sadly won't work if he wants to include a password to be automatically used in SSH.

Thanks, Richard

Hi again,

I've made a fix for this and it will be available in the next release.

Sorry for the inconvenience.

Thanks, Richard

OK, so for now .. just don't specify a username & password ?

Or will it work if I use an RSA key ?

BTW .. Neat application guys .. Thanks for all the hard work.

This is app is so much more than an RDP for Windows app.

Hi

Yes - manually entering the password will work. RSA key should work as well however if you have a problem you can reply in this thread.

Thanks again, Richard

Thank you! :D

Hi, this is an old issue thread, but I can't use the ITERM option with an SSH key with a passphrase.
It asks for the passphrase with clear text input, but after that it does nothing after, it simple does not seam to establish te connection.

What can I do to solve this?

Thanks in advance.

JG

Hi,

We do not actively support iTerm sessions anymore. The session itself was marked deprecated a couple of versions back.

We usually recommend user to switch to SSH Shell and Telnet sessions.

Is there anything preventing you from using those sessions? If so, I'd encourage you to post feature requests.


Best regards,