Accessing Homeassistant externally over ipv6

Installation Home Assistant OS
1

Hi,

I’d like to access Home Assistent from my phone when I’m not at home. My setup

  • Fritzbox 7490, DynDNS configured for DuckDNS
  • My IPSV only provides an external IPv6 address (Netcologne)
  • Port forwarding to homeassistant host configured as 8123->8123 for IPv4 and IPv6
  • HassIO runs on a Raspberry

The port forwarding page of my Fritzbox shows me an IPv6 IP which I can use externally (unsure how long it will be static). However, my communication with this IP is not encrypted. So I wanted to encrypt use DuckDNS with LetsEncrypt.

I tried the DuckDNS plugin and according to the log everything went fine. However, I’m unable to access Home Assistant via DuckDNS hostname. Any suggestions?

Thanks for your support,
Boris

2

Hi Boris, does it work without using the DuckDNS domain?
Does DuckDNS know the actual IPv6 address?
Do you also provide your IPv4 to duckDNS?

3

Hi Dominik,

DuckDNS knows the ip4 and ip6 address, but the ip4 address does not seem to be usable (that at least what MyFritz tells me). If I use the ip6 address provided on the device share page of my FritzBox, I can access HomeAssistant (without encryption).

So I’m little bit stuck right now.

Best regards,
Boris

4

Hi Boris,

I’d try to only provide the IPv6 to DuckDNS and leave the IPv4 empty.
In that case the DuckDNS domain should always resolve to this IPv6.

Hope that helps…

5

Hi
Did you find a solution yet?

6

Hi,

Unfortunately not. I used a trial month from Nabu Casa, which worked flawlessly. Dominik’s approach with leaving the ip4 address empty, didn’t work.

So I really have no idea at the moment besides to subscribe to Nabu Casa.

Best regards,
Boris

7

Hi,

did someone find a solution yet, because I heard that Homeassistant Cloud is changing to a yearly plan and is not accepting PayPal anymore. So after the switch im not able to pay for it anymore. And so I wanted to look for an alternative.

Best regards,
Johannes

8

It seems the Home Assistant app is not able to deal with an FQDN which only return a AAAA DNS record (IPv6) but no A DNS record (IPv4). I have the same setup and it fails too.

What’s the best way to open an issue for this?