Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

I normally use RSA keys for SSH, but for no particular reason, I wanted to try using an ED25519 key. I made one and added it to my collection of SSH keys. I then spun an Ubuntu 17.10 droplet up and had it use this public key.
The server does not seem happy about this key, however. This is the log from when trying to connect. Any idea what’s causing this?
jes@mymachine:~$ ssh -vvv -i .ssh/testservers root@178.62.62.178
OpenSSH_7.6p1, OpenSSL 1.0.2g 1 Mar 2016
debug1: Reading configuration data /home/jes/.ssh/config
debug1: Reading configuration data /usr/local/etc/ssh_config
debug2: resolving "178.62.62.178" port 22
debug2: ssh_connect_direct: needpriv 0
debug1: Connecting to 178.62.62.178 [178.62.62.178] port 22.
debug1: Connection established.
debug1: identity file .ssh/testservers type 3
debug1: key_load_public: No such file or directory
debug1: identity file .ssh/testservers-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_7.6
debug1: Remote protocol version 2.0, remote software version OpenSSH_7.5p1 Ubuntu-10
debug1: match: OpenSSH_7.5p1 Ubuntu-10 pat OpenSSH* compat 0x04000000
debug2: fd 3 setting O_NONBLOCK
debug1: Authenticating to 178.62.62.178:22 as 'root'
debug3: hostkeys_foreach: reading file "/home/jes/.ssh/known_hosts"
debug3: send packet: type 20
debug1: SSH2_MSG_KEXINIT sent
Connection closed by 178.62.62.178 port 22
jes@mymachine:~$ ssh-keygen -lf .ssh/testservers.pub
256 SHA256:80Y1v3JofR7j6CGlACM+C4iQlMWff+qIUX5Aje+/lDw jes@mymachine (ED25519)
jes@mymachine:~$
2528527458a540fba5c38cc921bb27
c21c0b00bb284130a0d0cd3b7bdab4
IsaacMvd
Leon Junior
hashembarret@gmail.com
JetForMe
24608ead89f046a8abab394f968f2c
Philipp Mayerhofer
enews
Brian Magnosi
jairunet