Packetwritewait: Connection to 192.30.253.112 port 22: Broken pipe fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. And it seems that nothing related to the certificate issues.
![Fatal write failed broken pipe Fatal write failed broken pipe](/uploads/1/2/5/4/125457422/720048098.png)
Welcome to LinuxQuestions.org, a friendly and active Linux Community.You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Today!Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.Are you new to LinuxQuestions.org? Visit the following links: If you have any problems with the registration process or your account login, please. If you need to reset your password,.Having a problem logging in?
Please visit to clear all LQ-related cookies. Introduction to Linux - A Hands on GuideThis guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.to receive this Complete Guide absolutely free.
Older default fedora sshd configurations would time out after some minutes and disconnect the client, leaving the same error message. It seems to me I had to change a setting in the putty connection settings to send a client keep alive packet (if you're using putty). There is an options setting in linux ssh to provide TCPkeepalive maybe it can help.Anyway, current fedora settings don't seem to have this problem any longer, maybe you can compare your sshdconfig with a new default sshdconfig and see if there are any big differences. Nowdays I just open a default settings ssh connection and it stays open for days.