I love the idea of this add-on. I followed the official HA developer guide to create a public/private key but couldnât get it to work. Then installed this add-on, but still no luck. When trying to ssh to port 22222 Iâm getting error âConnection refusedâ.
This is what the logs of the add on show:
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
no vda1 config found
no sda1 config found
no sdb1 config found
no mmcblk0p1 config found
no nvme0n1p1 config found
This Configurator did it's job. Perform a hard-power-off now. This configurator only works once and is no longer needed.
Iâm running HA on an Odroid N2+. Any suggestions on how to troubleshoot/fix?
i follow the docâŚbut in the HassOs22222 AddOn i put the wrong key.
In config/.ssl/ you have the id_rsa.pub and this is the key you need to paste in the âconfigurationâ part of this AddOn. this key finish by âroot@a0d7b954-sshâ.
I have the ssh and web terminal AddOn from @frenck and its not the same key, its end with ârsa-key-20190824â
Hope someone can help. Not clued up on SSH but needing to get this working for full Samba-nas addon support (medialibrary).
Constantly getting pop up via Putty and terminal app -
" No supported authentication methods available (server sent: public key)"
my log:
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
no vda1 config found
no sda1 config found
no sdb1 config found
no mmcblk0p1 config found
no mmcblk1p1 config found
already added this key to nvme0n1p1
This Configurator did it's job. Perform a hard-power-off now. This configurator only works once and is no longer needed.
Is it because public key is being added to nvme0n1p1 ?
Iâm trying to get this addon working to run SambaNas addon with an external USB but i canât get it working
This is the log when I run this addon:
[s6-init] making user provided files available at /var/run/s6/etcâŚexited 0.
[s6-init] ensuring user provided files have correct permsâŚexited 0.
[fix-attrs.d] applying ownership & permissions fixesâŚ
[fix-attrs.d] done.
[cont-init.d] executing container initialization scriptsâŚ
[cont-init.d] done.
[services.d] starting services
[services.d] done.
no vda1 config found
no sda1 config found
no sdb1 config found
no mmcblk0p1 config found
no mmcblk1p1 config found
no nvme0n1p1 config found
This Configurator did itâs job. Perform a hard-power-off now. This configurator only works once and is no longer needed.
Iâm running Home Assistant OS 7.0 in a rpi4 and I have tried this addon and also using a USB with an authorized_keys file. I also use the SSH & web terminal Addon to enter HA. With that terminal I have seen that in /root/.ssh/ folder there is only a file called known_hosts with a public? key for port 22222 but that key is not the one I have generated. I think a file called id_rsa is supossed to be found also in that directory.
In addition, in SambaNas plugin logs I can read:
Warning: Permanently added â[192.168.1.4]:22222â (ECDSA) to the list of known hosts.
Load key â/root/.ssh/id_rsaâ: invalid format [email protected]: Permission denied (publickey).
What am I doing wrong? Any help would be appreciated!
Just wanted to say THANK YOU @adamoutler1 for this (and for the I2C configurator)! I spent a couple of hours trying to understand the convoluted, poorly documented process from HA maintainers, and I ended up being able to access via ssh, but only with the USB card inserted! I find it completely unbelievable that it is faster to install a UI plugin than to execute a couple of commands (used linux for 20 years), because in their infinite wisdom they decided to make an âeasyâ process based on a USB card and without any feedback or logging. Good job, but horrible experience with HA maintainers.
Iâm running hassio.ova on ESXi and am logging into the supervisor using the Terminal Add-On with a password. I copied the contents of authorized_keys and ran this configurator but Putty seems to want a private key. Is a private-public key pair the only authentication method supported?