Today I needed to reinstall it after updating the virtual host my HA is running on, but I can not see it in the list of add-ons in the store
Any idea why?
I have the same problem âŚ
Hi,
I switched from version 9.1.1 to 10.0.2 yesterday and now I canât access any more.
No â|pubkeyacceptedkeytypesâ listed any more
~ sshd -T|egrep "pubkeyauthentication|pubkeyacceptedkeytypes"
pubkeyauthentication yes
AddOn protocol:
userauth_pubkey: key type ssh-rsa not in PubkeyAcceptedAlgorithms [preauth]
I have fixed with new âssh-ed25519â key
1 Like
Hello @skank ,
you mean it work but whitout catt? so no more cast lovelace dashboard to a google_nest?
Is anyone found a solution please to cast lovelace again?
the service âcast.show_lovelace_viewâ work but dont show the all the menu, widgets, image, ⌠not so nice that the CATT option which you can control every thing from a Google_nest tabâŚ
Hi
I am using the SSH & Web Terminal v10.0.2, but I only can ssh using PuTTY if I type the password manually. If I use keys I get the message âServer refused our keyâ besides the ssh-rsa keys are ok.
So I can confirm what Thomas Grandor said that only generating âssh-ed25519â keys (on puttygen its also possible to do that) its possible to ssh using keys!
Thanks
FYI, your keys may work depending on when they were created, but youâll need to use the latest PuTTY 0.76 and the WinSCP 5.20 beta.
For me, PuTTY 0.76 was working but WinSCP 5.19 failed using the same key due to âkey type ssh-rsa not in PubkeyAcceptedAlgorithmsâ. Upgrading WinSCP to the 5.20 beta allowed it to work with that same key.
Iâve been having trouble with keys as well. Iâve used this add on previously but it wouldnât accept my RSA key. The same key Iâm using for another server fine.
I was getting the error
Permission denied (publickey,keyboard-interactive)
I ran ssh -vvv root@ip and I could see this under host keys.
debug3: order_hostkeyalgs: prefer hostkeyalgs: [email protected],[email protected],[email protected],ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521
Am I correct in thinking this means the server wonât accept an RSA key?
To test this, I created a new ECDSA key, added it to the config, then connected using ssh -vvv -i $HOME/.ssh/id_ecdsa root@ip and it connected straight away.
So does this confirm that RSA keys arenât working? Iâm on version 9.3.0.
Firstly thanks @frenck and all the other people who have contributed to make this add-on.
I have an issue using this add-on on an Samsung Android tablet where every key I press is shown twice. It works fine if used on PC. I have switched between bash and zsh which makes no difference. I turned echo off but then it doesnât show any chars entered. Has anyone seen this and know of a config setting or command that will stop this happening?
Thanks for this - I just came looking for a solution as I had broken fonts. Disabling âSite Privacy Protectionâ in the DuckDuck Go Privacy Essentials extension also worked for me (Chrome) 
I had the same problem. There was a message at the bottom of the Addons Store page that said to enable the âAdvanced Modeâ to access more community addons.
Go to your profile (icon in the bottom left of the panel if youâre using a desktop browser) and search for that option (it was in the first pane for me).
Once enabled, the addon was available for me to install.
Anyone have this using WinSCP or Putty with this addon?
I do have an ssh-rsa key that has worked for years but now I am getting this error
userauth_pubkey: key type ssh-rsa not in PubkeyAcceptedAlgorithms [preauth]
Addon config:
allow_agent_forwarding: false
allow_remote_port_forwarding: false
allow_tcp_forwarding: false
authorized_keys:
- '!secret ssh_web_addon'
compatibility_mode: true
password: ''
sftp: true
username: root
Hi!
I didnât connect with SSH with at least 1 year on my HASS.IO
I have a problem when I try to connect from my PC with PUTTY.
After typing the username, I get this error :
âno supported authentication methods available (server sent: publickey)â
But itâs working when I connect from my Android phone (with JuiceSSH) with the same configuration (same port, same key, same username).
I use a key in a file. WinSCP can connect too with the same username and the same .key
I don"t understand why itâs not working.
Please, do you have any idea?
I saw a video that explains to add the username in PUTTY Settings > Connection > Data > âAuto login usernameâ, but itâs still the same problem.
I am still using this add on with putty and it still works for me.
Itâs weird. It is working for ssh to the host debian system (which doesnât use the addon of course) and the web terminal is working too.
What errors are you seeing? I had some issues early on with my key. Had an extra LF.
as per above
userauth_pubkey: key type ssh-rsa not in PubkeyAcceptedAlgorithms [preauth]
my key has worked for years
Try to sign in with root as the user name. I have been using root for awhile for port 2222. It does not accept my user name for this port but it does for 22.
as you can see from the addon config I am using root and that is what is set in the PuTTY profile an WinSCP
my config:
allow_agent_forwarding: false
allow_remote_port_forwarding: false
allow_tcp_forwarding: false
authorized_keys:
- >-
ssh-rsa
hidden rsa-key-20210104
compatibility_mode: false
password: ~hidden
sftp: false
username: hidden