kex | A platform for analysis of Java bytecode | Bytecode library

Your server/device seems to require some dummy keyboard interactive authentication:

Your server seems to issue two keyboard-interactive authentication challenges

• First, a prompt for a password
• Second, a banner with no prompts.

So you will have to do something like this:

TL;DR Your config file "github" entry should look like this:

So the issue was I was using the wrong username, but it was still throwing a key authentication error.

Per @martin-prikryl's request, I attempted to connect using PuTTY, and found a nice tutorial specifically using PuTTY to SSH into Bluehost.

I had first written a script for FTP, and that used the Bluehost FTP account you can specifically create on their site. When I decided to write my SSH script, I used the same username. Alas, but for SSH, Bluehost wants the main login's username, NOT the FTP account one.

But it still recognizes the username on some level, but then the key is not linked to it, thus the key authentication error.

So I used PuTTy with the main username and that worked fine.

I then updated my script (credit to this stackoverflow post)

My new script that uploads an entire dir to bluehost using SSH:

I have been able to solve this and will explain how.

My issue was my password was not being accepted even after resetting the password in the droplet.

"Password not accepted in the console" info can be found here https://docs.digitalocean.com/products/droplets/resources/troubleshooting-ssh/authentication/

I followed the Boot into the Recovery process linked here: https://docs.digitalocean.com/products/droplets/resources/recovery-iso/#boot-into-the-recovery-iso

• Power down or stop droplet
• Select boot from recovery ISO
• Turned on the droplet again
• clicked the console

At this stage I was present with a list of options.

1. Mount your Disk Image [Not Mounted]
2. Check Filesystem
3. Reset Droplet Root Password
4. Configure Keyboard
5. Attempt to 'chroot' into installed system
6. Interactive Shell [/bin/bash] Choose (1-6) and press Enter to continue.

• I selected option 1, then 3, followed by 6.

• After this I powered off the droplet and selected boot from hard drive.

• Accessing the console I was able to login and enter the password which was accepted and the ghost install began and completed successfully.

I hope this helps anyone who is experiencing the same issue.

BadPaddingExceptions are a very common failure mode when a decryption is performed with the wrong key.

The server must decode with the client's public key whilst encoding with its own key.

Similarly the client must decode with the server's public key and encode with its own key.

The test you performed suggests that the decode and encode are using the local public key, not the sender's public key.

There are a few things you are doing wrong

1. You should not login from within the gerrit container as it will use the gerrit user and ssh key. There is no gerrit user in gerrit in such a way
2. You should create a new user, are you using LDAP?
3. Next, log in to gerrit using that users credentials and add the public ssh key from the user in the user profile. Depending on your server url: https://myserver.net/settings/#SSHKeys
4. Now you should be able to connect

If the private key format differs, that means, as I mentioned here that:

• one platform is using openssh prior to 7.8, with an old PEM 64-chars per line format.
• one is using a more recent OpenSSH format, 70-chars per line.

You can force a recent openSSH to generate the old format with: