broken pipe on ssh during connection
Using fedora 24, I have ssh connection problem. I installed it on 2 laptops and have the same problem on both. When I ssh, it asks for a password during connection, but immediately writes broken pipe and kicks me out.
ssh -l myname 192.168.1.5
myname@192.168.1.5's password:
packet_write_wait: Connection to 192.168.1.5 port 22: Broken pipe
When I make it verbose, I have this:
debug1: Next authentication method: password
myname@192.168.1.5's password:
debug1: Authentication succeeded (password).
Authenticated to 192.168.1.5 ([192.168.1.5]:22).
debug1: channel 0: new [client-session]
debug1: Requesting no-more-sessions@openssh.com
debug1: Entering interactive session.
debug1: pledge: network
packet_write_wait: Connection to 192.168.1.5 port 22: Broken pipe
I have no idea of how to connect, but I can connect from the same laptop to another debian laptop. I cannot connect from debian to any of those 2 Fedora computers.
I tried ssh -l myname localhost twice then ran journalctl -u sshd and this is the result:
Nov 03 17:15:09 localhost.localdomain sshd[15663]: Server listening on :: port 22.
Nov 03 17:15:09 localhost.localdomain systemd[1]: Started OpenSSH server daemon.
Nov 03 17:19:37 localhost.localdomain sshd[16025]: Accepted password for myname from 127.0.0.1 port 57942 ssh2
Nov 03 17:22:50 localhost.localdomain sshd[16086]: Accepted password for myname from 127.0.0.1 port 57996 ssh2
I don't know where to find more logs.
PS: SElinux is disabled.
I tried 2 times ssh -l myname localhost then run journalctl -u sshd and this is the result:
Nov 03 17:15:09 localhost.localdomain sshd[15663]: Server listening on :: port 22.
Nov 03 17:15:09 localhost.localdomain systemd[1]: Started OpenSSH server daemon.
Nov 03 17:19:37 localhost.localdomain sshd[16025]: Accepted password for myname from 127.0.0.1 port 57942 ssh2
Nov 03 17:22:50 localhost.localdomain sshd[16086]: Accepted password for myname from 127.0.0.1 port 57996 ssh2
ssh fedora
edited Dec 20 '18 at 1:56
Jeff Schaller
38.8k1053125
asked Nov 2 '16 at 23:35
lilington
1814
add a comment |
Using fedora 24, I have ssh connection problem. I installed it on 2 laptops and have the same problem on both. When I ssh, it asks for a password during connection, but immediately writes broken pipe and kicks me out.
ssh -l myname 192.168.1.5
myname@192.168.1.5's password:
packet_write_wait: Connection to 192.168.1.5 port 22: Broken pipe
When I make it verbose, I have this:
debug1: Next authentication method: password
myname@192.168.1.5's password:
debug1: Authentication succeeded (password).
Authenticated to 192.168.1.5 ([192.168.1.5]:22).
debug1: channel 0: new [client-session]
debug1: Requesting no-more-sessions@openssh.com
debug1: Entering interactive session.
debug1: pledge: network
packet_write_wait: Connection to 192.168.1.5 port 22: Broken pipe
I have no idea of how to connect, but I can connect from the same laptop to another debian laptop. I cannot connect from debian to any of those 2 Fedora computers.
I tried ssh -l myname localhost twice then ran journalctl -u sshd and this is the result:
Nov 03 17:15:09 localhost.localdomain sshd[15663]: Server listening on :: port 22.
Nov 03 17:15:09 localhost.localdomain systemd[1]: Started OpenSSH server daemon.
Nov 03 17:19:37 localhost.localdomain sshd[16025]: Accepted password for myname from 127.0.0.1 port 57942 ssh2
Nov 03 17:22:50 localhost.localdomain sshd[16086]: Accepted password for myname from 127.0.0.1 port 57996 ssh2
I don't know where to find more logs.
PS: SElinux is disabled.
I tried 2 times ssh -l myname localhost then run journalctl -u sshd and this is the result:
Nov 03 17:15:09 localhost.localdomain sshd[15663]: Server listening on :: port 22.
Nov 03 17:15:09 localhost.localdomain systemd[1]: Started OpenSSH server daemon.
Nov 03 17:19:37 localhost.localdomain sshd[16025]: Accepted password for myname from 127.0.0.1 port 57942 ssh2
Nov 03 17:22:50 localhost.localdomain sshd[16086]: Accepted password for myname from 127.0.0.1 port 57996 ssh2
ssh fedora
edited Dec 20 '18 at 1:56
Jeff Schaller
38.8k1053125
asked Nov 2 '16 at 23:35
lilington
1814
1
You need to look in the target machine's log files to see whysshis rejecting your incoming connections.
– roaima
Nov 3 '16 at 0:00
2
See "Write Failed: Broken Pipe” when trying to login through ssh with a specific user
– roaima
Nov 3 '16 at 0:03
As noted on the earlier stackoverflow post, we need the logs from the server to make sense of this.
– mattdm
Nov 3 '16 at 2:15
Did you set up a usermynameon that hosts?
– Jakuje
Nov 3 '16 at 7:13
add a comment |
Using fedora 24, I have ssh connection problem. I installed it on 2 laptops and have the same problem on both. When I ssh, it asks for a password during connection, but immediately writes broken pipe and kicks me out.
ssh -l myname 192.168.1.5
myname@192.168.1.5's password:
packet_write_wait: Connection to 192.168.1.5 port 22: Broken pipe
When I make it verbose, I have this:
debug1: Next authentication method: password
myname@192.168.1.5's password:
debug1: Authentication succeeded (password).
Authenticated to 192.168.1.5 ([192.168.1.5]:22).
debug1: channel 0: new [client-session]
debug1: Requesting no-more-sessions@openssh.com
debug1: Entering interactive session.
debug1: pledge: network
packet_write_wait: Connection to 192.168.1.5 port 22: Broken pipe
I have no idea of how to connect, but I can connect from the same laptop to another debian laptop. I cannot connect from debian to any of those 2 Fedora computers.
I tried ssh -l myname localhost twice then ran journalctl -u sshd and this is the result:
Nov 03 17:15:09 localhost.localdomain sshd[15663]: Server listening on :: port 22.
Nov 03 17:15:09 localhost.localdomain systemd[1]: Started OpenSSH server daemon.
Nov 03 17:19:37 localhost.localdomain sshd[16025]: Accepted password for myname from 127.0.0.1 port 57942 ssh2
Nov 03 17:22:50 localhost.localdomain sshd[16086]: Accepted password for myname from 127.0.0.1 port 57996 ssh2
I don't know where to find more logs.
PS: SElinux is disabled.
I tried 2 times ssh -l myname localhost then run journalctl -u sshd and this is the result:
Nov 03 17:15:09 localhost.localdomain sshd[15663]: Server listening on :: port 22.
Nov 03 17:15:09 localhost.localdomain systemd[1]: Started OpenSSH server daemon.
Nov 03 17:19:37 localhost.localdomain sshd[16025]: Accepted password for myname from 127.0.0.1 port 57942 ssh2
Nov 03 17:22:50 localhost.localdomain sshd[16086]: Accepted password for myname from 127.0.0.1 port 57996 ssh2
ssh fedora
edited Dec 20 '18 at 1:56
Jeff Schaller
38.8k1053125
asked Nov 2 '16 at 23:35
lilington
1814
Using fedora 24, I have ssh connection problem. I installed it on 2 laptops and have the same problem on both. When I ssh, it asks for a password during connection, but immediately writes broken pipe and kicks me out.
ssh -l myname 192.168.1.5
myname@192.168.1.5's password:
packet_write_wait: Connection to 192.168.1.5 port 22: Broken pipe
When I make it verbose, I have this:
debug1: Next authentication method: password
myname@192.168.1.5's password:
debug1: Authentication succeeded (password).
Authenticated to 192.168.1.5 ([192.168.1.5]:22).
debug1: channel 0: new [client-session]
debug1: Requesting no-more-sessions@openssh.com
debug1: Entering interactive session.
debug1: pledge: network
packet_write_wait: Connection to 192.168.1.5 port 22: Broken pipe
I have no idea of how to connect, but I can connect from the same laptop to another debian laptop. I cannot connect from debian to any of those 2 Fedora computers.
I tried ssh -l myname localhost twice then ran journalctl -u sshd and this is the result:
Nov 03 17:15:09 localhost.localdomain sshd[15663]: Server listening on :: port 22.
Nov 03 17:15:09 localhost.localdomain systemd[1]: Started OpenSSH server daemon.
Nov 03 17:19:37 localhost.localdomain sshd[16025]: Accepted password for myname from 127.0.0.1 port 57942 ssh2
Nov 03 17:22:50 localhost.localdomain sshd[16086]: Accepted password for myname from 127.0.0.1 port 57996 ssh2
I don't know where to find more logs.
PS: SElinux is disabled.
I tried 2 times ssh -l myname localhost then run journalctl -u sshd and this is the result:
Nov 03 17:15:09 localhost.localdomain sshd[15663]: Server listening on :: port 22.
Nov 03 17:15:09 localhost.localdomain systemd[1]: Started OpenSSH server daemon.
Nov 03 17:19:37 localhost.localdomain sshd[16025]: Accepted password for myname from 127.0.0.1 port 57942 ssh2
Nov 03 17:22:50 localhost.localdomain sshd[16086]: Accepted password for myname from 127.0.0.1 port 57996 ssh2
ssh fedora
ssh fedora
edited Dec 20 '18 at 1:56
Jeff Schaller
38.8k1053125
asked Nov 2 '16 at 23:35
lilington
1814
edited Dec 20 '18 at 1:56
Jeff Schaller
38.8k1053125
asked Nov 2 '16 at 23:35
lilington
1814
edited Dec 20 '18 at 1:56
Jeff Schaller
38.8k1053125
edited Dec 20 '18 at 1:56
Jeff Schaller
38.8k1053125
edited Dec 20 '18 at 1:56
Jeff Schaller
38.8k1053125
38.8k1053125
asked Nov 2 '16 at 23:35
lilington
1814
asked Nov 2 '16 at 23:35
lilington
1814
asked Nov 2 '16 at 23:35
lilington
1814
1814
1
You need to look in the target machine's log files to see whysshis rejecting your incoming connections.
– roaima
Nov 3 '16 at 0:00
2
See "Write Failed: Broken Pipe” when trying to login through ssh with a specific user
– roaima
Nov 3 '16 at 0:03
As noted on the earlier stackoverflow post, we need the logs from the server to make sense of this.
– mattdm
Nov 3 '16 at 2:15
Did you set up a usermynameon that hosts?
– Jakuje
Nov 3 '16 at 7:13
add a comment |
1
You need to look in the target machine's log files to see whysshis rejecting your incoming connections.
– roaima
Nov 3 '16 at 0:00
2
See "Write Failed: Broken Pipe” when trying to login through ssh with a specific user
– roaima
Nov 3 '16 at 0:03
As noted on the earlier stackoverflow post, we need the logs from the server to make sense of this.
– mattdm
Nov 3 '16 at 2:15
Did you set up a usermynameon that hosts?
– Jakuje
Nov 3 '16 at 7:13
1
1
You need to look in the target machine's log files to see why
ssh is rejecting your incoming connections.– roaima
Nov 3 '16 at 0:00
You need to look in the target machine's log files to see why
ssh is rejecting your incoming connections.– roaima
Nov 3 '16 at 0:00
2
2
See "Write Failed: Broken Pipe” when trying to login through ssh with a specific user
– roaima
Nov 3 '16 at 0:03
See "Write Failed: Broken Pipe” when trying to login through ssh with a specific user
– roaima
Nov 3 '16 at 0:03
As noted on the earlier stackoverflow post, we need the logs from the server to make sense of this.
– mattdm
Nov 3 '16 at 2:15
As noted on the earlier stackoverflow post, we need the logs from the server to make sense of this.
– mattdm
Nov 3 '16 at 2:15
Did you set up a user
myname on that hosts?– Jakuje
Nov 3 '16 at 7:13
Did you set up a user
myname on that hosts?– Jakuje
Nov 3 '16 at 7:13
add a comment |
1 Answer
1
active
oldest
votes
vi /etc/ssh/sshd_config
Change value of UsePrivilegeSeparation into yes.
I using fedora23, and I met the same with you, try my solution above, maybe it works. It looks like a problem about openssh-server-7.2p2-1.
edited Dec 20 '18 at 1:54
Jee
295
answered Jan 3 '17 at 6:11
user3152932
141
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f320691%2fbroken-pipe-on-ssh-during-connection%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
vi /etc/ssh/sshd_config
Change value of UsePrivilegeSeparation into yes.
I using fedora23, and I met the same with you, try my solution above, maybe it works. It looks like a problem about openssh-server-7.2p2-1.
edited Dec 20 '18 at 1:54
Jee
295
answered Jan 3 '17 at 6:11
user3152932
141
add a comment |
vi /etc/ssh/sshd_config
Change value of UsePrivilegeSeparation into yes.
I using fedora23, and I met the same with you, try my solution above, maybe it works. It looks like a problem about openssh-server-7.2p2-1.
edited Dec 20 '18 at 1:54
Jee
295
answered Jan 3 '17 at 6:11
user3152932
141
add a comment |
vi /etc/ssh/sshd_config
Change value of UsePrivilegeSeparation into yes.
I using fedora23, and I met the same with you, try my solution above, maybe it works. It looks like a problem about openssh-server-7.2p2-1.
edited Dec 20 '18 at 1:54
Jee
295
answered Jan 3 '17 at 6:11
user3152932
141
vi /etc/ssh/sshd_config
Change value of UsePrivilegeSeparation into yes.
I using fedora23, and I met the same with you, try my solution above, maybe it works. It looks like a problem about openssh-server-7.2p2-1.
edited Dec 20 '18 at 1:54
Jee
295
answered Jan 3 '17 at 6:11
user3152932
141
edited Dec 20 '18 at 1:54
Jee
295
edited Dec 20 '18 at 1:54
Jee
295
edited Dec 20 '18 at 1:54
Jee
295
295
answered Jan 3 '17 at 6:11
user3152932
141
answered Jan 3 '17 at 6:11
user3152932
141
answered Jan 3 '17 at 6:11
user3152932
141
141
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f320691%2fbroken-pipe-on-ssh-during-connection%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
You need to look in the target machine's log files to see why
sshis rejecting your incoming connections.– roaima
Nov 3 '16 at 0:00
2
See "Write Failed: Broken Pipe” when trying to login through ssh with a specific user
– roaima
Nov 3 '16 at 0:03
As noted on the earlier stackoverflow post, we need the logs from the server to make sense of this.
– mattdm
Nov 3 '16 at 2:15
Did you set up a user
mynameon that hosts?– Jakuje
Nov 3 '16 at 7:13