Related

Join the DigitalOcean Community Community

Join 1M+ other developers and:

  • Get help and share knowledge in Q&A
  • Subscribe to topics of interest
  • Get courses & tools that help you grow as a developer or small business owner
 Join Now
Why poweroff (even from the command line)? Question Question
Filezilla gives error " "no such file or directory" Question Question

Question

ssh, after successful login, I keep getting Write failed: Connection reset by peer

Posted July 25, 2015 12.3k views
UbuntuDigitalOceanConfiguration Management

It is unworkable. Ubuntu, NY 2. Am I the only one? What can I do?

Add a comment
protagonist
By:
protagonist

Related

Join the DigitalOcean Community Community

Join 1M+ other developers and:

  • Get help and share knowledge in Q&A
  • Subscribe to topics of interest
  • Get courses & tools that help you grow as a developer or small business owner
 Join Now
Why poweroff (even from the command line)? Question Question
Filezilla gives error " "no such file or directory" Question Question
Add a comment
2 comments
  • davisonio July 25, 2015
    Reply Report

    Does the terminal freeze when this happens?
    Does the message show instantly when you join, or does it show after a few seconds?

  • protagonist July 25, 2015
    Reply Report

    Hello,

    The terminal does not freeze, and it does not happen instantly. Sometime, I can work normally for a few minutes, but it keeps happening. Time span can be somewhere between 30 seconds and 5 minutes before the connection fails.

    Thank you for reply

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
Submit an Answer
1 answer
davisonio July 25, 2015

Hi @protagonist

In that case, try editing a couple of files.

On the server edit /etc/ssh/sshd_config (using nano /etc/ssh/sshd_config for example).
Find the line which says ClientAliveInterval and increase it to something like 600.

On the client edit /etc/ssh/sshd_config (using nano /etc/ssh/sshd_config for example).
Find the line which says ServerAliveInterval and increase it to something like 600.

If those lines are not in the files already, just add them like this:

ClientAliveInterval 600

and this:

ServerAliveInterval 600
Reply Report

Related

Looking for something else?

Ask a new question Search for more help