I can see bluez listed in the Dockerfile, but don’t seem to be able to find it/run it in v3.1.0 or v3.2.0. Do I have to do something in my configuration files to enable it?
Is it possible to start this via Web UI -> Developer Tools -> Services -> hassio.addon_start ?
If so, what is the service data?
Yes, it should be:
{
"addon": "a0d7b954_ssh"
}
Edit: this ofcourse assumes you already set up the Config.
It needs to have either a SSH password or authorized keys.
Because of security reasons there is no default.
Release v3.3.0
Today is the birthday of the Community Hassio Add-ons project! 
Let celebrate with a packed release!
This release adds support for GPIO! That would make debugging much easier, right?
Also added: Mosh! Mosh is a replacement for interactive SSH terminals that allows roaming, supports intermittent connectivity. It’s more robust and responsive, especially over Wi-Fi, cellular, and long-distance links.
Furthermore, the security has been tightened. Remember, anyone who gains access to this add-on, literally controls your whole system! So, passwords are now securely checked against the HaveIBeenPwned password database using K-Anonymity and authentication on the Web Terminal is now enforced.
Questions? Consider joining our Discord server: https://discord.me/hassioaddons
Added
- Adds support for GPIO (#28)
- Adds support for Mosh mobile shell
- Checks used password against HaveIBeenPwned
- Enforces the use of Web Terminal authentication
- Adds support for colordiff (#30)
Changed
- Upgrades base image to v2.1.0
- Enables SSL by default
- Updates README with latest changes
4 Likes
thanks for the continued support and reconsidering about mosh 
1 Like
Release v3.4.0
Only 6 days passed since the previous release, nevertheless, I’m shipping a really big update again!
It now supports the use of your Home Assistant secrets file! So you can now use !secret ssh_password as your password and the add-on will fetch the actual password from your secrets file. 
This release also adds access to the Docker instance running on your Hassio 
A really powerful, but dangerous feature. So added a warning: With great power comes great responsibility. This Docker feature is disabled by default, but can be enabled it by running the docker command.
Added
- Adds warning with great power comes great responsibility
- Documents secrets support
- Adds Docker support
Fixed
- Adds access to /dev/mem to support GPIO better
Changed
- Upgrades base image to v2.1.1
- Sets default Shell
- Updates README with latest changes
- Updates Discord links
Questions? Join our Discord server! https://discord.me/hassioaddons
Enjoying my add-ons? Consider supporting my work: https://patreon.com/frenck
2 Likes
Release v3.4.1
Changed
- Upgrades base image to v2.1.2
Questions? Join our Discord server! https://discord.me/hassioaddons
Enjoying my add-ons? Consider supporting my work: https://patreon.com/frenck
Sorry if this is the wrong place to post this, but I am getting the following error when trying to start v.3.4.1 of SSH Terminal:
Error loading shared library libjson-c.so.4: Exec format error (needed by /usr/bin/ttyd)
The plugin won’t start
Hi @frenck I have just started having some issues with this addon… I use a bluetooth keyboard with my iPad and it’s just started not working is say I am using nano to edit a file, it is not recognising the control button so I can’t ctrl+x to exit. Also tried command + x but that doesn’t work either. These keys do work in other applications.
It’s possible it might be that I am on public iOS Beta 12 but I think it’s the addon as it works in other apps.
My options are:
{
"log_level": "info",
"ssh": {
"enable": true,
"port": xxx,
"username": "root",
"password": "",
"authorized_keys": [
"ssh-rsa xxx"
],
"sftp": true,
"compatibility_mode": false,
"allow_agent_forwarding": false,
"allow_remote_port_forwarding": false,
"allow_tcp_forwarding": false
},
"web": {
"enable": true,
"port": 7681,
"username": "!secret ssh_user",
"password": "!secret ssh_pass",
"ssl": false,
"certfile": "fullchain.pem",
"keyfile": "privkey.pem"
},
"share_sessions": true,
"packages": [],
"init_commands": []
}
Release v3.5.0
- Upgrades docker to 18.06.1-r0
- Upgrades ncurses to 6.1_p20180818-r1
- Upgrades openssh to 7.7_p1-r3
- Upgrades bind-tools to 9.12.2_p1-r0
- Upgrades ttyd to 1.4.2
- Upgrades Hassio CLI to 1.4.0
- Upgrades base image to v2.3.0
- Adds Hassio API security role
- Upgrades OpenSSL to 1.0.2p-r0
- Adds documentation about shared_sessions option
- Fixes copy/paste in SSH when using shared sessions
Questions? Join our Discord server! https://discord.me/hassioaddons
Enjoying my add-ons? Consider supporting my work: https://patreon.com/frenck
stuck with this error in the log:
[2018/09/30 00:17:05:9092] ERR: lws_tls_server_vhost_backend_init: SSL_CTX_load_verify_locations unhappy
[2018/09/30 00:17:05:9708] ERR: Unable to load SSL Client certs file from -- client ssl isn't going to work
Connection from 116.31.116.44 port 44352 on 192.168.1.57 port 22
Unable to negotiate with 116.31.116.44 port 44352: no matching key exchange method found. Their offer: diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1 [preauth]
Connection from 27.40.23.221 port 39006 on 192.168.1.57 port 22
Unable to negotiate with 27.40.23.221 port 39006: no matching key exchange method found. Their offer: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 [preauth]
Uninstalled the default SSH add-on, (didnt restart HA though, should I?)
Keys method is not selected, login and Password is. Why is this error still about the keys then?
thx for any help,
M
Hmm. So I’ve moved my install from a Pi to a Docker installation on Debian (https://github.com/home-assistant/hassio-build/tree/master/install#install-hassio). I’ve restored my snapshot, but I just can’t get this working. Essentially I’ve put in my authorized key, but it’s insisting I set a password (which seems counterproductive).
I’ve tried reinstalling the addon but that doesn’t seem, to help.
Any ideas?
[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] 10-hassio: applying...
[fix-attrs.d] 10-hassio: exited 0.
[fix-attrs.d] 50-ssh: applying...
[fix-attrs.d] 50-ssh: exited 0.
[fix-attrs.d] 51-sudoers: applying...
[fix-attrs.d] 51-sudoers: exited 0.
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing...
-----------------------------------------------------------
Hass.io Add-on: SSH & Web Terminal v3.5.0
SSH & Web Terminal access to your Home Assistant instance
parse error: Expected string key before ':' at line 1, column 4
ERROR: Unknown HTTP error occured
From:
parse error: Expected string key before ':' at line 1, column 4
ERROR: Unknown HTTP error occured
By:
-----------------------------------------------------------
amd64 / Debian GNU/Linux 9 (stretch) / HA 0.79.3 / SU 133 / stable
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing...
Log level is set to INFO
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] 02-updates.sh: executing...
INFO: You are running the latest version of this add-on
[cont-init.d] 02-updates.sh: exited 0.
[cont-init.d] 10-requirements.sh: executing...
FATAL: You need to set a password!
[cont-init.d] 10-requirements.sh: exited 1.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] 99-message.sh: executing...
-----------------------------------------------------------
Oops! Something went wrong.
We are so sorry, but something went terribly wrong when
starting or running this add-on.
Be sure to check the log above, line by line, for hints.
-----------------------------------------------------------
[cont-finish.d] 99-message.sh: exited 0.
[cont-finish.d] done.
[s6-finish] syncing disks.
[s6-finish] sending all processes the TERM signal.I’m running into the same issue after updating home assistant from v0.73.1 to v0.79.1 and the addon from v2.5.0 to v3.5.0. I tried resetting the config to defaults and just adding my SSH key to the authorized keys array but unfortunately that didn’t fix the errors.
Just in case it’s relevant, I’m running hassio on a Raspberry Pi 3 B+, installed using https://github.com/dale3h/hassio-installer
Update: it seems it was talking about the password in the web section, setting one there worked for me.
Hi I installed the ssh terminal add-on version 3.5.0 on Hass-io 0.79.3. Attached my config. When I press start it after a while returns to the off position. I’m interested in accessing the terminal from the panel only. I also tried it in the config.yaml. Where am I wrong? Thanks in advance to those who want to help me!
{
“log_level”: “info”,
“ssh”: {
“enable”: true,
“port”: 22,
“username”: “hassio”,
“password”: “prova”,
“authorized_keys”: [],
“sftp”: false,
“compatibility_mode”: false,
“allow_agent_forwarding”: false,
“allow_remote_port_forwarding”: false,
“allow_tcp_forwarding”: false
},
“web”: {
“enable”: true,
“port”: 7681,
“username”: “hassio”,
“password”: “prova”,
“ssl”: true,
“certfile”: “fullchain.pem”,
“keyfile”: “privkey.pem”
},
“share_sessions”: true,
“packages”: [],
“init_commands”: []
}
#########################
panel_iframe:
terminal:
title: Terminal
icon: mdi:console
url: http://hassio.local:7681
Without some logs we can’t help you, please provide them. My two guesses at the moment are:
- The password you’ve set is insecure
- You enabled SSL while there are no certificates available
I tried this addon on my odroid C2. It doesn’t start and the only thing I see in the log is the fact I have no sound device. Any chance to bypass this and launch this addon without sound device?
Anyone got any ideas?
This is a bug with Hass.io, which has been addressed and should be fixed soon.
This is outside the scope of the add-on, so nothing I can do.
Did you set a web password for the Web Terminal?
1 Like
Thank you for your feedback. I will wait.