Trouble logging in to pi through ssh

[sa250039]

I'm sorry this is probably a stupid question and im a newb. but I am having trouble ssh'ing into the pi. I use putty to ssh and get to the log in screen but no username and password work. I use the ip address that pops onto my LCD screen as the log in, I've also used admin@myip, along with the password raspiblitz. but I have never been able to log in, it just freezes my putty and tells me connection error. the closest I ever got was to use pi as the log in but it just forwarded the screen from the LCD saying what my log in and password is and that's it. any help would be appreciated .

[fluidvoice]

It should be admin@yourIP but if your node is syncing you may have to wait a while before it replies asking for you to enter your password. Once you login, you'll have to hit ctrl-c to get out of the menu and to the command prompt. Perhaps you forgot your password?

[rootzoll]

Make sure that you are on the same local network. What is ping [ip-of-your-node] say?

If you are in WLAN check that you dont have "IP isolation" switched on at your router (its an edge casem but can happen). Also if you have a VPN or firewall running on your laptop maybe switch that off and try again.

[sa250039]

Make sure that you are on the same local network. What is ping [ip-of-your-node] say?
If you are in WLAN check that you dont have "IP isolation" switched on at your router (its an edge casem but can happen). Also if you have a VPN or firewall running on your laptop maybe switch that off and try again.

Pinging 192.168.0.32 with 32 bytes of data:
Reply from 192.168.0.32: bytes=32 time=102ms TTL=64
Reply from 192.168.0.32: bytes=32 time=5ms TTL=64
Reply from 192.168.0.32: bytes=32 time=4ms TTL=64
Reply from 192.168.0.32: bytes=32 time=6ms TTL=64
Ping statistics for 192.168.0.32:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 4ms, Maximum = 102ms, Average = 29ms
and I don't have a vpn or firewall running at the moment.
and no ip isolation.
I can connect enough to reach the log in screen but once I try the admin@myip and password raspiblitz it just tells me access denied. if I use log in pi and the password raspiblitz it takes me to a mirror of the screen on the little lcd but I cannot interact with it.

[rootzoll]

OK so you can reach your Pi - so ist not a network issue.
Can you try to logon with: bitcoin@myip ... ist to see if that works.

[lolrip]

I am having the same issue. I can ping the host and receive replies but when I ssh to admin (or bitcoin@) I receive:

Connection reset by 10.10.10.57 port 22

I attempted to mount the sd card to check SSH config, permissions, etc. but it will not allow me to mount "rootfs"

nmap results below showing the port is open:

Nmap scan report for 10.10.10.57 Host is up (0.0063s latency). Not shown: 999 closed ports PORT STATE SERVICE 22/tcp open ssh

[lolrip]

Sorry for the spam.

I solved this issue by mounting the SD card and removing all of the SSH keys from /etc/ssh/

rm /mnt/rootfs/etc/ssh/*key*

I am now able to SSH to the pi

[m8tion]

I use Linux Mint 19 and for whatever reason my ssh connections only works if I call them with root privileges ("sudo ssh admin@myip"). Maybe you can try this if you are on Linux or launch your terminal / ssh app on windows as a superuser.

[Zemekis11]

Hi I'm getting the same issue as sa250039 up above. The odd thing is that after brute force trying and retrying without changing anything it let me through once. I was able to complete the torrent download and then when it asked me to ssh using Password A....right back to infinite access denied.

When I first attempt to ssh into the raspiblitz, PuTTY gives me a warning about the connection and asks if I want to add it to my cache. Should I be agreeing?

[Strikeaxe]

Make sure that you are on the same local network. What is ping [ip-of-your-node] say?
If you are in WLAN check that you dont have "IP isolation" switched on at your router (its an edge casem but can happen). Also if you have a VPN or firewall running on your laptop maybe switch that off and try again.

Pinging 192.168.0.32 with 32 bytes of data:
Reply from 192.168.0.32: bytes=32 time=102ms TTL=64
Reply from 192.168.0.32: bytes=32 time=5ms TTL=64
Reply from 192.168.0.32: bytes=32 time=4ms TTL=64
Reply from 192.168.0.32: bytes=32 time=6ms TTL=64
Ping statistics for 192.168.0.32:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 4ms, Maximum = 102ms, Average = 29ms
and I don't have a vpn or firewall running at the moment.
and no ip isolation.
I can connect enough to reach the log in screen but once I try the admin@myip and password raspiblitz it just tells me access denied. if I use log in pi and the password raspiblitz it takes me to a mirror of the screen on the little lcd but I cannot interact with it.

I had the same issue. I was successful logging in using only admin + raspiblitz

[bucko13]

Having the same issue after everything working without any problem (able to sync the node and everything). RTL doesn't work and ssh doesn't work. ping responds with 64 bytes from 192.168.2.137: icmp_seq=9 ttl=64 time=2.119 ms. using sudo does not work either. What's strange is that on the router (I have a dd-wrt router) in the DHCP clients it does not have the device listed. I also tried to plug in a keyboard to the raspbi and reboot it but the keyboard isn't responding which seems weird.

[Zemekis11]

I was able to successfully login using a different SSH software, somehow I couldn't get PuTTY to work even after 10 hours tooling around with it so I tried Terminus for Android and voila, it worked on my first try! If PuTTY is being a troublemaker, don't beat your head against it for too long, just try a different device or piece of software. Currently 10 days into syncing, so even if you get past this hurdle, remember that there are a lot more days of waiting ahead...

[openoms]

I was able to successfully login using a different SSH software, somehow I couldn't get PuTTY to work even after 10 hours tooling around with it so I tried Terminus for Android and voila, it worked on my first try! If PuTTY is being a troublemaker, don't beat your head against it for too long, just try a different device or piece of software. Currently 10 days into syncing, so even if you get past this hurdle, remember that there are a lot more days of waiting ahead...

Termius on Android is a great tool indeed. Allows you to try from a whole different Operating system.

On Windows Kitty is a good alternative to Putty: https://www.fosshub.com/KiTTY.html

Also if someone is happy to dive in a bit Windows 10 can run a whole Linux with native ssh: https://docs.microsoft.com/en-us/windows/wsl/install-win10

[bucko13]

I'm on a mac so I don't think the ssh issue is related to terminal application (using iTerm fwiw)