Get Zerotier or similar on your dad’s PC. Alternative is to use noMachine or another remote access solution.
If you were to go the hypervisor way things are even more flexible as you can then see the entire network, including all hardware. However you can achieve full LAN access with Zerotier or similar as well.
Ran into the same issue and found some solutions (but I’m clearly no expert) :
You could use the following :
ssh -t user@your-ha-host 'zsh -l'
This will request a tty from the server [-t] and ensure proper user login phase using zsh [zsh -l] (that’s an L). that should put you right into the tmux used on the web interface.
I tried and fiddle with these two options, and I think that removing [-l] will put you into zsh but not the tmux, but I’m getting confused with user configs, login config, etc. If anyone can shed some light, it’d be welcome!
Hi
I am using this on a test machine and just updated it from 2024.6.4 to 2024.10.4.
Now when I try to ssh from Windows Terminal it doesn’t display the banner message and the prompt looks weird.
Any idea what could be the issue?
Otherwise everything seems to work. I can still print the banner with ha banner. And it also looks fine in the web terminal.
Originally I posted about that as a symptom of using mosh + tmux all in one line like I do to start sessions on other Linux hosts:
mosh hassio@hasshost -- tmux a
I just worked around it by doing it in two steps mosh hassio@hasshost then tmux a.
The cause of that problem is that /home/hassio/.profile doesn’t run which does sudo -i to switch from hassio to “root” in the container.
I’ve seen that starting a month or two ago. I thought I broke something in my init script or something. Good to know it isn’t just me.
The cause is similar to above, for some reason /home/hassio/.profile doesn’t run or fails. So the sudo to root doesn’t happen.
The .profile file only contains “exec sudo -i”, which does not appear to be the cause (commenting it out doesn’t remove the symptom).
The question is why isn’t .profile being run? If I run it source ~/.profile (which as just pointed out just does sudo -i ) you wind up in the right state, running as “root” in the container and running the dot files in /root like .zshrc
For me, /home/hassio/.profile is owned by root with mode 0644. I’ve changed that to 0755 and with ownership hassio:hassio but it still doesn’t run correctly.
Do you use the add-on’s init commands or install additional packages? I think the think to do is try this on a fresh install with the default config.
As a result of this I realized I can work around this and get mosh + tmux to run in a single line:
mosh hassio@hasshost -- sudo -i tmux a -t homeassistant
Ok, now I understand what’s breaking the prompt and causing the sudo to root not to happen. The change may have appeared in 19.0. See the github issue: Shell prompt regression #788 for all the details. Note that issue is misnamed.
I believe it was broken by PR #755 which changed the default shell from /bin/sh to /bin/zsh for the added users. However, the script creates only .profile, while, I’m pretty sure that zsh will not run .profile by default for a login shell, and thus requires .zprofile to exist.
A temporary hack is to add the following to “init_commands” configuration option and restart:
This does not only not not but also breaks the terminal addon from starting with current versions because I have no such hassio username.
I tried using ~ or $HOME to make it work, even . while assuming the it would be the current directly but nope, no way to make it work in a portable way. Unless you use the full path it will not work.
Add-on version: 19.0.0
You are running the latest version of this add-on.
System: Home Assistant OS 13.2 (aarch64 / raspberrypi5-64)
Home Assistant Core: 2024.11.3
Home Assistant Supervisor: 2024.11.4
I just updated my addon to 20.0.0 and had to copy .zprofile to .profile for it to work again in an external ssh client (works ok from terminal). Not sure why don’t include this stuff in release notes for new versions!
Edit: This changed gets removed on a home assistant restart. Why???
selecting “use zsh” from config allows it to work from outside terminal, but zsh is lame!
IMHO the add-on restarts and all contant that was not in he container image is lost - except from the configuration.
See the gist I shared above which allows me to setup the environment again upon the first login after restart: Home Assistant Community Add-on: SSH & Web Terminal - #582 by le_top .
Hopefully I can gain some traction on this request – fingers crossed.
I’m running virtualized HAOS 14.2 along with Advanced SSH & Web Terminal version 20.0.0. For some reason the Advanced SSH & Web Terminal wont start for me. I looked the logs and here is what I’m getting:
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting
-----------------------------------------------------------
Add-on: Advanced SSH & Web Terminal
A supercharged SSH & Web Terminal access to your Home Assistant instance
-----------------------------------------------------------
Add-on version: 20.0.0
You are running the latest version of this add-on.
System: Home Assistant OS 14.2 (amd64 / qemux86-64)
Home Assistant Core: 2025.2.4
Home Assistant Supervisor: 2025.02.1
-----------------------------------------------------------
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
Log level is set to INFO
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-ssh: starting
s6-rc: info: service init-mysql: starting
s6-rc: info: service init-mosquitto: starting
s6-rc: info: service init-docker: starting
s6-rc: info: service init-docker successfully started
s6-rc: info: service init-mysql successfully started
s6-rc: info: service init-mosquitto successfully started
s6-rc: info: service init-ssh successfully started
s6-rc: info: service init-user: starting
fetch https://dl-cdn.alpinelinux.org/alpine/v3.21/main/x86_64/APKINDEX.tar.gz
fetch https://dl-cdn.alpinelinux.org/alpine/v3.21/community/x86_64/APKINDEX.tar.gz
v3.21.3-25-gd11b6459f45 [https://dl-cdn.alpinelinux.org/alpine/v3.21/main]
v3.21.3-24-g76530f97e25 [https://dl-cdn.alpinelinux.org/alpine/v3.21/community]
OK: 25441 distinct packages available
ERROR: unable to select packages:
musl-1.2.5-r8:
breaks: musl-dev-1.2.5-r9[musl=1.2.5-r9]
satisfies: world[musl=1.2.5-r8]
apk-tools-2.14.6-r2[musl>=1.2.3_git20230424]
apk-tools-2.14.6-r2[so:libc.musl-x86_64.so.1]
libbsd-0.12.2-r0[musl]
libbsd-0.12.2-r0[so:libc.musl-x86_64.so.1]
isl26-0.26-r1[so:libc.musl-x86_64.so.1]
bind-libs-9.18.32-r0[so:libc.musl-x86_64.so.1]
libblkid-2.40.2-r4[so:libc.musl-x86_64.so.1]
rsync-3.3.0-r1[so:libc.musl-x86_64.so.1]
dash-0.5.12-r2[so:libc.musl-x86_64.so.1]
gcc-14.2.0-r4[so:libc.musl-x86_64.so.1]
wget-1.25.0-r0[so:libc.musl-x86_64.so.1]
procps-ng-4.0.4-r2[so:libc.musl-x86_64.so.1]
libpcap-1.10.5-r0[so:libc.musl-x86_64.so.1]
perl-5.40.0-r3[so:libc.musl-x86_64.so.1]
alsa-lib-1.2.12-r0[so:libc.musl-x86_64.so.1]
g++-14.2.0-r4[so:libc.musl-x86_64.so.1]
libffi-3.4.6-r0[so:libc.musl-x86_64.so.1]
alsa-utils-1.2.12-r2[so:libc.musl-x86_64.so.1]
abseil-cpp-log-internal-format-20240722.0-r0[so:libc.musl-x86_64.so.1]
libevent-2.1.12-r7[so:libc.musl-x86_64.so.1]
bluez-5.79-r0[so:libc.musl-x86_64.so.1]
bind-tools-9.18.32-r0[so:libc.musl-x86_64.so.1]
nmap-7.95-r1[so:libc.musl-x86_64.so.1]
jansson-2.14-r4[so:libc.musl-x86_64.so.1]
patch-2.7.6-r10[so:libc.musl-x86_64.so.1]
json-c-0.18-r0[so:libc.musl-x86_64.so.1]
mii-tool-2.10-r3[so:libc.musl-x86_64.so.1]
bash-5.2.37-r0[so:libc.musl-x86_64.so.1]
gcompat-1.1.0-r4[so:libc.musl-x86_64.so.1]
xxd-9.1.0707-r0[so:libc.musl-x86_64.so.1]
unzip-6.0-r15[so:libc.musl-x86_64.so.1]
fstrm-0.6.1-r4[so:libc.musl-x86_64.so.1]
libeconf-0.6.3-r0[so:libc.musl-x86_64.so.1]
python3-3.12.8-r1[so:libc.musl-x86_64.so.1]
libxau-1.0.11-r4[so:libc.musl-x86_64.so.1]
binutils-2.43.1-r1[so:libc.musl-x86_64.so.1]
net-tools-2.10-r3[so:libc.musl-x86_64.so.1]
mariadb-client-11.4.4-r1[so:libc.musl-x86_64.so.1]
busybox-1.37.0-r8[so:libc.musl-x86_64.so.1]
less-668-r0[so:libc.musl-x86_64.so.1]
openssh-client-common-9.9_p1-r2[so:libc.musl-x86_64.so.1]
abseil-cpp-stacktrace-20240722.0-r0[so:libc.musl-x86_64.so.1]
lz4-libs-1.10.0-r0[so:libc.musl-x86_64.so.1]
sqlite-libs-3.47.1-r0[so:libc.musl-x86_64.so.1]
libmd-1.1.0-r0[so:libc.musl-x86_64.so.1]
libucontext-1.3.2-r0[so:libc.musl-x86_64.so.1]
libpsl-0.21.5-r3[so:libc.musl-x86_64.so.1]
keyutils-libs-1.6.3-r4[so:libc.musl-x86_64.so.1]
sudo-1.9.16_p2-r0[so:libc.musl-x86_64.so.1]
curl-8.11.1-r0[so:libc.musl-x86_64.so.1]
abseil-cpp-base-20240722.0-r0[so:libc.musl-x86_64.so.1]
eudev-libs-3.2.14-r5[so:libc.musl-x86_64.so.1]
sqlite-3.47.1-r0[so:libc.musl-x86_64.so.1]
libcap2-2.71-r0[so:libc.musl-x86_64.so.1]
libvorbis-1.3.7-r2[so:libc.musl-x86_64.so.1]
vim-9.1.0707-r0[so:libc.musl-x86_64.so.1]
krb5-libs-1.21.3-r0[so:libc.musl-x86_64.so.1]
libuv-1.49.2-r0[so:libc.musl-x86_64.so.1]
libx11-1.8.10-r0[so:libc.musl-x86_64.so.1]
libxcb-1.16.1-r0[so:libc.musl-x86_64.so.1]
utmps-libs-0.1.2.3-r2[so:libc.musl-x86_64.so.1]
mosh-client-1.4.0-r12[so:libc.musl-x86_64.so.1]
libpanelw-6.5_p20241006-r3[so:libc.musl-x86_64.so.1]
abseil-cpp-die-if-null-20240722.0-r0[so:libc.musl-x86_64.so.1]
pwgen-2.08-r3[so:libc.musl-x86_64.so.1]
git-2.47.1-r0[so:libc.musl-x86_64.so.1]
soxr-0.1.3-r7[so:libc.musl-x86_64.so.1]
fftw-single-libs-3.3.10-r6[so:libc.musl-x86_64.so.1]
pulseaudio-utils-17.0-r4[so:libc.musl-x86_64.so.1]
libsndfile-1.2.2-r2[so:libc.musl-x86_64.so.1]
abseil-cpp-spinlock-wait-20240722.0-r0[so:libc.musl-x86_64.so.1]
tdb-libs-1.4.12-r0[so:libc.musl-x86_64.so.1]
zsh-5.9-r4[so:libc.musl-x86_64.so.1]
abseil-cpp-raw-hash-set-20240722.0-r0[so:libc.musl-x86_64.so.1]
abseil-cpp-log-globals-20240722.0-r0[so:libc.musl-x86_64.so.1]
musl-utils-1.2.5-r8[so:libc.musl-x86_64.so.1]
abseil-cpp-cordz-handle-20240722.0-r0[so:libc.musl-x86_64.so.1]
nghttp2-libs-1.64.0-r0[so:libc.musl-x86_64.so.1]
abseil-cpp-log-internal-log-sink-set-20240722.0-r0[so:libc.musl-x86_64.so.1]
diffutils-3.10-r0[so:libc.musl-x86_64.so.1]
abseil-cpp-crc-internal-20240722.0-r0[so:libc.musl-x86_64.so.1]
libflac-1.4.3-r1[so:libc.musl-x86_64.so.1]
abseil-cpp-log-internal-globals-20240722.0-r0[so:libc.musl-x86_64.so.1]
cjson-1.7.18-r0[so:libc.musl-x86_64.so.1]
libstdc++-14.2.0-r4[so:libc.musl-x86_64.so.1]
dbus-1.14.10-r4[so:libc.musl-x86_64.so.1]
libbz2-1.0.8-r6[so:libc.musl-x86_64.so.1]
brotli-libs-1.1.0-r2[so:libc.musl-x86_64.so.1]
glib-2.82.4-r0[so:libc.musl-x86_64.so.1]
libcom_err-1.47.1-r1[so:libc.musl-x86_64.so.1]
acl-libs-2.3.2-r1[so:libc.musl-x86_64.so.1]
file-5.46-r2[so:libc.musl-x86_64.so.1]
libogg-1.3.5-r5[so:libc.musl-x86_64.so.1]
abseil-cpp-crc32c-20240722.0-r0[so:libc.musl-x86_64.so.1]
abseil-cpp-int128-20240722.0-r0[so:libc.musl-x86_64.so.1]
openssh-sftp-server-9.9_p1-r2[so:libc.musl-x86_64.so.1]
libcurl-8.11.1-r0[so:libc.musl-x86_64.so.1]
mpg123-libs-1.32.9-r0[so:libc.musl-x86_64.so.1]
mpc1-1.3.1-r1[so:libc.musl-x86_64.so.1]
libmenuw-6.5_p20241006-r3[so:libc.musl-x86_64.so.1]
mosh-server-1.4.0-r12[so:libc.musl-x86_64.so.1]
libmagic-5.46-r2[so:libc.musl-x86_64.so.1]
mpdecimal-4.0.0-r0[so:libc.musl-x86_64.so.1]
libxml2-utils-2.13.4-r3[so:libc.musl-x86_64.so.1]
musl-obstack-1.2.3-r2[so:libc.musl-x86_64.so.1]
abseil-cpp-cord-20240722.0-r0[so:libc.musl-x86_64.so.1]
gdbm-1.24-r0[so:libc.musl-x86_64.so.1]
ncurses-6.5_p20241006-r3[so:libc.musl-x86_64.so.1]
libpulse-17.0-r4[so:libc.musl-x86_64.so.1]
abseil-cpp-time-20240722.0-r0[so:libc.musl-x86_64.so.1]
abseil-cpp-crc-cord-state-20240722.0-r0[so:libc.musl-x86_64.so.1]
oniguruma-6.9.9-r0[so:libc.musl-x86_64.so.1]
mpfr4-4.2.1-r0[so:libc.musl-x86_64.so.1]
tmux-3.5a-r0[so:libc.musl-x86_64.so.1]
abseil-cpp-low-level-hash-20240722.0-r0[so:libc.musl-x86_64.so.1]
libcrypto3-3.3.2-r4[so:libc.musl-x86_64.so.1]
zlib-1.3.1-r2[so:libc.musl-x86_64.so.1]
libmount-2.40.2-r4[so:libc.musl-x86_64.so.1]
lame-libs-3.100-r5[so:libc.musl-x86_64.so.1]
abseil-cpp-cordz-functions-20240722.0-r0[so:libc.musl-x86_64.so.1]
zip-3.0-r13[so:libc.musl-x86_64.so.1]
abseil-cpp-examine-stack-20240722.0-r0[so:libc.musl-x86_64.so.1]
abseil-cpp-kernel-timeout-internal-20240722.0-r0[so:libc.musl-x86_64.so.1]
libgomp-14.2.0-r4[so:libc.musl-x86_64.so.1]
protobuf-c-1.5.0-r2[so:libc.musl-x86_64.so.1]
abseil-cpp-city-20240722.0-r0[so:libc.musl-x86_64.so.1]
nano-8.2-r0[so:libc.musl-x86_64.so.1]
abseil-cpp-exponential-biased-20240722.0-r0[so:libc.musl-x86_64.so.1]
abseil-cpp-log-internal-check-op-20240722.0-r0[so:libc.musl-x86_64.so.1]
libprotobuf-24.4-r4[so:libc.musl-x86_64.so.1]
libltdl-2.4.7-r3[so:libc.musl-x86_64.so.1]
abseil-cpp-str-format-internal-20240722.0-r0[so:libc.musl-x86_64.so.1]
abseil-cpp-strerror-20240722.0-r0[so:libc.musl-x86_64.so.1]
libintl-0.22.5-r0[so:libc.musl-x86_64.so.1]
htop-3.3.0-r0[so:libc.musl-x86_64.so.1]
abseil-cpp-strings-20240722.0-r0[so:libc.musl-x86_64.so.1]
readline-8.2.13-r0[so:libc.musl-x86_64.so.1]
libssh2-1.11.1-r0[so:libc.musl-x86_64.so.1]
libutempter-1.2.1-r9[so:libc.musl-x86_64.so.1]
make-4.4.1-r2[so:libc.musl-x86_64.so.1]
speexdsp-1.2.1-r2[so:libc.musl-x86_64.so.1]
lua5.4-libs-5.4.7-r0[so:libc.musl-x86_64.so.1]
libedit-20240808.3.1-r0[so:libc.musl-x86_64.so.1]
libxdmcp-1.1.5-r1[so:libc.musl-x86_64.so.1]
zstd-libs-1.5.6-r1[so:libc.musl-x86_64.so.1]
libgcc-14.2.0-r4[so:libc.musl-x86_64.so.1]
abseil-cpp-statusor-20240722.0-r0[so:libc.musl-x86_64.so.1]
libssl3-3.3.2-r4[so:libc.musl-x86_64.so.1]
libexpat-2.6.4-r0[so:libc.musl-x86_64.so.1]
orc-0.4.40-r1[so:libc.musl-x86_64.so.1]
mosquitto-libs-2.0.20-r0[so:libc.musl-x86_64.so.1]
abseil-cpp-raw-logging-internal-20240722.0-r0[so:libc.musl-x86_64.so.1]
libxxhash-0.8.2-r2[so:libc.musl-x86_64.so.1]
perl-io-tty-1.20-r1[so:libc.musl-x86_64.so.1]
libatomic-14.2.0-r4[so:libc.musl-x86_64.so.1]
openssh-client-default-9.9_p1-r2[so:libc.musl-x86_64.so.1]
libidn2-2.3.7-r0[so:libc.musl-x86_64.so.1]
skalibs-libs-2.14.3.0-r0[so:libc.musl-x86_64.so.1]
xz-libs-5.6.3-r0[so:libc.musl-x86_64.so.1]
dbus-libs-1.14.10-r4[so:libc.musl-x86_64.so.1]
abseil-cpp-strings-internal-20240722.0-r0[so:libc.musl-x86_64.so.1]
popt-1.19-r4[so:libc.musl-x86_64.so.1]
openssh-keygen-9.9_p1-r2[so:libc.musl-x86_64.so.1]
pcre2-10.43-r0[so:libc.musl-x86_64.so.1]
libxml2-2.13.4-r3[so:libc.musl-x86_64.so.1]
libverto-0.3.2-r2[so:libc.musl-x86_64.so.1]
c-ares-1.34.3-r0[so:libc.musl-x86_64.so.1]
scanelf-1.3.8-r1[so:libc.musl-x86_64.so.1]
abseil-cpp-synchronization-20240722.0-r0[so:libc.musl-x86_64.so.1]
gmp-6.3.0-r2[so:libc.musl-x86_64.so.1]
opus-1.5.2-r1[so:libc.musl-x86_64.so.1]
abseil-cpp-cord-internal-20240722.0-r0[so:libc.musl-x86_64.so.1]
abseil-cpp-cordz-info-20240722.0-r0[so:libc.musl-x86_64.so.1]
abseil-cpp-time-zone-20240722.0-r0[so:libc.musl-x86_64.so.1]
abseil-cpp-hash-20240722.0-r0[so:libc.musl-x86_64.so.1]
mosquitto-clients-2.0.20-r0[so:libc.musl-x86_64.so.1]
jq-1.7.1-r0[so:libc.musl-x86_64.so.1]
abseil-cpp-status-20240722.0-r0[so:libc.musl-x86_64.so.1]
libasyncns-0.8-r4[so:libc.musl-x86_64.so.1]
libncursesw-6.5_p20241006-r3[so:libc.musl-x86_64.so.1]
abseil-cpp-malloc-internal-20240722.0-r0[so:libc.musl-x86_64.so.1]
dialog-1.3.20240619-r0[so:libc.musl-x86_64.so.1]
libformw-6.5_p20241006-r3[so:libc.musl-x86_64.so.1]
libunistring-1.2-r0[so:libc.musl-x86_64.so.1]
openssl-3.3.2-r4[so:libc.musl-x86_64.so.1]
libproc2-4.0.4-r2[so:libc.musl-x86_64.so.1]
abseil-cpp-debugging-internal-20240722.0-r0[so:libc.musl-x86_64.so.1]
abseil-cpp-log-internal-message-20240722.0-r0[so:libc.musl-x86_64.so.1]
alsa-plugins-pulse-1.2.12-r0[so:libc.musl-x86_64.so.1]
dbus-daemon-launch-helper-1.14.10-r4[so:libc.musl-x86_64.so.1]
openssh-server-9.9_p1-r2[so:libc.musl-x86_64.so.1]
openssh-9.9_p1-r2[so:libc.musl-x86_64.so.1]
[21:01:19] FATAL: Failed installing package build-base
s6-rc: warning: unable to start service init-user: command exited 1
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
/run/s6/basedir/scripts/rc.init: fatal: stopping the container.
s6-rc: info: service init-mysql: stopping
s6-rc: info: service init-mosquitto: stopping
s6-rc: info: service init-docker: stopping
s6-rc: info: service init-ssh: stopping
s6-rc: info: service init-mysql successfully stopped
s6-rc: info: service init-mosquitto successfully stopped
s6-rc: info: service init-docker successfully stopped
s6-rc: info: service init-ssh successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service base-addon-log-level: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service base-addon-log-level successfully stopped
s6-rc: info: service base-addon-banner: stopping
s6-rc: info: service base-addon-banner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
Having an issue with SSH, on the logs keep seeing this (as the password prompt arises):
Connection from 1.2.3.4 port 64692 on 5.6.7.8 port 22 rdomain “”
Invalid user HAOS from 1.2.3.4 port 64692
Excess permission or bad ownership on file /var/log/btmp
and then inputting the correct password yields this:
Failed password for invalid user HAOS from 1.2.3.4 port 64740 ssh2
Excess permission or bad ownership on file /var/log/btmp
I have been using this add-on for many months, really helps to tinker with the configs, etc!
I am running the latest versions of all software. But recently (less than a month ago) I noticed I started having issues: the add-on does not start automatically after the server reboots. For security, I do not have it set to retry starting when it crashes.
When I try to start it manually after I log onto HA, it always starts without issues. Looking at the logs, it seems to be due to docker not having initialised some IP address when the add-on starts. Is there a simple way to put a workaround in, like to introduce a delay?
Here is an extract of the log:
Add-on: Advanced SSH & Web Terminal
A supercharged SSH & Web Terminal access to your Home Assistant instance
Add-on version: 20.0.2
You are running the latest version of this add-on.
System: Home Assistant OS 14.2 (amd64 / generic-x86-64)
Home Assistant Core: 2025.4.1
Home Assistant Supervisor: 2025.03.4
…
s6-rc: info: service init-ssh successfully started
s6-rc: info: service init-user: starting
[17:28:31] NOTICE: Session sharing has been disabled!
s6-rc: info: service init-user successfully started
s6-rc: info: service ttyd: starting
s6-rc: info: service sshd: starting
s6-rc: info: service ttyd successfully started
s6-rc: info: service sshd successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[17:28:32] INFO: Starting the SSH daemon…
[17:28:32] INFO: Starting the ttyd daemon… Bind to port 22222 on 0.0.0.0 failed: Address in use. Bind to port 22222 on :: failed: Address in use.
Cannot bind any address.
[17:28:32] INFO: Service SSH exited with code 255 (by signal 0)
s6-rc: info: service legacy-services: stopping
Hi, I’ve just set up HA on a new Pi5 and was looking for a way for the Pi5 to access my ssl certificates on my main Debian server so I can access HA from the internet using SSL. I thought setting up a file share would be a good way to do it so I’ve installed this SSH Add-on and added “sshfs” and “fuse3” to the packages list. Looking in the log SSH installs the packages ok, but when I try to create the share I get “fuse: failed to open /dev/fuse: Operation not permitted”.
Maybe there’s a better way to share the pems or I’m doing something daft? Thanks