Home Assistant in Proxmox, local dns not working

Submitted ⁨⁨5⁩ ⁨days⁩ ago⁩ by ⁨WbrJr@lemmy.ml⁩ to ⁨selfhosted@lemmy.world⁩

Hi there, I just installed Proxmox on my home server and like the idea a lot, but there is a noticable learning curve. I used this wonderful website and the provided link for home assistant os.

Usually home assistant is available at homeassistant.local without any configuration, i think its called mdns? But on my setup, homeassistant.local does not work for me, on any device, but the ip does.

So i suspect some settings in the proxmox firewall stops the ha vm mdns service from creating an entry in my router (fritzbox). I could not find any useful information about this though, and AI gave me the usual not quite helpful advice.

I hope you have some tips what i can check. Thanks a lot!

source

Comments

Sort:hotnew top

ikidd@lemmy.world ⁨5⁩ ⁨days⁩ ago
So there’s 5 methods in there of installing HA, not to mention having to take apart the scripts to figure out what they do in order to help you troubleshoot this.

Not sure what you expect of asking a question like this with no useful info about what you actually have in front of you.

source
- WbrJr@lemmy.ml ⁨4⁩ ⁨days⁩ ago
  Sorry, i thought i was clear.
  
  I used the proxmox ve helper script from here: tteck.github.io/Proxmox/ to install ha os.
  
  The local domain does not get resolved how it should, i hoped someone here might have hosted ha in proxmox themselves or ran into a similar problem, or could give me a hint what to check
  
  source
  - ikidd@lemmy.world ⁨4⁩ ⁨days⁩ ago
    If you click the HA header, there’s 5 different scripts there, each install HAOS in a different way. As a container in an LXC, as a “baremetal” LXC, as a VM, as a Pimox VM, or as a Podman container.
    
    Image
    
    source
Xanza@lemm.ee ⁨4⁩ ⁨days⁩ ago

homeassistant.local

So then this isn’t what you set it to during the setup.

I could not find any useful information about this though

Because it’s not a thing.

Proxmox doesn’t automatically edit your router settings to add itself so you can connect, it simply allows all connections from local sources until you can set it up securely. If the mDNS isn’t working, just visit the IP address.

source
klangcola@reddthat.com ⁨4⁩ ⁨days⁩ ago
Hard to say without knowing which method you used to install HomeAssistant.

But I never found mdns .local addresses to be very reliable. They work 80-90% of the time, but the remaining 10-20% are a hassle.

Instead I’d recommend you install PiHole (in a docker container is easiest). PiHole is a DNS server intended for network-level ad-blocking. But it also have a handy feature of defining local DNS entries, so you can have HomeAssistant.myhome or HomeAssistant.whatever (.local should not be used with PiHole local DNS because .local is meant for mdns)

source
- WbrJr@lemmy.ml ⁨4⁩ ⁨days⁩ ago
  Thanks for the advice, i was thinking about it anyways :) i used the proxmox ve helper scripts: tteck.github.io/Proxmox/ to install it
  
  source
  - Oisteink@feddit.nl ⁨3⁩ ⁨days⁩ ago
    Multicast DNS uses multicasting (surprise!) so keep your devices on the same network and it just works. Docker is not very multicast friendly but lxc or a vm should have no issues.
    
    source
bigDottee@geekroom.tech ⁨4⁩ ⁨days⁩ ago
So you definitely still need a local DNS running. AdGuard Home, PiHole, Technitium, Hell your router probably has a local dns server you can enable and add some entries to it.

But once you setup a dns server, you’ll need to point all network clients to the dns server address so it can start resolving the web address to the ip in question.

source