Sorry folks, but as part of the bug clean up ahead of 16.04 LTS I'm
marking this as invalid because it affects an Ubuntu release which is
now unsupported. If you can still recreate this bug in a supported
release please do open a new bug and we can triage it for consideration
in the 16.04 LTS
Sorry folks, but as part of the bug clean up ahead of 16.04 LTS I'm
marking this as invalid because it affects an Ubuntu release which is
now unsupported. If you can still recreate this bug in a supported
release please do open a new bug and we can triage it for consideration
in the 16.04 LTS
Hi guys.
Without apparent reason suddenly I wasn't enable to make a ssh
connection with my production server. When run a ssh -v I get expecting
SSH2_MSG_KEX_ECDH_REPLY connection closed. After spend a lot of time
looking for a solution, I solve my problem just uncommenting two lines
in my
Hi guys.
Without apparent reason suddenly I wasn't enable to make a ssh
connection with my production server. When run a ssh -v I get expecting
SSH2_MSG_KEX_ECDH_REPLY connection closed. After spend a lot of time
looking for a solution, I solve my problem just uncommenting two lines
in my
no resolution ?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/708493
Title:
Can't login anymore: Read from socket failed: Connection reset by peer
To manage notifications about
no resolution ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/708493
Title:
Can't login anymore: Read from socket failed: Connection reset by peer
To manage notifications about this bug go to:
Thank you for the suggestions Gary. I realized that my problem is caused
by the router firmware. Basically, they introduced loopback blocking and
I couldn't connect from the same network even using the external IP.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Thank you for the suggestions Gary. I realized that my problem is caused
by the router firmware. Basically, they introduced loopback blocking and
I couldn't connect from the same network even using the external IP.
--
You received this bug notification because you are a member of Ubuntu
Server
:) ...
In the IT world it takes time to analyze a problem well !!
Congrats ...
Happy Easter !!
On 4 April 2015 at 13:06, Mike smart...@gmail.com wrote:
Thank you for the suggestions Gary. I realized that my problem is caused
by the router firmware. Basically, they introduced loopback
:) ...
In the IT world it takes time to analyze a problem well !!
Congrats ...
Happy Easter !!
On 4 April 2015 at 13:06, Mike smart...@gmail.com wrote:
Thank you for the suggestions Gary. I realized that my problem is caused
by the router firmware. Basically, they introduced loopback
** Changed in: openssh (Ubuntu)
Assignee: Irfan Fauzan (irfan-it2988) = (unassigned)
** Changed in: openssh (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
** Changed in: openssh (Ubuntu)
Assignee: Irfan Fauzan (irfan-it2988) = (unassigned)
** Changed in: openssh (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: oneiric precise
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/708493
Title:
Can't login anymore: Read from socket failed: Connection reset by peer
To manage
** Tags added: oneiric precise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/708493
Title:
Can't login anymore: Read from socket failed: Connection reset by peer
To manage notifications about this
Use dbclient ...
On 20 February 2015 at 19:07, Mike smart...@gmail.com wrote:
Hello,
Not sure it is the same problem here, but I cannot connect to my machine
if go through NAT.
If I connect directly from LAN everything works, but if I use the external
IP, then I get connection reset after
Use dbclient ...
On 20 February 2015 at 19:07, Mike smart...@gmail.com wrote:
Hello,
Not sure it is the same problem here, but I cannot connect to my machine
if go through NAT.
If I connect directly from LAN everything works, but if I use the external
IP, then I get connection reset after
Hello,
Not sure it is the same problem here, but I cannot connect to my machine if go
through NAT.
If I connect directly from LAN everything works, but if I use the external IP,
then I get connection reset after debug1: SSH2_MSG_KEXINIT sent.
Client and server is the same machine. I tried to
Hello,
Not sure it is the same problem here, but I cannot connect to my machine if go
through NAT.
If I connect directly from LAN everything works, but if I use the external IP,
then I get connection reset after debug1: SSH2_MSG_KEXINIT sent.
Client and server is the same machine. I tried to
Thanks, but a specific client is not an option. I need to connect with any
client from different systems. The flow I described is for problem
isolation only. Putty cannot connect either.
On Fri Feb 20 2015 at 18:31:15 Gary Salisbury 708...@bugs.launchpad.net
wrote:
Use dbclient ...
On 20
Thanks, but a specific client is not an option. I need to connect with any
client from different systems. The flow I described is for problem
isolation only. Putty cannot connect either.
On Fri Feb 20 2015 at 18:31:15 Gary Salisbury 708...@bugs.launchpad.net
wrote:
Use dbclient ...
On 20
Did this used to work ?
This bug is due to a ssh version change ...
Sounds like you may have a firewall issue, if you are trying to connect via
a nated connection for the 1st time.
Use tcpdump on your server ... and analyze the traffic on port 22
Compare the traffic, when you connect
Did this used to work ?
This bug is due to a ssh version change ...
Sounds like you may have a firewall issue, if you are trying to connect via
a nated connection for the 1st time.
Use tcpdump on your server ... and analyze the traffic on port 22
Compare the traffic, when you connect
Why are you testing a NATED address from the same server ( client and
server ) ?
Do you get the same problem when connecting via the NATED address from the
outside network ... using a different client machine from outside ?
On 20 February 2015 at 20:43, Gary Salisbury gary.r.salisb...@gmail.com
Why are you testing a NATED address from the same server ( client and
server ) ?
Do you get the same problem when connecting via the NATED address from the
outside network ... using a different client machine from outside ?
On 20 February 2015 at 20:43, Gary Salisbury gary.r.salisb...@gmail.com
This worked for me:
ssh -v admin@172.16.3.253 -o KexAlgorithms=diffie-hellman-group14-sha1
source:
http://stackoverflow.com/questions/25341773/cisco-ssh-key-exchange-
fails-from-ubuntu-14-04-client-dh-key-range-mismatch
--
You received this bug notification because you are a member of Ubuntu
This worked for me:
ssh -v admin@172.16.3.253 -o KexAlgorithms=diffie-hellman-group14-sha1
source:
http://stackoverflow.com/questions/25341773/cisco-ssh-key-exchange-
fails-from-ubuntu-14-04-client-dh-key-range-mismatch
--
You received this bug notification because you are a member of Ubuntu
This has now been bountied :
https://www.bountysource.com/issues/1033630-can-t-login-anymore-read-
from-socket-failed-connection-reset-by-peer
Good Luck 'Guesy ' and others.
This is just a note of a bounty made and shouldn't change the spirit of
fixing bugs. Thank-you.
--
You received this
This has now been bountied :
https://www.bountysource.com/issues/1033630-can-t-login-anymore-read-
from-socket-failed-connection-reset-by-peer
Good Luck 'Guesy ' and others.
This is just a note of a bounty made and shouldn't change the spirit of
fixing bugs. Thank-you.
--
You received this
I figured out a temporary workaround. Edit your ~/.ssh/config, and add the line:
Ciphers aes128-cbc
I haven't done any real debugging, but there looks like there could be a
problem with ciphers bigger than 128-bits. My Cisco devices are
complaining about DH length when I use AES192 or AES256.
I figured out a temporary workaround. Edit your ~/.ssh/config, and add the line:
Ciphers aes128-cbc
I haven't done any real debugging, but there looks like there could be a
problem with ciphers bigger than 128-bits. My Cisco devices are
complaining about DH length when I use AES192 or AES256.
My cases of this bug (though it seems like there are different ones with
similar symptoms) happen each time I reset a 14.04 VM to an older state
from a hard shutdown. Localhost ssh connections fail as well with same
output.
Workaround for me is regenerating the host keys (sudo rm /etc/ssh/host_*
Looks to be a No supported key exchange algorithms [preauth] problem.
Regenerating the host RSA key with ssh-keygen -t rsa -f
/etc/ssh/ssh_host_rsa_key fixes the issue
Log of failure (pre-keygen) on host:
$ sudo /usr/sbin/sshd -p -D -d -d -d -e
debug2: load_server_config: filename
I don't know if it's related but this is the log of trying to use that
RSA key to connect to a server:
debug1: Trying private key: /etc/ssh/ssh_host_rsa_key
debug1: key_parse_private2: missing begin marker
debug1: key_parse_private_pem: PEM_read_PrivateKey failed
debug1: read PEM private key
Well, at least in my case, I found that all the sshd host keys were
truncated. I'm guessing that the hard shutdown of the VM was the cause
but I'm not 100% sure.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
My cases of this bug (though it seems like there are different ones with
similar symptoms) happen each time I reset a 14.04 VM to an older state
from a hard shutdown. Localhost ssh connections fail as well with same
output.
Workaround for me is regenerating the host keys (sudo rm /etc/ssh/host_*
Looks to be a No supported key exchange algorithms [preauth] problem.
Regenerating the host RSA key with ssh-keygen -t rsa -f
/etc/ssh/ssh_host_rsa_key fixes the issue
Log of failure (pre-keygen) on host:
$ sudo /usr/sbin/sshd -p -D -d -d -d -e
debug2: load_server_config: filename
I don't know if it's related but this is the log of trying to use that
RSA key to connect to a server:
debug1: Trying private key: /etc/ssh/ssh_host_rsa_key
debug1: key_parse_private2: missing begin marker
debug1: key_parse_private_pem: PEM_read_PrivateKey failed
debug1: read PEM private key
Well, at least in my case, I found that all the sshd host keys were
truncated. I'm guessing that the hard shutdown of the VM was the cause
but I'm not 100% sure.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: openssh (Ubuntu)
Assignee: (unassigned) = Irfan Fauzan (irfan-it2988)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/708493
Title:
Can't login anymore: Read
** Changed in: openssh (Ubuntu)
Assignee: (unassigned) = Irfan Fauzan (irfan-it2988)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/708493
Title:
Can't login anymore: Read from socket failed:
Hi
I am facing the same problem. I have tried manys mentioned on the net to
solve but nothing seem to work.
When I called:
ping -M do -s 1500 ubuntu
This is what I recieved in output-
PING ubuntu (127.0.1.1) 1500(1528) bytes of data.
1508 bytes from ubuntu (127.0.1.1): icmp_req=1 ttl=64
Hi
I am facing the same problem. I have tried manys mentioned on the net to
solve but nothing seem to work.
When I called:
ping -M do -s 1500 ubuntu
This is what I recieved in output-
PING ubuntu (127.0.1.1) 1500(1528) bytes of data.
1508 bytes from ubuntu (127.0.1.1): icmp_req=1 ttl=64
Howdy,
I know that in my case, this was definitely an MTU problem, and it
exhibits exactly the behavior stated above.
to test this, call
ping -M do -s 1500 host
If it goes through, this is probably not your issue. If it does not, try
lowering the -s value until it does go through. If the
Howdy,
I know that in my case, this was definitely an MTU problem, and it
exhibits exactly the behavior stated above.
to test this, call
ping -M do -s 1500 host
If it goes through, this is probably not your issue. If it does not, try
lowering the -s value until it does go through. If the
I've studied the thread and tried the workaround suggestions. The
problem persists in 12.04.2!
Regards
SCUBA
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/708493
Title:
Can't
Hi,
I've managed to solve the issue... purge openssh-server on server
machine, then reinstall -- worked for me.
Regards
SCUBA
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/708493
I've studied the thread and tried the workaround suggestions. The
problem persists in 12.04.2!
Regards
SCUBA
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/708493
Title:
Can't login anymore: Read
Hi,
I've managed to solve the issue... purge openssh-server on server
machine, then reinstall -- worked for me.
Regards
SCUBA
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/708493
Title:
Can't
I have the same problem here. Only on one remote host:
sylock@sylock-vmware:~$ ssh -vvv XX
OpenSSH_6.0p1 Debian-3ubuntu1, OpenSSL 1.0.1c 10 May 2012
debug1: Reading configuration data /home/sylock/.ssh/config
debug1: /home/sylock/.ssh/config line 1: Applying options for *
debug1: Reading
Use dropbear
On 21 December 2012 15:27, Nicolas Michel nicolas.mic...@lemail.be
wrote:
I have the same problem here. Only on one remote host:
sylock@sylock-vmware:~$ ssh -vvv XX
OpenSSH_6.0p1 Debian-3ubuntu1, OpenSSL 1.0.1c 10 May 2012
debug1: Reading configuration data
Multiple commenters (#19, #43) have posted the workaround. In my
~/ssh/.config I now have
Host *
# Workaround for the dreaded 'connection reset by peer' bug, openssh =5.7:
Ciphers aes128-ctr,aes192-ctr,aes256-ctr
and I no longer see this problem.
--
You received this bug notification because
It's not really an answer, this bug has been around in ssh for a year or so
already ...
dropbear doesn't have this issue or older versions of ssh ... they don't
crash , it should have been fixed by now.
On 21 December 2012 18:44, Andrew Schulman
launchpad-and...@sneakemail.comwrote:
Multiple
I know the workaround. But we're here on a bug report platform ... I
posted to say hey, the problem is still here in 12.04!
Best regards,
Nicolas
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
I have the same problem here. Only on one remote host:
sylock@sylock-vmware:~$ ssh -vvv XX
OpenSSH_6.0p1 Debian-3ubuntu1, OpenSSL 1.0.1c 10 May 2012
debug1: Reading configuration data /home/sylock/.ssh/config
debug1: /home/sylock/.ssh/config line 1: Applying options for *
debug1: Reading
Use dropbear
On 21 December 2012 15:27, Nicolas Michel nicolas.mic...@lemail.be
wrote:
I have the same problem here. Only on one remote host:
sylock@sylock-vmware:~$ ssh -vvv XX
OpenSSH_6.0p1 Debian-3ubuntu1, OpenSSL 1.0.1c 10 May 2012
debug1: Reading configuration data
Multiple commenters (#19, #43) have posted the workaround. In my
~/ssh/.config I now have
Host *
# Workaround for the dreaded 'connection reset by peer' bug, openssh =5.7:
Ciphers aes128-ctr,aes192-ctr,aes256-ctr
and I no longer see this problem.
--
You received this bug notification because
It's not really an answer, this bug has been around in ssh for a year or so
already ...
dropbear doesn't have this issue or older versions of ssh ... they don't
crash , it should have been fixed by now.
On 21 December 2012 18:44, Andrew Schulman
launchpad-and...@sneakemail.comwrote:
Multiple
I know the workaround. But we're here on a bug report platform ... I
posted to say hey, the problem is still here in 12.04!
Best regards,
Nicolas
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/708493
ssh -c 3des-cbc host also works for me as well. And adding this to my
ssh config makes it automatic
Host *
Ciphers 3des-cbc
btw, this is only a problem through my cisco openconnect VPN. Different
VPNs don't have this issue.
--
You received this bug notification because you are a member of
ssh -c 3des-cbc host also works for me as well. And adding this to my
ssh config makes it automatic
Host *
Ciphers 3des-cbc
btw, this is only a problem through my cisco openconnect VPN. Different
VPNs don't have this issue.
--
You received this bug notification because you are a member of
** Summary changed:
- cannot login anymore: Read from socket failed: Connection reset by peer
+ Can't login anymore: Read from socket failed: Connection reset by peer
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
** Summary changed:
- cannot login anymore: Read from socket failed: Connection reset by peer
+ Can't login anymore: Read from socket failed: Connection reset by peer
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
62 matches
Mail list logo
