Timeline for Ssh connection refused
Current License: CC BY-SA 3.0
24 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Nov 28, 2015 at 2:11 | history | suggested | A.B. | CC BY-SA 3.0 |
formatting
|
| Nov 27, 2015 at 21:50 | review | Suggested edits | |||
| S Nov 28, 2015 at 2:11 | |||||
| Oct 29, 2015 at 9:24 | comment | added | Peter Paul Kiefer | Sorry then I have no more good ideas. Perhaps: If possible you can create a new SD card with a new Raspian (Wheezy) installation. If the misbehavior remains then you have likely a problem with your ssh-clients (Putty, ...) or the network configuration. If it disappears I would say something went wrong on your pi resp. the old sd card. Perhaps a virus, unawared misconfiguration, the kernel firewall of your pi. Perhaps before you install a new SD card; you can change your ip adress with the last number from 21 to e.g. 42 (if it still free) and try if the error depend on the ip adress. | |
| Oct 28, 2015 at 21:13 | answer | added | Matthew A. Flinchbaugh | timeline score: 1 | |
| Oct 28, 2015 at 14:15 | comment | added | Matthew A. Flinchbaugh | @PeterPaulKiefer yes i recreated .ssh with the new keys. And arp -n reports the correct MAC. Also other connections to the pi are aloud such as the web traffic, and webiopi traffic. | |
| Oct 28, 2015 at 14:11 | comment | added | Peter Paul Kiefer |
Did you create a new .ssh on each device with your private key id_rsa file on debian and an authorized_keys file on the raspi containing the public key after relocating? Another idea: Have you accidently another device with adress 192.168.1.21 in your network. That'd explain that weird behavior and also why it works again after a reboot of your pi. Next time it refuses connect, try arp -n on you debian box and check if the ip adress 192.168.1.21 is mapped with the correct MAC adress of you pi. Or try an nmap 192.168.1.1-255 on your debian box. Probably you have to install nmap before.
|
|
| Oct 28, 2015 at 12:45 | comment | added | Matthew A. Flinchbaugh | @PeterPaulKiefer Windows (putty), Linux, and Android (juicessh). All are refused. Firewall is not the issue, as it works for connections inside and outside of the firewall. I've done a reconfigure, still no change. I've also relocated my entire .ssh folder to .ssh2 on both my Debian server and the pi and it still starts refusing. | |
| Oct 28, 2015 at 12:42 | comment | added | Peter Paul Kiefer |
Ah, and don't forget to update the source index before reinstalling ssh. On debian sudo apt-get update.
|
|
| Oct 28, 2015 at 12:39 | comment | added | Peter Paul Kiefer |
Do you connect from linux, windows, OSX? Are you sure the firewall does not block under certain conditions? Do you have multiple private rsa files in your desktop computers .ssh directory? If so have you added the public key of all of them to your authorized_keys file on the pi? If on windows have you started pageant and added your private key? If all failes: Can you uninstall open_ssh on your pi and reinstall it again; or reconfigure it with sudo dpkg-reconfigure ssh if you have a debian on the pi (e.g. raspbian). After the next fail try dmesg and check the output for related hints.
|
|
| Oct 28, 2015 at 12:14 | comment | added | Matthew A. Flinchbaugh | @PeterPaulKiefer Yes same username on both, I've also tried adding the matthew@ just in case it would work and it does not change the results | |
| Oct 28, 2015 at 12:08 | comment | added | Peter Paul Kiefer |
Do you connect with the right username. e.g. ssh [email protected]. If you connect with ssh 192.168.1.21 without a username then, a user matthew must exist on the raspi. The public key is taken from that user account. Perhaps you connect with a existing username when it worked and without a username when it refused connection. It's just a guess ;-).
|
|
| Oct 28, 2015 at 11:32 | history | edited | Matthew A. Flinchbaugh | CC BY-SA 3.0 |
added 155 characters in body
|
| Oct 27, 2015 at 22:40 | answer | added | Mircea Baja | timeline score: 0 | |
| Oct 27, 2015 at 21:37 | answer | added | Patrick Cook | timeline score: 0 | |
| Oct 27, 2015 at 15:35 | comment | added | Matthew A. Flinchbaugh | Added the requested outputs | |
| Oct 27, 2015 at 15:32 | history | edited | Matthew A. Flinchbaugh | CC BY-SA 3.0 |
added 2 characters in body; added 13 characters in body; added 27 characters in body
|
| Oct 27, 2015 at 15:27 | history | edited | Matthew A. Flinchbaugh | CC BY-SA 3.0 |
deleted 1 character in body; added 1 character in body; added 10 characters in body
|
| Oct 27, 2015 at 15:20 | history | edited | Matthew A. Flinchbaugh | CC BY-SA 3.0 |
added 835 characters in body; added 82 characters in body
|
| Oct 27, 2015 at 14:43 | comment | added | goldilocks♦ |
Does /home/matthew/.ssh/id_rsa exist? Edit in the output from stat /home/matthew/.ssh/id_rsa and stat /home/matthew/.ssh.
|
|
| Oct 27, 2015 at 14:28 | comment | added | Matthew A. Flinchbaugh | I have 10+GB free | |
| Oct 27, 2015 at 14:26 | comment | added | Jakuje | do you have enough memory? Space on card? It used to happen to me also but now I have really long uptime. | |
| Oct 27, 2015 at 13:40 | history | edited | Phil B. | CC BY-SA 3.0 |
improved formatting
|
| Oct 27, 2015 at 12:51 | review | First posts | |||
| Oct 27, 2015 at 21:34 | |||||
| Oct 27, 2015 at 12:51 | history | asked | Matthew A. Flinchbaugh | CC BY-SA 3.0 |