Hi, I'm using DuckDNS to connect to my HA from an external network.
Since a couple of days ago, I can only connect successfully from my internal network and I saw people having the same issue posting on this Discord server in the last few days.
Does anybody know if that's a known issue and if there is any update regarding it?
Thank you in advance!
#Is there an issue with DuckDNS?
73 messages ยท Page 1 of 1 (latest)
Not that I've seen - do you have some way of connecting a laptop externally to troubleshoot?
So your seeing logs on HA of the attempt? That must mean that duckdns is working correctly since the attempt is getting to your HA server
I didn't change anything in the past days and it always worked fine.
I've also tried restarting the add-ons or even reinstalling them, but seeing that two people were having the same issue here, I thought it could have been a common issue
(the same issue with the exact same timing)
All duckdns does is take the name "yourdomain.duckdns.org" and translate that to an IP address - if you see requests to HA from your phone then you know that process is working correctly and something else must be at fault somewhere in the chain
(assuming the logs are correct)
If you can connect a laptop to your 4g and test then it might give more indication as to what the problem is
I can try and see if I get something different
You can also do nslookup yourdomain.duckdns.org in a command prompt and verifying the returned IP is correct
By the way, I was following your guide to set the external connection through DuckDNS to check if everything was ok and when it comes to see if port 8123 is open through CanYouSeeMe.org it doesn't work
Feel free to post screenshots of the port forward and can double check them
Sure, but it's the same setting I was using since more than an year ago, so it should be correct
Is the internal IP definitely correct? Btw no need to hide internal IPs
Yes, I double checked that
Congratulations @vale helm! You just advanced to level 2!
Cool. Do you need both ports forwarded?
If I recall correctly port 443 was for using the Alexa integration and for another integration I'm using
If I run this command when connected to the internal network, it returns the internal ip of my HA instance.
If I connect to a VPN service to emulate a connection coming from outside, on the other hand, I get a non-authoritative answer returning my PC's ip (not sure if this is what it is supposed to do)
Send a screenshot of the response (no need to hide information) to @gilded blaze in a DM and will check jt
I just hid my public ip and my domain's name and left the rest as it is
And sent the DM
Hard to tell with hidden information but will check
Looks good to me from what I can tell
I'll check online again and see if I find someone having the same issues also there.
Thank you very much for the support and for your videos!
What happens if you try and visit the URL on the PC with VPN?
If you mean on my PC, I can only see the loading screen with HA logo for a while, then "Unable to connect to Home Assistant. Retrying in x seconds" pops out and it stays in this state forever.
And in the logs I get this
I guess it might not work on a VPN actually because of the way it would connect...you'll probably get similar results on 4g but maybe worth trying
I get the same if I connect using 4g both on my PC and using the Android app.
I've always connected to my HA using the VPN from my PC and it suddenly stopped working a few days ago.
Ah OK
Also using the Android app with 4g never gave me any issue.
Is there any kind of certificate or similar that could be expired?
You can view the cert from the browser when connected locally
Because, as mentioned before, I didn't change anything
Click on the padlock in the browser and view cert, you can see the expiry date
You'd be surprised how often I hear that ๐
Ok, the certificate is valid and expires in February
Makes sense otherwise you would get a cert error when viewing locally
The only strange thing I remember is that my domain was detected by Chrome as a potentially harmful site, when trying to connect to it something like two weeks ago, but I just confirmed that I was sure to proceed and never get that warning ever after.
At this point, given that I saw two other guys complaining about the same issue with the exact same timing here on this server, I just hope that it's a common issue which is going to be fixed soon (who knows caused by what ๐ )
I don't see how it can be a duckdns issue given the IP address returned is correct you said and also you are seeing logs in Home Assistant relating to the connection..if your connection is hitting your Home Assistant server and it is showing in the logs as you mention, how could that be duckdns? ๐ hopefully you see what I mean
This page also indicates no issue but there was on the 27th which would tie up with when others had issues: https://downforeveryoneorjustme.com/duck-dns
Can I ask you what do you think about this?
Can it suggest that it should be something router-related?
Does port 443 work?
It doesn't
Congratulations @vale helm! You just advanced to level 3!
Hmm, try disable the 443 one for now
The only thing that might make sense is your ISP moved you to a CGNat?
I have no idea
If you go to your routers web page, what does it say the public IP is?
Disabling 443 didn't change anything btw
Don't post it but just take a note once you find it
Found it
They are different
So the port forwarding isn't working anymore, right?
Yeah that's right
I'd suggest moving to the cloudflare method
Or your going to have to phone up your ISP and get them to move it back
Guess I'll follow your guide then ๐
Thank you very much for your support!
No problems!
Completely off-topic, but will you announce when the Everything Presence One Kit will be back in stock on #product-announcements ?
Yes you can join the role to get a notification about it