When you select a session in the Sessions Menu you will begin the connection process.
The next thing you should see is a black screen (assuming you haven’t changed the colours) with the words:
Connecting to yourserver.com...
After a few seconds you should see that followed by the word OK to indicate that a connection has been made.
Connecting to yourserver.com...OK
If you don’t see that or see an error message instead take a look at connection troubleshooting.
You will then see a different series of messages depending upon the protocol in use and the build you’re using. After those messages, if all goes well, you will see the prompt from your server.
After the Connecting...OK message you will see a negotiating message:
Negotiating...
This is when your device computes some private and public keys to encrypt this connection. This may take some time before you see the OK as it is quite computationally difficult. You can improve the speed of this by tuning your SSH Settings. Once you see the OK the keys have been successfully negotiated.
Negotiating...OK
This will be followed by a fingerprint of the server’s public key. This will be its ssh-dss key because MidpSSH only supports some ssh2 algorithms.
ssh-dss a6:7f:82:12:19 etc
We are then waiting for the remote server to send us the confirmed keys. From this point onward the messages are not seen in lite builds of MidpSSH. If you are using a non-lite build you will see a sequence similar to the following:
Requesting authentication Sent publickey / password Authentication accepted Shell opened
After this you should see your server’s prompt.
If the connection fails you may see something that helps you troubleshoot the problem in the messages that appear. If you see a message that authentication failed, double, triple check your password, and if that doesn’t work try changing your password to something really simple and trying again.