Hi,
I have set up duckdns on my HA, port forwarded 443, drunk several cups of strong coffee and I just get the Home Assistant loading page but not the goodies that lie beyond.
I am so close so there must be something simple that I have missed or not done properly.
Can anyone help me please?
Unless this is an extremely common configuration issue, you’re unlikely to get much help without more information about how you’ve configured your system. You should provide more information about how you’ve set up the DNS and what you’re trying to do with it.
This is a standard Duckdns set up, it works on the local network but not remotely. I am trying to connect to the device from outside the local network but the link stops at the part where it has connected and found the duckdns connection but refuses to load the HA interface.
I did an Ip lookup and it says this
Start: 2025-03-24T21:21:22+0500
HOST: DNSChecker.org Loss% Snt Last Avg Best Wrst StDev
1.|-- ??? 100.0 3 0.0 0.0 0.0 0.0 0.0
2.|-- 10.74.132.63 0.0% 3 0.6 0.7 0.4 1.2 0.4
3.|-- 138.197.248.246 66.7% 3 1.2 1.2 1.2 1.2 0.0
4.|-- 143.244.192.162 0.0% 3 0.3 0.4 0.3 0.6 0.2
5.|-- 143.244.225.214 0.0% 3 0.9 0.9 0.8 1.1 0.1
6.|-- 143.244.225.143 0.0% 3 0.7 0.7 0.7 0.7 0.0
7.|-- NYIIX-gig1-0.ukcore.bt.net (198.32.160.80) 0.0% 3 1.6 5.5 1.4 13.5 6.9
8.|-- t2c3-ae-12.uk-lon1.gia.bt.net (166.49.208.93) 0.0% 3 70.7 70.8 70.7 70.8 0.1
9.|-- 166-49-214-195.gia.bt.net (166.49.214.195) 0.0% 3 71.3 72.7 70.8 76.1 2.9
10.|-- core5-hu0-0-0-1.faraday.ukcore.bt.net (62.6.201.209) 0.0% 3 70.8 70.9 70.8 71.0 0.1
11.|-- 109.249.139.110 0.0% 3 70.6 70.7 70.6 70.9 0.2
12.|-- 213.121.52.209 0.0% 3 73.8 73.0 72.5 73.8 0.7
13.|-- 213.121.52.208 0.0% 3 74.0 77.1 74.0 83.1 5.3
14.|-- ??? 100.0 3 0.0 0.0 0.0 0.0 0.0
Does this help?
I don’t think it helps. “Ip lookup” is not a defined term and you didn’t even include the command you ran to get that output. And obviously, your problem is not with looking up DNS for remote hosts.
Apologies, it was a traceroute
Okay. That’s helpful, but your original problem statement is so vague that I can’t even begin to understand why you think a traceroute output is useful, whether or not it might be.
I’ll reiterate what I originally wrote, and if you would like help on this forum without hitting the lottery:
And pinging the ip address that the server is at all time out.
I have set duck dns up and added the token and domain address, then set up NGINX fully according to the documentation. and added the nginx_proxy_default_fix_ingress.conf file to the share folder. Set the duckdns address to the network section and forwarded port 443 to the server on the router.
When I go to the duckdns domain it reaches the interface but doesn’t come up with the login boxes for user name and password.
Are there any additional ports for forward?
Do I need to configure anything else to make this work?
the page I get as shown in the image above comes from
https://xxxxxxxx.duckdns.org/lovelace
So it is sending some information but not completing the deal…
Also, this is on a GSM router with EE, could they be blocking the port?
Check if they use cgnat
It looks like they do, can this help?
if they use cgnat, duckdns etc are useless, because you ave an ip-address that is shared with many others.