Hi everyone.
I’m trying to add DuckDNS to my home assistant, but I have a problem with the ports.
With my internet provider I can only forward ports 30000 to 30100.
I’m reading that opening ports 8123, 80 and 443 are needed to install DuckDNS.
Is there any other way to do this?
Thank you very much.
You are probably behind CGNAT, and so don’t get a proper external IP.
Can you ring them up and be asked to remove from their CGNAT scheme? Tell them you need an external IP address.
2 Likes
Assuming that you are not behind CGNAT as @callifo says (you might be, it’s worth checking) then this statement:
needs some clarification.
You do not need to expose any of those ports externally. You can choose pretty much any port number for your external port. Internally you need to forward to your HA server port 8123.
So it could look like this:
Router [public IP address] : 30005 ----> Hassio [internal IP address] : 8123
Port 8123 is sometimes chosen as the external (public) port as well for simplicity (forward 8123 external to 8123 internal). Similarly port 443 is chosen as this is the port assigned to https, however it is not mandatory that you use 443. Any port can use a secure connection. It’s just a convention. It does simlify things a bit as https is assumed to be on port 443 so if you don’t specify a port and you use https, that’s what port gets used.
Forwarding port 80 is not needed for the hassio addon. I think it might have been at one point for SSL certificate renewal but this is no longer the case.
3 Likes
I have spoken with the internet provider and they told me that I live in a building where all the neighbours share a static IP. That’s why I can only do stuff with ports 30000 to 30100. And I’m afraid it can not be changed.
Anyway, I don’t know where to tell hassio to use port 30000 (for example) instead of 8123.
I think that this is the problem to create the ssl certificate.
Thank you for your help!
Nowhere in hassio.
You change your router to accept connections coming in on port 30000 and forward them to your hassio on port 8123.
Perhaps nabu casa would be a better option for you?
$5 a month for seamless remote access (no router configuration) and easier integration with voice assistants. All the money goes to support home assistant development:
2 Likes
I was considering nabu casa, but this issue is something I would like to finish.
I can forward conections coming in port 30000 to port 8123, and it is working, but I duckdns is not generating a ssl certificate.
The problem looks like in every tutorial tells you to forward port 443 to 8123 (like this one: https://www.juanmtech.com/hassio-duckdns-add-on-set-up/), and I cannot do that.
I just updated home assistant and now Duckdns is working.
Thank you Tom for your help!