Version 20.0.0 breaks login

[jdeath]

Problem/Motivation

Updating to 20.0.0 breaks the login from an external SSH terminal when "use zsh" in not checked. There is a fix to copy .zprofile to .profile, but it gets removed every restart of the addon. Internal from webui works fine.

Checking "use zsh" works, but it is ugly!

Expected behavior

I expect it work work as before

Actual behavior

can log in as hassio, but do not have access to change files

Steps to reproduce

upgrade to 20.0.0

Proposed changes

Make addon copy the file everytime or just go back to what worked before

[scop]

Another workaround is to manually source ./.zprofile until this is fixed.

[tescophil]

This does not login to the correct shell regardless of whether use zsh is checked or not.

[barecool]

Seems like #826 breaks the addon if you upgrade and profile already exists if you have the previous workaround to add

init_commands:
  - ln -s /home/hassio/.profile /home/hassio/.zprofile

if you remove the init command then it works again

[danyrd92]

Hello, I have Home Assistant installed on a PC with Windows 11 using VirtualBox. I installed the SSH addon, but I can’t get it to start. I start the addon, click on "Open Web Interface," and the addon stops running.

What am I doing wrong?

[github-actions[bot]]

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

[scop]

Not stale I believe.

[scop]

Maybe someone with powers can remove the stale label here, as it didn't happen with my previous comment even though the github-actions message kind of implies it would.

[github-actions[bot]]

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

[scop]

!stale

[github-actions[bot]]

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

[scop]

Not stale.

[github-actions[bot]]

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

[scop]

Not stale.

[github-actions[bot]]

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

[trentbrown13]

Just upgraded to 21.1 and cannot ssh to ha from an external client - there is no error message displayed on the client, it merely returns the prompt. advanced ssh log shows onnection from 192.168.100.133 port 58420 on 192.168.100.227 port 22 rdomain "" Unable to negotiate with 192.168.100.133 port 58420: no matching key exchange method found. Their offer: curve25519-sha256,[email protected],ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,ext-info-c,[email protected] [preauth]

[jdeath]

1. Different Problem
2. Happened to me too. I updated my Putty to latest release and it worked again. Sometimes they depreciate encryption and need to update putty.

You could also try setting compatibility_mode: true in the addon options to see if it will allow your old client to connect.

[trentbrown13]

Ah thanks! Compatabity-mode was already set to false. I was using a wsl linux terminal where it failed (that has always been my default ssh client) so switched to a native ubuntu client and it connected right away.

I then updated my wsl2 ssh client but it still will not connect.

This is a very good workaround for me ( I have lots of ubuntu machines ;) to use as clients but would still like to see this fixed so all clients can connect. Windows is my default OS for work so I use WSL quite a bit.

thank you very much for the quick response!

[jdeath]

I meant set compatibility_mode: true sorry. that might fix it.

[github-actions[bot]]

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!