I’ve followed the SSH Access to the Host instructions, but am still unable to reach HassOS over ssh.
Here’s what I’ve done. My main question also is, what to expect. The role of the login command, in particular (instructions leave this a bit open).
USB stick with FAT32 formatting, with authorized_keys at the root, LF checked
place to RPi and “Import from USB”
the “System Log” shows this likely succeeded(?):
19-12-31 20:48:53 INFO (MainThread) [hassio.hassos] Syncing configuration from USB with HassOS.
19-12-31 20:48:53 INFO (MainThread) [hassio.host.services] Restart local service hassos-config.service
19-12-31 20:48:53 INFO (MainThread) [hassio.utils.gdbus] Call org.freedesktop.systemd1.Manager.RestartUnit on /org/freedesktop/systemd1
Expecting:
ssh [email protected] -p 22222 from my Mac (same network) would take me to something HassOS.
Actual:
$ ssh [email protected] -p 22222
ssh: connect to host hassio.local port 22222: Connection refused
Q: How should the last part look?
Edit: I tried with my userid instead, and that seems to take further. However, it doesn’t use the SSH key pairs.
I got the same problem, and i’m getting mad about it.
i tried the method mentioned on the dev-documentation …additionally, i tried creating the keys on another raspberry pi (dietpi) and simply did an "cp pub.key authorized_keys and uploaded this one via USB Stick.I tried rsa and ed25519
I can use this key files on any other linux host i got…but HassOS (which i really start to hate atm; Hass = hate in german):
This addon is asking me a password when I do the “login” as indicated here:
The “login” command works fine if I’m connected to the hardware using a keyboard and a monitor (the physical console), it gives me full access to the host, but is not working using the ssh.
Is that the way it is intended to be? only access through the physical console?
Sorry, my bad, I was confusing the internal ssh service with the ssh add on provided for advanced users. Once I got the internal one working then I could do the “login” command I needed.
I had this issue when using a USB with a GPT partition table: switching to an msdos partition table (and using a FAT32 partition labelled CONFIG) worked for me, with either rsa or ed25519 keys.
I am having exactly the same issues. Really checked the file name, checked LF, freshly formatted FAT32 USB stick recognized by hassio… Got the same results as OP, simply “connection refused”.