After some configuration changes, I get “502: Bad Gateway” displayed for the Hass.io panel. I am able to SSH in, but CLI is not working and I want to try restarting the Raspberry Pi next. I don’t have physical access to pull the plug at the moment.
Like I said, I can SSH in, but I get this trying to use the CLI:
core-ssh:~# hassio
/usr/bin/hassio: line 6: cannot create temp file for here-document: Read-only file system
I tried to use other commands, but here are the results:
core-ssh:~# docker
-ash: docker: not found
core-ssh:~# sudo shutdown -r now
-ash: sudo: not found
Yes, but in my case, the Cli is dead… without SSH access directly to the host I cannot reboot the device, docker or Hass.io without physically pulling the plug.
core-ssh:~# hassio host reboot
API error:
core-ssh:~# hassio
/usr/bin/hassio: line 6: cannot create temp file for here-document: Read-only file system
I have access to Home Assistant in the browser, but anything related specifically to Hass.io, like the panel etc. is dead.
I’m not on the same LAN - I use port forwarding - I do not have VPN setup.
So, is the SSH Add-on on port 22 by default and the host SSH is on port 22222? I’m wondering if I could just forward that port and that would work. Not sure about the authorized keys however.