[Errno -5] No address associated with hostname
``` sounds like problems to get the ipv6, maybe he uses only the empty ipv4?
So changing this construct directly to the actual ipv6:
Failed to establish a new connection: [Errno -9] Address family for hostname not supported
does anyone have a idea, what exactly that means or what i could try next?
Many thanks...
Address family would be IPv4, IPv6, etc. and in this case its IPv6. My guess is that somewhere along the path from AWS to your HA, IPv6 is being dropped and not making its way to your HA Server.
I think one good test would be to try to connect to your HA using your mobile device over the internet with that same IPv6 address/port to see if your HA webserver is reachable via https.
Hi sorry, forget to write it: Yes, i can reach my homeasstant with two different handys even after shutting down their wlan and with the same duckdns url.
has anyone everytime seen a log entry about not trusted proxy for ipv6?
I remember i’ve had that problem sometimes with ipv4 and then i added for example 172.30.33.8 (out of the log entry) to trusted proxies. Until today i don’t know why (my internal network is 192.168.178.xx) but after that the external access over ipv4 worked. Now i wonder: I never have had some message of this kind for ipv6! Maybe HA doesn’t log ipv6 Problems properly?
On the other Hand: The booth Handys get access without problems, so why aws lambda doesent?
Not using duckdns, but the actually IPv6 address you posted in the Lambda log. It may be the case that that IPv6 address is not the correct one (but just a guess).
On the other hand, if you are using DuckDNS, did you try using the DuckDNS name for Lambda?
Hi,
the first Screenshot is from trying it with the duckdns url.
The second with the ipv6, that is saved in duckdns. The ipv6 and the durckdns url works with my handy (without wlan )
Ah I see … looking at it and it has a different error. It says there is no (IPv6) address for the duckdns name you used for Lambda. I would suggest you go to this Toolbox from a computer and enter that same DuckDNS name and see if it resolves to an IPv6 address.
As a check, are you sure the IPv6 address you are using is the one that will reach your HA Server? Could it be that that address is your router’s WAN IP address instead? Is your router doing IPv6-IPv6 NAT? those types of things.
(my internal network is 192.168.178.xx) but after that the external access over ipv4 worked. Now i wonder: I never have had some message of this kind for ipv6! Maybe HA doesn’t log ipv6 Problems properly?