New system issues

Thanks all for the help you have provided. In an attempt to ‘make things easy’, I purchased a new Raspberry Pi 4, with a 64 GB MicroSD card, and am building a new Home Assistant system. Given that my current system only has four devices with automation, I figured this would be easy. However…

I would like to be able to access the file system directly, to edit files (or whatever), so I installed the add-on ‘Advanced SSH & Web Terminal’, which I have on my existing system and I added it to the Sidebar. Here’s the problem: When I click the Terminal icon, a window pops up saying ‘The add-on is not running. Do you want to start it now?’. When I click ‘Start add-on’, a message saying 502: Bad Gateway pops up. What on earth did I miss?

Don’t know if this matters at all: In Settings->System-> Network, I set the Hostname. However, when I look at the page in my router that shows DHCP clients, the new Raspberry Pi’s hostname is shown as ‘homeassistant’. These pages are essentially the same, new Home Assistant system and old, but the old one shows the name I gave it in the router. The one difference is that the new system has a section called ‘Network adapter’ and the Autoconfigure box is checked.

Hello Gerry Roston,

First I am going to assume you are running HAOS, which is what I run and the most common install, especially for a PI.

I can tell you that editing files on the OS level is not recommended. That add-on and all add-ons are running is a Docker container, and HA is running in another one. After you get the lay of the land, more things are possible, but definitely start out using the ‘File Editor’ add-on in the official store to edit files.
The exception would be if you are already familiar with VSCode / Code Server, there is an add-on for that in the Community add-ons. Being a Pi4 that is a heavy lift as it will probably eat 1/4 of your resources when running, but it is a better editor. If you stop it when not editing you should be OK.

Your specific problem, don’t know. I just know I use the SSH add-on once a year maybe in the last 6 years, so unless you like the weeds, I would stay out of them.

I have been programming Unix systems since the mid-1980s. I suspect that it is safe for me to look around.

1 Like

The add-on version you mention is ‘functionality reduced’ for newbies to prevent them from hurting themselves.

As an experienced user, you will find this frustrating and search and discover other options and the appropriate settings, and security certificates available to you…

Hint…

U just did some looking at the Supervisor Log (thanks for the hint IOT7712) and I see the following:

2025-11-09 22:54:35.620 INFO (MainThread) [supervisor.docker.addon] Starting Docker add-on ghcr.io/hassio-addons/ssh/aarch64 with version 22.0.0
2025-11-09 22:54:39.804 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.32.1:64547 ssl:default [Connect call failed ('172.30.32.1', 64547)]

No idea why it is looking for that IP or where that IP is defined.

There is also this error:
supervisor.exceptions.AddonsJobError: Rate limit exceeded, more than 10 calls in 0:30:00
but I suspect that is happens because of the previous one.

Go to Settings → Addons → Advanced SSH & Web Terminal and check that it is running and there are no errors in the log.

That IP is a local IP in the Docker virtual network.

Advanced SSH addon will only give you access to that specific addon.
There is a way to get access directly to the HA container instead on port 22222, instead of port 22.
You need to do some setup and I know there should be a couple of guides on the forum on how to do it, so search for them (I do not have a direct link). One place to start the search could be the HA cookbook in the Community Guide category.

Remember that HA is running with an overlayFS, so changing stuff is not easy and many areas of the filesystem will be completely overwritten when you update HA and/or HAOS.

For what it’s worth. I had both SSH and FileEditor add-ons and found the FileEditor way easier to modify files and browse the filesystem.

I was about to ask another question, but it now seems to be working. Not sure what I did, but thanks everyone for your help.

Waiting and rebooting a few times tends to get the freshly minted internals eventually sorted out by themselves is my guess.

Good luck!