Please try selecting “Native IP-Anbindung verwenden”.
do you mean Native IPv4-Anbindung verwenden?
Yes try this
unfortunately on IPv4 I don’t have internet connection anymore, if I take off “IPv4 über DS-Lite” it connects only with IPv6 and not with IPv4.
In the log I found this entry,
so I guess the customer service on the phone today had no idea what they were telling me and that is that my connection is on DL-Lite.
So all I´m left with is the alternative of VNP.
Or you could try using Ipv6 instead. I have not done this but here is a thread about it https://community.home-assistant.io/t/external-access-to-ha-via-ipv6/689716
1 Like
Hi Patrick,
May I kindly ask you to share what changes did you implement to solve Alexa issue?
I have the same issue but reading the commented post it not clear to me how to solve it.
Thanks a lot in advance
I have the same problem but I also cannot understand what to change from the linked thread. @C09038 and @patrickfl could you please help?
Hello Chris,
it looks like, you missed to create the portforwarding for IPv6. My provider is also 1&1 and I have a DSLite connection, means no native IPv4.
If you create your rule, then select “Internet access for IPv4 and IPv6”
You should get two entries.
One for IPv4 and the second for IPv6. Both ports have to be open, that letsencryp can create a new certificate.
1 Like
Why do you exclude DS-Lite?
I didn’t figure out how it works, yet. But it should be possible, nor?
In my current setup I use “MyFritz Device sharing” on port 8123 of my HA instance. With that I’m able to connect via IPv6 from remote to my HA. Forsure, for that all devices need IPv6. In most cases that’s not an issue.
But with that configuration, I’m not able to connect via the compaion app to my IPv4 address of HA, due to wrong certificates. Even in my local network.
When I tried to setup everything with Nginx, I was able to connect via IPv4 locally, but the remote access via IPv6 did not work anymore
IPv4 does not work with DS-Lite because the provider does not give you a public IPv4 address you can connect to from the internet. You can “IPv4 out” from your home network but you cannot “IPv4 in”. IPv6 should work in general but is seems that Nginx does not support it. At least I could not make it work with Nginx.
2 Likes
Sorry I am a bit late. I don’t remember exactly what I did but I think I just followed the instructions of the first contribution on this thread https://community.home-assistant.io/t/alexa-no-cloud-external-port-8123-with-events/226128
Well, I made a big mistake and changed my internet provider to Vodafone. Now I’m affected by the DS-Lite issue. Has anybody had any luck in solving the problem with DS-Lite?
Hello,
please can you help me, since i setup this configuration, i have all days following Error in my logs: “Login attempt or request with invalid authentication” mentioning my LAN IP Adress of my mobile phone. Seams using the internet adress is working fine but using local network it creates this issue and after some time, HA is banning my mobile phone. Any idea how to fix this? Thanks.
Did you configure your internal connection URL in the mobile app? Did you configure your internal WLAN SSID in the mobile app?
Did you configure your internal address in the HA network configuration?
Hello, thanks for the feedback. Yes i configured this in the App as well the HA Network configuration. As it occurs only in case the mobile is in the local network, the app does the switch correctly and access HA using the local connection instead of the internet connection. But using the local connection trigger the issue.
And you are using http (not https) for internal access? Can you try with a PC?
Yes, internally i’m using http. Chrome Browser mentioning its not save because the connection is not secure not using https, but it is working.
Good morning,
a few weeks ago I followed this post, set everything up, and it all worked perfectly on the first try.
I also configured the blueprint (still to be tested) and the Certificate Expiry to monitor the certificate expiration — that was working too.
However, for the past few days I haven’t been seeing the certificate expiration anymore, and if I try to reconfigure it, I can’t enter my domain — it times out. I’m entering “xxxxxxx.myfritz.net” with port 8123, which should be correct since it was working before.
What’s strange is that if I try to access “xxxxxxx.myfritz.net:8123” from the same network as the Fritz!Box, it doesn’t work — but it does work from another network.
The same happens with the address used to access the router settings.
I suspect something might have changed with the latest beta update of the Fritz!Box 7590.
Is there anything I can check?
I’m having an issue where Home Assistant becomes inaccessible after an uncertain period – both externally and locally. I followed your guide to expose HA externally using FritzBox’s MyFritz DDNS.
After some time, I can no longer access HA externally and just get an “Unable to connect” browser error.
When trying to connect locally via homeassistant.local:8123, I get the same message. However, if I try accessing via the server’s IP:8123, I only see the HA logo and nothing else loads.
When attempting SSH access, I get the following error:
My setup:
- Home Assistant OS (HAOS)
- Raspberry Pi 4 (8GB RAM)
- Connected via an LTE router (meaning internet connectivity isn’t 100% stable)
Has anyone experienced similar issues? Any troubleshooting suggestions would be greatly appreciated!
Good morning,
As an alternative to using the blueprint that checks whether the certificate has expired or not, couldn’t I create an automation that runs Let’s Encrypt at a specific time every day and then restarts Nginx after 30 seconds?
From the Let’s Encrypt logs, it seems that if the certificates haven’t expired, they are not recreated, so running the plugin once a day shouldn’t be a problem. Restarting Nginx daily shouldn’t cause any issues either.