Should my Home Assistant connection always show as insecure [DuckDNS / LetsEncrypt]?

Configuration Frontend
1

Hi,

Years ago, when I first configured my Home Assistant, I configured the DuckDNS addon (with Lets Encrypt), created a domain with DuckDNS etc, and it is / was working. But, it always show as Not Secure.

This is getting more and more of a problem as browsers keep cracking down on this, I always get a perpetual error when trying to load and it’s fiddly on a mobile browser to get to the “Continue to this site” message.

Is it meant to show as Not Secure? Is there something I can do that’ll make it “Secure”?

My configuration in the DuckDNS addon is:

domains:
  - xyz.duckdns.org
token: xxxxxxxxxxxxx
aliases: []
lets_encrypt:
  accept_terms: true
  algo: secp384r1
  certfile: fullchain.pem
  keyfile: privkey.pem
seconds: 300

And I have the entry in the config.yaml file to load the pem files.

I don’t honestly know what I’m missing or may have done wrong, any help would be wonderful.

2

Add DNSMasq to your system and create a local A record, then access HA via the duckdns FQDN from inside your network.

Howto:

The video is somewhat dated, but the technical info is still accurate, even if the UI has changed a bit.

3

Hey,
Thanks, I’ll check this video out.

Will this conflict with me using AdGuard on my HA instance? It’s effectively acting as a DNS server to block ads?

4

If you are able to create A records in ad guard, then just do it there instead of using DNSMasq. If you’re not, then just configure adguard as the upstream dns server for DNSMasq and all requests will run through that.