Hi @arun2118, I am glad you got the DNS sorted - I’m curious: is Pi-Hole still disabled? I’m asking because a few others have also had DNS troubles, but I’m unsure exactly what they’re doing to fix the issue. I’m trying to figure out how to help others better with this in the future.
I’m using Pi-Hole, so I don’t think that’s the issue.
Can you say if you have manually configured the network setting in the TrueNAS UI?
For example, on my TrueNAS, I have configured Nameserver 1 with my Pi-Hole IP and IPv4 Default Gateway with my router’s IP.
I started pi hole back up, changed my router settings back, I’m restarting HA each change I do to see if one causes a issue. I found I was not able to update HA or any plugins, error came back something along the lines of “no connection to host”, the DNS for HA was set to pi-hole, and had to change to 8.8.8.8 to get the updates working.
This may be why initial install failed as some connection was trying to be made outside but pi-hole was interfering? I didn’t see anything getting blocked on the pi-hole web UI but I’m not also too familiar with reading the logs to say what happened. I’m going to restart truenas and my router today and see if it still works. My truenas network config is same as yours.
EDIT:
I didn’t notice before but the National Weather Service card is not showing any data, I did some digging and found this may be a DNS issue. I SSH in to HA ran “ha dns logs” and found a error:
[core-ssh ~]$ ha dns logs
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/corefile.sh
cont-init: info: /etc/cont-init.d/corefile.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun coredns (no readiness notification)
s6-rc: info: service legacy-services successfully started
[ERROR] plugin/mdns: could not locate primary interface due to: Could not resolv e ‘8.8.8.8.in-addr.arpa’, server or network returned error SERVFAIL
.:53
.:5553
CoreDNS-1.8.4
linux/amd64, go1.15.15, 053c4d5-dirty
after trying a few things like changing settings on the router(asus rt66u b1) I found if I use pi hole DNS running on the same computer, the error goes away but have some other errors which may be due to bad tokens due to restoring he back up on a new system? :
I’m was having a issue with the time in the logs of pi hole being off and suspecting this could also be a DNS issue but found the the bios time in the computer running Truenas/Pi hole needs to be set to GMT.
Everything is working fine now. Any one know how to back up the main Truenas drive in case it fails?
okay, so i’ve been searching through all the comments here to see if somewhere i can find my issue but since i can’t seem to find an answer i’m just going to ask.
I run HA in a vm on truenass scale cobia. Has worked great for years but now i’m trying to passthrough my conbee II. it does show show up in my HA machine but doesn’t connect to ZHA. my truenas keeps spamming:
Jan 21 21:36:14 truenas kernel: usb 1-8: usbfs: process 3152564 (CPU 0/KVM) did not claim interface 0 before use
i can’t seem to find anything regarding my issue where my device does show up in HA but doesn’t want to connect to the integration.
if anyone knows anything i could really use some help.
[supervisor.jobs] 'GitRepo.clone' blocked from execution, no supervisor internet connection
[supervisor.store] Can't add repository https://github.com/esphome/home-assistant-addon due to 'GitRepo.clone' blocked from execution, no supervisor internet connection
Hi @troy I’m new to HA and installed the VM within TrueNAS Scale with little issue given the instructions. However, I notice that I am dropping connection when getting to the HA web interface.
After the VM is loaded up, I maybe have a minute or so where I can get to the web interface via the url or the IP address and then it just dies. No more web interface access, but I can still ping to and from the VM with no issues. If I restart the VM, I can access the web interface again, but it dies shortly after. Rinse and repeat.
I have no other services running. Does anyone know what could be going on?
I am currently stuck at step 1 of this haha. I’ve rather green behind the ears in Linux and home server stuff (only been running my TrueNAS for less than a year now).
I keep getting a 404 Error with the wget command and even when I copy/paste the link into a url bar I get the 404. Here’s a screenshot:
Thanks for all of your work @troy ! I’ve tried to get this process to work multiple times. I’m successful in getting through all the steps. Once I have the VM created, I start it and go to “Display” and get this screen. I can’t log in via the URL either.
This usually happens if we use the incorrect path when writing the HAOS image to our zvol. Notice in the following command, that the path starts with /dev/zvol
qemu-img convert -O raw haos_ova-11.5.qcow2 /dev/zvol/tank/vm/haos
If you’re still having trouble, please share the exact command you used for this step.
So… any wizzards here that are trying to get this running in TrueNAS Scale JAILS? Official in 24.04 now. Should reduce the ressource overhead from VMs by a lot.
This should be possible via Supervised installer. But that looks like a lot of chances for mistakes…
I don’t think a HAOS VM has enough overhead to justify the hassle of running a supervised installation.
That being said, I think running docker-compose in one of these jails is a far better option for a container install versus using the SCALE apps for Home Assistant.
