#First time installing HomeAssistant OS, can't access HA server

1 messages ยท Page 1 of 1 (latest)

fallow epoch
#

I also checked nslookup for homeassistant.local - it doesn't resolve

thorny gazelle
#

Well, that's because .local uses mDNS not DNS

#

But, if you can't reach the IP, the hostname won't work

#

Make sure that you configured the VM with bridged networking

fallow epoch
#

I used VirtIO as the network adapter, so I'm wondering if that's the issue. Rebooting the host now after specifying to use the hardware adapter.

#

Alright, same issue whether I specify VirtIO or the hardware NIC. The router does assign homeassistant an IP address at the MAC address listed - 192.168.0.157 - also does not resolve.

thorny gazelle
#

Try port 4357

fallow epoch
#

Will do. Rebooted the VM after assigning it a new MAC address that I set as a reserved IP in the DHCP table.

#

Well, 4357 loads

thorny gazelle
#

Progress!

fallow epoch
#

But not 8123.

#

Agreed, progress

#

Thanks for helping me with this. I spent several hours last night trying to get the install to work on my NAS

thorny gazelle
#

Now at least you know the host is accessible, if it wasn't before then it probably never finished installing

fallow epoch
#

That was my thought too. I ran into all kinds of errors trying the docker install and then the python pip package install, so I gave up on those methods in favor of just getting the raw OS to install.

thorny gazelle
#

I suspect you've had a load of networking issues then, Docker particularly is really hard to get wrong if the networking is good

fallow epoch
#

Yeah, that was the issue with Docker that caused me to say screw it.

#

So, 8123 doesn't load but 4357 does. I cleared out homeassistant.local from my hosts file on my local machine (Linux)

thorny gazelle
#

The VM has far more moving parts, with broken networking it was never going to be an easier option ablobjoy

#

The console should tell you more about what's going on, hopefully

fallow epoch
#

The TrueNAS console or the CLi window with HA?

thorny gazelle
#

The VM's console

fallow epoch
#

Currently it's got the supervisor started and has an HA prompt. It shows that it should be accessible via port 8123.

thorny gazelle
#

core logs should tell you about HA itself

fallow epoch
#

Well that explains it. It failed on a json file on line 39.

#

/config/.storage/core.config_entries line 39 it looks like. Is this a case where I need to get into the VM from the CLI on the TrueNAS to edit that config file or is there a simpler way?

thorny gazelle
#

Did you restore a backup?

fallow epoch
#

No. This was right out of the gate as it tried to start.

thorny gazelle
#

Generally that's a folder you don't touch, though maybe you've managed to corrupt your install with all the restarts

fallow epoch
#

I did create a backup immediately as per the documentation on the site you linked.

#

I figured.

thorny gazelle
#

I'd suggest you nuke everything in that folder and reboot

fallow epoch
#

I'm always THAT guy that gets the weird stuff.

slow whale
#

hello - first time installing home assistant - managed to use Container Station on my QNAP NAS and got all set up, I can see the main page on my IP with port 8123 - but cant figure out how to get "settings" added on? Any help muchly appreciated - thanks ๐Ÿ™‚

thorny gazelle
slow whale
#

haha cheers ๐Ÿ˜„

fallow epoch
#

Alright, need a bit of help since the normal Linux CLI tools don't work inside the VM and it appears that what the NAS does is load the entire image as a single file, boots to it, and lets the VM sort out the rest.

thorny gazelle
#

You can type login there to get a minimal shell

fallow epoch
#

Ahh, so I made a mistake on the directory - it's /usr/src/homeassistant/homeassistant/util/json.py

#

Can't remove file - no such file exists

#

Wow, yeah really botched install. No wonder it can't find it - there's no homeassistant directory inside /usr/src

#

Nuke the VM from orbit and try again?

thorny gazelle
#

Well, you do realise that HA runs inside a container?

#

So, you're not going to find the file mentioned there, and you wouldn't be touching it anyway

fallow epoch
#

Right. I'm so bad with containers (clearly)

#

I'm trying to do the whole thing from scratch again without a bunch of reboots to potentially corrupt the file.

thorny gazelle
#

Any error that mentions a file in HA's source is just telling you what threw the error, not what to touch

fallow epoch
#

That makes sense with containers.

thorny gazelle
#

Even without the containers, you don't go fiddling with the source/installed software

fallow epoch
#

Firing up the VM again now that I've nuked it from orbit, recreated it using the network adapter and the saved MAC address, and I think I see where I screwed it up. It ended up hanging on Waiting for root device PARTUUID=gobbledygook

#

I gave it 30 minutes last time.

#

After that I rebooted the VM, which resulted in the start of this thread.

#

WOW that was a simple fix. I had used VirtIO for the disk - recreating the image using ACHI causes it to boot