I have tried single ip and single port in ipv6 firewall but still the same.
I use a range ip in firewall because I don’t have a static ip address.
Are you saying you don’t get a static IPv6 subnet from your ISP??? All ISP’s here in Australia are giving out a static /56 for IPv6 that is routable. My HA device has it’s own static IPv6 port and I only have that port opened for the HA port.
I’m using the network from mobile 4g LTE. I have a usb dongle to share the network to my Asus router via passthrough. So I don’t have a static IP.
I started using HA 6 days ago. Last night I began DuckDNS, NGINX and Alexa integration and am happy to report it’s done and working!
Good to hear, if you like the post it will raise its ranking as a solution
1 Like
Hi,
Have been trying to get this working all day long, but no success. If port testing with this returns a closed port, then it has to absolutely be a router issue, right?
Yes,
Does your modem say the port is forwarded ?
Without an open port, duckdns can not communicate, to issue you a cert or configure your external address to forward to.
How are you getting your external address (ie how do you know it) ?
Hi Mutt,
well the port forwarding is configured in my fritz box and I have followed your instructions but is not working, so the only problem that I can think of is that somehow the router is having problems… I am running HA in a virtual box by the way…
The external address can be seen in the duckdns web, at least I can see a ip and ipv6 address.
Both the duckdns and nginx add-ons are running fine… so it has to be the port forwarding.
cheers
I am struggling to get DuckDNS w/NGINX working. I have had this work in the past but I had to rebuild my HA instance and now I can’t seem to get it working again.
When I try to access my HA instance via https://xxxx.duckdns.org I get -
ERR_CONNECTION_TIMED_OUT
I have checked that my port on my router appears to be open via an OpenPortChecker.
My DuckDNS config is:
lets_encrypt:
accept_terms: true
certfile: fullchain.pem
keyfile: privkey.pem
token: xxxxxx
domains:
- xxxxx.duckdns.org
aliases: []
seconds: 300
I have commented out the HTTP section in my configuration file.
Any clue on how to debug this?
Just curious folks forwarding 443 on their router for this… you notice an increase in probing when that’s enabled? Every time I’ve tried to run a VPN through 443, it gets hammered hard! Just curious if anyone else has noticed this, and if using an off port helped?
Nope.
Not noticed anything on my end, the only two attempted entries, in the last 9 months, were me from another external computer.
Edit: Sorry, got a third notification today when I probed my own port for Carlos about t 4 posts above
Can you confirm that you do not have an http or https section in your config
That you don’t have a base internal or external address assigned.
That you followed the instructions above about the installation of duckdns and nginx (did you wait the required times and get the required confirmations.
Have you checked that duckdns has your port (apparently you may need to set it sometimes)
You say this worked before, was it on the same modem?
Are you sure you don’t have issues with hairpin nat
Have you tried turning WiFi off on your phone and accessing your duckdns that way
If you’ve done all that my sone, there’s nothing more you need.
I double checked by configuration:
- http/https section is commented out
- base_url is commented out
Yes. I waited the times and saw that they are both setup.
In DuckDNS - I don’t have a port number. How do you add this? I’m just using 443
It is a different modem, that might be the problem but the port does appear to be open.
I’m not sure about hairpin NAT… Not sure how to check that.
When I connected through my phone (outside of my home network) I got the Nginx screen which said that I have not setup anything yet in Nginx.
So research your modem/router
But the last item seems to say that you have two problems
In a FritzBox you must add your domain to a loop back list or it won’t work
1 Like
Thankyou David, I did not know that, but I was suspecting it had something to do with the fritz ox.
@Mutt,
I did all steps from you instruction but still I have only access to HA from local network and only from xxx.xxx.x.xx:8123
(after port fowarding my connection to router page is not secured, it its ok?)
In configuration.yaml I removed http section.
So I like said, I have access only from local network through ha ip and port 8123
So, like I said to Brian above : -
Specifically check that your modem allows hairpin nat
my router supports NAT loopback and it is enabled by default.