New Odroid M1S 8GB. Successfully flashed. Boots without error messages. Pings by name and address. But I get no web access. I have lots of Linux experience, but zero HA experience.
Is there a way to use the CLI to diagnose whats happening? I have a monitor and keyboard connected. I’ve poked around, but really don’t know what to look for. What process/service am I looking for?
It’s hard wired to my gateway, everyone’s on the same subnet.
What are you typing in the web browser to access HA?
http://homeassistant.local:8123/
http://192.168.1.30:8123/
I can ping with either ip or name just fine.
You don’t need the trailing slash.
Do you see an IPV4 address on the terminal on the server?
I have the correct address.
I’m interested in how to diagnose the problem from the HA CLI. For instance, what process actually presents the web service? How to I restart a process? Can I exit the HA CLI and work from the Linux CLI?
How do you know? That’s why you need a terminal on the Home Assistant server.
Sounds like you are running in a container or VM. What could you possibly do outside of the container. (I never use containers, so it’s a real curiosity question). Home Assistant is a Docker container, but HAOS manages the container settings for you.
A terminal connected to the Home Assistant server the environment is the operating system (HAOS). When you SSH into Home Assistant you are in a container.
Per the original post, I have monitor and keyboard. The screen shows the IP address. The screen is sitting at an “ha >” prompt. I’m assuming this is the CLI prompt. From another computer’s browser I can’t get to port 8123 on the HA server.
It’s not in a container. It should be HAOS. I don’t believe there is a sshd process running yet.
What steps can I take at the CLI to find out why there’s not a webpage presented?
Can you reach http://192.168.1.30:4357?
I’d first take a look at/follow the logs
ha core logs -vf
ha supervisor logs -vf
ha host logs -vf
Major Update!
From a linux server I used “wget 192.168.1.30:8123” to see what happens, and I got some http code!
My dumb phone web server found the HA web page.
I tried Safari on a newer Mac and it found the HA web page.
So the good news is: HA is working as expected.
The bad news is: Firefox and Chrome on the Mac can’t retrieve the web page and don’t give any clue that there is a problem.
On a Mac, you have to allow Local Network access in Privacy & Security settings for each browser.
Question: Are you expecting the actual HomeAssistant server device to present you with a GUI dashboard, rather than connect to the server via another device running a web browser?
You shouldn’t need to see the CLI for normal headless operation.
Is the Mac on the same LAN as the HomeAssistant server?
List the IP address of your router, MAC computer, phone, and HomeAssistant server.
Have you considered the benefits of Static IP Address allocation via the DHCP section on your router configuration?
Sorry, I missed that. If you got the IP from an IP scanner or from the router, that only means HAOS is running. When you see it on the server terminal then Supervisor is running.
HAOS on bare metal - 
. That eliminates a whole host of complications.
SSH is an add-on app that you install from the website. Also, must-have add-ons apps are Samba Share and Samba Backup.
Well, there’s your problem; use a real computer. I’ve never touched a Mac, but it wouldn’t surprise me if the firewall in the Mac is blocking port 8123. Try to open the Observer page at http://homeassistant.local:4357.
Thank you for the reply, but read the Major Update post above.
MacOS has a security system that prevents viewing websites on the local network. I changed that setting and all is well.
I’ve set a hard IP address in HAOS.