4

When using SSH on my Chromebook using the Google Secure Shell app to connect to my Debian DigitalOcean droplet, the connection drops suddenly after around 2 minutes of use and I am receiving this error message: 

NaCl plugin exited with status code 255.
(R)econnect, (C)hoose another connection, or E(x)it?

Any suggestions on what this is? Many thanks, Nathan

Jesse Nickles
  • 1,435
  • 1
  • 17
  • 25
Nathan Dunn
  • 336
  • 2
  • 3
  • 12
  • I'm experiencing the same, on my Toshiba Chromebook ... :( ... the I found a possible solution with disabling a flag: enable-tcp-fast-open ... but it was already disabled, so the solution doesn't work for me. – pesho hristov Feb 24 '14 at 14:41
  • Just remove --no-proxy-host from config and it will work – M K Garwa Apr 25 '19 at 04:02

1 Answers1

3

This is most likely a NAT idle timeout in your home router. Try adding -o TCPKeepAlive=yes to the "SSH Arguments" field of the connection dialog.

If it's not a NAT issue, then the second most likely option is that you've imported a config file (using Secure Shell's "Import..." link in the connection dialog) that specifies a ServerAliveInterval, which does not work properly in Secure Shell.

snollygolly
  • 1,858
  • 2
  • 17
  • 31
rginda
  • 41
  • 2
  • Adding TCPKeepAlive flag solved this issue for me, connecting from W10 via my home router. Thanks heaps! – Andrej Grobler Jul 07 '19 at 00:43
  • This also may be happening to some people because SSH is being blocked by their network e.g. at certain office buildings or restaurants, etc. You can try using a VPN in those situations but VPNs might be blocked by firewalls, too. – Jesse Nickles Sep 11 '21 at 22:13