SSH connection refused via Putty on Windows 10

Archive - Mycroft Project This category is being retired - Support
1

With the Mark ii dev kit freshly installed and connected to wifi, I followed these directions to enable SSH:

The problem is that it ONLY gives directions for Linux. I’m running Windows on a laptop :confused:

I used the same command (ssh-keygen -t rsa) and Windows generated the key pair. I opened the public key and succeeded in adding it to my device via mycrofts website under my device.

I use PuTTY on Windows for SSH. Putty has PuttyGen to convert RSA or DSA key pairs into Putty format as seen here:

https://electrictoolbox.com/putty-rsa-dsa-keys/#:~:text=Some%20SSH%20servers%20require%20the%20use%20of%20these,and%20must%20convert%20them%20using%20the%20PuTTYGen%20application.

The problem is I’m still unable to connect and get : Network error: Connection Refused

I can’t be the only one trying to connect from Windows and PuTTY… or am I?

2

Are you sure sshd is running on the Linux side? Can you get a local terminal session and issue ‘service sshd status’?

-Mike Mac
3

I missed that the Mark II is on port 8222 rather than 22 so it works now. Oops.

That being said I was able to get in no problemo. However I might as well ask, if I put a keyboard onto the Mark II Dev how do I get to the command line?

1 Like
4

You need to connect a keyboard and a monitor. Then you will see the login prompt. That prompt is the same you used when copying the keypair

5

Since we currently don’t have the ability to voice install new skills/play with Mark II in general without the terminal can someone please post these instructions IN THE MYCROFT II SETUP NOTES? Maybe I missed it but I have spent hours looking for how to get into this thing from Windows or directly - a sidebar with “so you’re a noob…here is how to get into your device” in big bold red letters during the setup would be really nice

1 Like
6

If you’re getting “SSH connection refused using PuTTY on Windows 10, it usually means the SSH service (sshd) isn’t running on the target machine or port 22 is blocked. First, ensure the device is powered on and reachable (try pinging it). Then, use a different method, like serial or console access, to log in and check if sshd is active (sudo systemctl status ssh). Also, verify that the firewall or network settings aren’t blocking the connection. Rebooting the device can help reset the network stack, too.

Hope it helps!