eager mulch
Hello all,
Recently i've been working with deploying and configuring home assistant in TRUENAS Scale, and i've seen quite a few people with custom and local domain names for their home assistant installation, does anyone know if this is possible in TRUENAS Scale's docker format?
pliant solstice
Sure you can... that isn't really anything that needs to be TrueNAS specific (and I couldn't tell you if there's anything in TrueNAS to assist), but most set up a reverse proxy in front of Home Assistant and then you can configure that for your custom domain how you like. There's also nothing stopping you from just doing that w/ HA as-is, you can configure HA to serve an SSL certificate, but you'll need to handle the rotation of that on your own.
eager mulch
Sure you can... that isn't really anything that needs to be TrueNAS specific (an...
I think i'd go with the reverse proxy option, it's easier. Any idea of where and how I would do it?
pliant solstice
There's quite a few options out there. I use Nginx Proxy Manager, you could add that as a container, it has an easy to use web UI you can you to set things up. It takes care of getting an SSL certificate for you as well.
You'll need to make sure to add the IP of your proxy to you http: integration config (https://www.home-assistant.io/integrations/http/#reverse-proxies).
eager mulch
There's quite a few options out there. I use Nginx Proxy Manager, you could add...
thanks
@pliant solstice sorry for yet another question but where would I find this file?
pliant solstice
That's your /config/configuration.yaml
eager mulch
If `http:` isn't yet present in there, you can add it
also damn your fast
eager mulch
@pliant solstice update, manage to add mine, but I get a dns_probe_possible error everytime I try to access it:
pliant solstice
Well.... the only way to get that to work would be if you control the DNS server of your client and even then you'd never get a trusted cert issued to it.
Do you have a domain of your own to use
eager mulch
Well.... the only way to get that to work would be if you control the DNS server...
uhhh wdym?
pliant solstice
It is a bad idea to base services of yours on an unreserved domain space with a domain you don't own. There are some free subdomain services out there, DuckDNS is popular, where you can select a subdomain and get control over the DNS for it. Otherwise, I'd strongly recommend, if you want to have a domain yourself to register the domain you plan on using.
eager mulch
It is a bad idea to base services of yours on an unreserved domain space with a ...
ok i'll register it using duckdns
pliant solstice
Depending on if you want external access, you'll need to make sure you configure that correctly to follow your IP address (assuming you aren't behind something like CGNAT) and forward the port your proxy uses. If you want internal only access, you could just have it resolve to you local address and it'll just work within your network
eager mulch
Depending on if you want external access, you'll need to make sure you configure...
internal
and how do I get my access token? remember, i'm hosting duckdns on home assistant but nginx proxy on truenas scale if that matters
pliant solstice
Access token for what, DuckDNS?
eager mulch
yeah
pliant solstice
Should be at the top after you login
pliant solstice
Duck DNS
eager mulch
ohh wait I wasn't on the official site
yeah nvm I got it now
I uhh can't see the site anywhere
i've searched up and down
ah nvm
eager mulch
Duck DNS
k I added the site
what should I do now
this time I got a 500 internal server error
the new domain is under nfamily-homeassistant since the old one didn't work for duckdns
yeah nvm i'm getting the dns_probe_possible error again
i've also restarted and verified the integrity of the yaml config, everything works fine afaik
I am still getting the dns probe possible error however
eager mulch
@pliant solstice Any ideas?
pliant solstice
You've got some type of DNS issue, which isn't anything with Home Assistant or your hardware if you're using DuckDNS
You'll need to make sure the IP is configured correctly. If you're just using local, you can do that using the Web UI
eager mulch
You'll need to make sure the IP is configured correctly. If you're just using l...
I am planning on making the reverse proxy local, yes
eager mulch
You've got some type of DNS issue, which isn't anything with Home Assistant or y...
Uhh I don’t know, maybe I set something up wrong?
the config.yaml seems to be fine though
eager mulch
@pliant solstice Just to expand on what I said above, this isn’t meant to be an external link. All I need is a way to take a custom link and make it so that whoever types in that link on a device on the local network is forwarded to the ip and port my home assistant installation is on.
hope that clears things up a bit
pliant solstice
There's a chance that http://homeassistant.local:8123/ might already do that for you without this additional set up
But yes, you can still set DuckDNS to your internal address. I'd suggest just doing a ping against it after setting it up and validate you see the correct internal IP address of your proxy
eager mulch
There's a chance that http://homeassistant.local:8123/ might already do that for...
did that and got a 'dns probe possible' error
but I will try pinging it
pliant solstice
That kind of seems like you might have a DNS issue with the client machine.... usually you'll get more definitive errors like NXDOMAIN instead of that
eager mulch
That kind of seems like you might have a DNS issue with the client machine.... u...
so your telling me that my laptop (in which I typed the link into) has a dns issue? because I tried this on other devices and got the same exact thing
pliant solstice
How did the ping command result