Lost SSH access after Upgrade to 18.04
Clash Royale CLAN TAG#URR8PPP up vote
0
down vote
favorite
After upgrading 2 16.04 servers to 18.04 I lost ssh access to both. During both upgrades I got a message asking if I wanted to keep my custom config file or if I would like to replace it. I chose to keep it as both servers are configured as SFTP servers. Any suggestions for how to get ssh for remote login available again would be appreciated.
SFTP is still working for my configured users on both servers.
Thanks!
server upgrade ssh
asked May 16 at 21:49
Oscar Smarty
122
add a comment |Â
up vote
0
down vote
favorite
After upgrading 2 16.04 servers to 18.04 I lost ssh access to both. During both upgrades I got a message asking if I wanted to keep my custom config file or if I would like to replace it. I chose to keep it as both servers are configured as SFTP servers. Any suggestions for how to get ssh for remote login available again would be appreciated.
SFTP is still working for my configured users on both servers.
Thanks!
server upgrade ssh
asked May 16 at 21:49
Oscar Smarty
122
You should update your question with more info. What are the exact commands you have executed? What are the outputs you are getting? "Lost ssh access" is not very specific.
– curusarn
May 16 at 22:28
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
After upgrading 2 16.04 servers to 18.04 I lost ssh access to both. During both upgrades I got a message asking if I wanted to keep my custom config file or if I would like to replace it. I chose to keep it as both servers are configured as SFTP servers. Any suggestions for how to get ssh for remote login available again would be appreciated.
SFTP is still working for my configured users on both servers.
Thanks!
server upgrade ssh
asked May 16 at 21:49
Oscar Smarty
122
After upgrading 2 16.04 servers to 18.04 I lost ssh access to both. During both upgrades I got a message asking if I wanted to keep my custom config file or if I would like to replace it. I chose to keep it as both servers are configured as SFTP servers. Any suggestions for how to get ssh for remote login available again would be appreciated.
SFTP is still working for my configured users on both servers.
Thanks!
server upgrade ssh
asked May 16 at 21:49
Oscar Smarty
122
asked May 16 at 21:49
Oscar Smarty
122
asked May 16 at 21:49
Oscar Smarty
122
asked May 16 at 21:49
Oscar Smarty
122
122
You should update your question with more info. What are the exact commands you have executed? What are the outputs you are getting? "Lost ssh access" is not very specific.
– curusarn
May 16 at 22:28
add a comment |Â
You should update your question with more info. What are the exact commands you have executed? What are the outputs you are getting? "Lost ssh access" is not very specific.
– curusarn
May 16 at 22:28
You should update your question with more info. What are the exact commands you have executed? What are the outputs you are getting? "Lost ssh access" is not very specific.
– curusarn
May 16 at 22:28
You should update your question with more info. What are the exact commands you have executed? What are the outputs you are getting? "Lost ssh access" is not very specific.
– curusarn
May 16 at 22:28
add a comment |Â
2 Answers
2
active
oldest
votes
up vote
0
down vote
It appears the allowed ciphers for OpenSSH have changed. I moved Blowfish to the top of the order in my client and was able to connect to one. On the other I had to comment out the Ciphers line in the sshd_config, that command is optional anyway. After that I was able to connect to both servers.
answered May 17 at 8:08
Oscar Smarty
122
add a comment |Â
up vote
0
down vote
I got the same warning and could not get back in too. I had two issues that needed to be fixed.
My VPS provider offers another way in with LISH. I noticed SSH errors in the boot up window. What was wrong with the SSH service? Running sudo /usr/sbin/sshd –T gave me aMissing privilege separation directory: /var/run/sshd error.
After following these instructions SSH problem after update, at least ssh would run. mkdir /var/run/sshd
chmod 0755 /var/run/sshd
But my key was still not accepted. Then I started tailing the auth.log. Lish cut off the line, so this was all I had to go on: error: userauth_pubkey: could not parse k . But the first Google hit led me to a report that showed that SSH was failing for key length on Windows boxes. Just on a hunch, I created a new public private key pair and installed it – and Voila, I am in. My old key had been 1024 bits, and was made so long ago that I cannot be sure what encryption method was used in it’s creation.
https://github.com/PowerShell/Win32-OpenSSH/issues/855
answered Aug 14 at 14:46
wruckie
1138
add a comment |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
It appears the allowed ciphers for OpenSSH have changed. I moved Blowfish to the top of the order in my client and was able to connect to one. On the other I had to comment out the Ciphers line in the sshd_config, that command is optional anyway. After that I was able to connect to both servers.
answered May 17 at 8:08
Oscar Smarty
122
add a comment |Â
up vote
0
down vote
It appears the allowed ciphers for OpenSSH have changed. I moved Blowfish to the top of the order in my client and was able to connect to one. On the other I had to comment out the Ciphers line in the sshd_config, that command is optional anyway. After that I was able to connect to both servers.
answered May 17 at 8:08
Oscar Smarty
122
add a comment |Â
up vote
0
down vote
up vote
0
down vote
It appears the allowed ciphers for OpenSSH have changed. I moved Blowfish to the top of the order in my client and was able to connect to one. On the other I had to comment out the Ciphers line in the sshd_config, that command is optional anyway. After that I was able to connect to both servers.
answered May 17 at 8:08
Oscar Smarty
122
It appears the allowed ciphers for OpenSSH have changed. I moved Blowfish to the top of the order in my client and was able to connect to one. On the other I had to comment out the Ciphers line in the sshd_config, that command is optional anyway. After that I was able to connect to both servers.
answered May 17 at 8:08
Oscar Smarty
122
answered May 17 at 8:08
Oscar Smarty
122
answered May 17 at 8:08
Oscar Smarty
122
answered May 17 at 8:08
Oscar Smarty
122
122
add a comment |Â
add a comment |Â
up vote
0
down vote
I got the same warning and could not get back in too. I had two issues that needed to be fixed.
My VPS provider offers another way in with LISH. I noticed SSH errors in the boot up window. What was wrong with the SSH service? Running sudo /usr/sbin/sshd –T gave me aMissing privilege separation directory: /var/run/sshd error.
After following these instructions SSH problem after update, at least ssh would run. mkdir /var/run/sshd
chmod 0755 /var/run/sshd
But my key was still not accepted. Then I started tailing the auth.log. Lish cut off the line, so this was all I had to go on: error: userauth_pubkey: could not parse k . But the first Google hit led me to a report that showed that SSH was failing for key length on Windows boxes. Just on a hunch, I created a new public private key pair and installed it – and Voila, I am in. My old key had been 1024 bits, and was made so long ago that I cannot be sure what encryption method was used in it’s creation.
https://github.com/PowerShell/Win32-OpenSSH/issues/855
answered Aug 14 at 14:46
wruckie
1138
add a comment |Â
up vote
0
down vote
I got the same warning and could not get back in too. I had two issues that needed to be fixed.
My VPS provider offers another way in with LISH. I noticed SSH errors in the boot up window. What was wrong with the SSH service? Running sudo /usr/sbin/sshd –T gave me aMissing privilege separation directory: /var/run/sshd error.
After following these instructions SSH problem after update, at least ssh would run. mkdir /var/run/sshd
chmod 0755 /var/run/sshd
But my key was still not accepted. Then I started tailing the auth.log. Lish cut off the line, so this was all I had to go on: error: userauth_pubkey: could not parse k . But the first Google hit led me to a report that showed that SSH was failing for key length on Windows boxes. Just on a hunch, I created a new public private key pair and installed it – and Voila, I am in. My old key had been 1024 bits, and was made so long ago that I cannot be sure what encryption method was used in it’s creation.
https://github.com/PowerShell/Win32-OpenSSH/issues/855
answered Aug 14 at 14:46
wruckie
1138
add a comment |Â
up vote
0
down vote
up vote
0
down vote
I got the same warning and could not get back in too. I had two issues that needed to be fixed.
My VPS provider offers another way in with LISH. I noticed SSH errors in the boot up window. What was wrong with the SSH service? Running sudo /usr/sbin/sshd –T gave me aMissing privilege separation directory: /var/run/sshd error.
After following these instructions SSH problem after update, at least ssh would run. mkdir /var/run/sshd
chmod 0755 /var/run/sshd
But my key was still not accepted. Then I started tailing the auth.log. Lish cut off the line, so this was all I had to go on: error: userauth_pubkey: could not parse k . But the first Google hit led me to a report that showed that SSH was failing for key length on Windows boxes. Just on a hunch, I created a new public private key pair and installed it – and Voila, I am in. My old key had been 1024 bits, and was made so long ago that I cannot be sure what encryption method was used in it’s creation.
https://github.com/PowerShell/Win32-OpenSSH/issues/855
answered Aug 14 at 14:46
wruckie
1138
I got the same warning and could not get back in too. I had two issues that needed to be fixed.
My VPS provider offers another way in with LISH. I noticed SSH errors in the boot up window. What was wrong with the SSH service? Running sudo /usr/sbin/sshd –T gave me aMissing privilege separation directory: /var/run/sshd error.
After following these instructions SSH problem after update, at least ssh would run. mkdir /var/run/sshd
chmod 0755 /var/run/sshd
But my key was still not accepted. Then I started tailing the auth.log. Lish cut off the line, so this was all I had to go on: error: userauth_pubkey: could not parse k . But the first Google hit led me to a report that showed that SSH was failing for key length on Windows boxes. Just on a hunch, I created a new public private key pair and installed it – and Voila, I am in. My old key had been 1024 bits, and was made so long ago that I cannot be sure what encryption method was used in it’s creation.
https://github.com/PowerShell/Win32-OpenSSH/issues/855
answered Aug 14 at 14:46
wruckie
1138
answered Aug 14 at 14:46
wruckie
1138
answered Aug 14 at 14:46
wruckie
1138
answered Aug 14 at 14:46
wruckie
1138
1138
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1037131%2flost-ssh-access-after-upgrade-to-18-04%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
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
You should update your question with more info. What are the exact commands you have executed? What are the outputs you are getting? "Lost ssh access" is not very specific.
– curusarn
May 16 at 22:28