Test with more clients

[shazow]

Sounds like JuiceSSH on Android doesn't work?

Also possibly PuTTy on Windows?

[C0FFEEC0FFEE]

This occurs for me only on chat2.shazow.net, chat.shazow.net works fine.

I'm on Android 6.0.1 with a Nexus 7 and JuiceSSH 2.1.3.

I generated a ECDS 384 bit key pair.

[C0FFEEC0FFEE]

![screenshot_20160803-203109](https://cloud.githubusercontent.com/assets/20687034/17377307/7213e3f0-59b9-11e6-8d6c-2859f3955f50.png)

[shazow]

@C0FFEEC0FFEE Thanks! Is there any way to turn on verbose logging?

[C0FFEEC0FFEE]

I don't see any way to do that.

Also I tried all possible terminal types.

The connection will just timeout after something like 30 seconds.

[shazow]

Weird, thanks for reporting it! Will look into it once the more urgent bugs are fixed, or you're welcome to dive in too. :)

[botto]

Had an issue with Win 10 Putty 0.67 on chat2, but regular chat works find.

Added event log

2016-08-04 00:50:02 Looking up host "chat2.shazow.net"
2016-08-04 00:50:02 Connecting to 104.131.112.139 port 22
2016-08-04 00:50:02 We claim version: SSH-2.0-PuTTY_Release_0.67
2016-08-04 00:50:02 Server version: SSH-2.0-Go
2016-08-04 00:50:02 Using SSH protocol version 2
2016-08-04 00:50:02 Using Diffie-Hellman with standard group "group14"
2016-08-04 00:50:02 Doing Diffie-Hellman key exchange with hash SHA-1
2016-08-04 00:50:02 Host key fingerprint is:
2016-08-04 00:50:02 ssh-rsa 2048 ae:26:58:90:9c:07:71:a1:62:27:07:91:f2:25:9c:19
2016-08-04 00:50:02 Initialised AES-256 SDCTR client->server encryption
2016-08-04 00:50:02 Initialised HMAC-SHA-256 client->server MAC algorithm
2016-08-04 00:50:02 Initialised AES-256 SDCTR server->client encryption
2016-08-04 00:50:02 Initialised HMAC-SHA-256 server->client MAC algorithm
2016-08-04 00:50:02 Pageant is running. Requesting keys.
2016-08-04 00:50:02 Pageant has 1 SSH-2 keys
2016-08-04 00:50:04 Trying Pageant key #0
2016-08-04 00:50:10 Sending Pageant's response
2016-08-04 00:50:10 Server unexpectedly closed network connection

[shazow]

@botto I think it might have to do with my aggressive rate limiting and the size of your key. I'll tweak that.

[shazow]

@botto @C0FFEEC0FFEE Could you both try this server and let me know if it's better? Port 2222 on chat2.shazow.net:

$ ssh -p 2222 chat2.shazow.net

[C0FFEEC0FFEE]

On port 2222 it works fine.

[shazow]

@botto Can you confirm also?

Otherwise I'm closing this issue, should be resolved with the next release.

[botto]

Hi @shazow Sorry I haven't been back since reporting.
I still get disconnected when using my key, but without the key, no problems.
It's RSA 16384 bit length

[shazow]

That's quite a few bits. :P

Could you try with a shorter key for funsies?

[botto]

Tried with a 10240 and that worked.
Not first time I've pissed of owners of ssh servers 😆