Ssh help/background music

Jste84

@mitu I've tried but I'm.now getting a network error. Software caused connection abort message.

Clyde

@Jste84 Please give us the exact error messages, as we can't deduce much from a summary like "a network error".

mitu

@Jste84 Most likely the procedure didn't fix - can you run systemctl status ssh again and see if any errors are shown, from the log ?

Jste84

@mitu said in Ssh help/background music:

@Jste84 Most likely the procedure didn't fix - can you run systemctl status ssh again and see if any errors are shown, from the log ?

Jste84

@Clyde said in Ssh help/background music:

@Jste84 Please give us the exact error messages, as we can't deduce much from a summary like "a network error".

Jste84

@Clyde @mitu I've just tried to reinstall putty, to check if this makes any difference...but no joy. Slightly different error message

el chupacabra

Are you sure ssh is running? How did you run raspi-config before? you should use it again and make sure the ssh service is running on boot.

also you can do
tail /var/log/auth.log
or just nano to it and look at the last lines to see why it kicked you off. If it is running, that is.

mitu

Putty is a simple program, doesn't need to be re-installed. The errors in the ssh service indicate that sshd doesn't work correctly, hence the Putty error. If you run - from a command line on the Pi - ssh localhost, you'll probably also receive an error.

I've run the procedure to reset the SSHD host keys and they are re-generated - make sure you've correctly executed the steps on that page and that you restart the ssh service.

Jste84

@mitu maybe im doing it wrong. When I'm following the guide and get to the step keygen and it says remote server name here.... What should I be putting in?

mitu

@Jste84 The keygen step is the execution of

sudo dpkg-reconfigure openssh-server

Are you executing that on the PI ?

Jste84

@mitu yes executed that on the pi. Was looking at step 3? Do I need to do that? And if so do I do it on the pi?

I

mitu

Step 3 is not necessary - that's just for the SSH clients which connected before to the same machine.

cyperghost

@mitu If he needs only a possibilty to copy some files then why not set port to 21 and use FTP? This should work out of the box.

mitu

@cyperghost said in Ssh help/background music:

If he needs only a possibilty to copy some files then why not set port to 21 and use FTP?

FTP is a different protocol, you'd need a FTP server, while SSHD only provides sftp/scp.

Jste84

@el-chupacabra said in Ssh help/background music:

Are you sure ssh is running? How did you run raspi-config before? you should use it again and make sure the ssh service is running on boot.

also you can do
tail /var/log/auth.log
or just nano to it and look at the last lines to see why it kicked you off. If it is running, that is.

Ssh should be running. I've enabled it via raspiconfig. Tried this via both the retropie settings and manually by quitting emulation station

Jste84

@mitu ahh ok that's what I thought. Then yes, step 1 and 2 are complete. I keep getting remote side unexpectedly closed network connection message from putty

Jste84

Still getting the same error when I enter systemctl status ssh

mitu

@Jste84 Strange - are you sure your SD card is ok ? After step 1 - removing the host key files -, can you check that the files are really removed from /etc/ssh ?

Jste84

@mitu said in Ssh help/background music:

@Jste84 Strange - are you sure your SD card is ok ? After step 1 - removing the host key files -, can you check that the files are really removed from /etc/ssh ?

SD card is new, bought from a store rather than online, so absolutely shouldn't have any issues.

Silly question, but how would I know if they'd been removed? Or if they were there to begin with?

Also how do I check etc/ssh?

mitu

@Jste84 said in Ssh help/background music:

Also how do I check etc/ssh?

You can use mc (Midnight Commander) to browse the filesystem, or just run

ls -l /etc/ssh

to see if the files you removed in Step 1 are still there.