Unable to connect to the server (anymore)

[thomdietrich]

Unable to connect to the server (anymore)

[kszys]

So... mystery solved, though I still have no clue why it was working before, and not any longer, as I have not made any changes on the server when it stopped working...

Anyway - the clue is in the statement: This account is currently not available. This message is apparently provided by the nologin shell. So it was sufficient to change the default shell for ha user to bash and magically everything works...

After some thinking, I decided that ha user should not really need a login shell on my server. So I changed the default shell back to nologin and added instead option -N in the additional options in autossh configuration - and it still works!

Again - why it worked before, but no any longer - no idea.

[ThomDietrich]

Hey!
I am sorry, this might have been caused by a change here...
#1
The user needed the login shell to see relevant information. That's why I moved the -N from default to "additonal options", forgetting that users like you might be affected.

Btw your case sounds like you would benefit from he Docker based SSH daemon on the server, which I've described in DOCS.md

[kszys]

You are probably right. I got to the bottom of it, so no issues. But perhaps it would be useful to document it a bit more explicitly - either use the -N option, or ensure the user has a shell defined.

For Docker - you are probably right, but I do not use Docker on my server, and I was too lazy to set it up just for this ;)

[ThomDietrich]

The -N is part of the default options now: 07316f3
Of course existing users won't have that in their setup after a regular update. I will investigate ho to add a document with release notes for a home assistant addon and provide the info through that. It's not ideal but every user with an issue like yours will probably have a look at the version changes first. Agreed?

[ThomDietrich]

I'm happy with that :)

[kszys]

Looks good! Thanks!