Issue Setting Up DuckDNS on Home Assistant with Raspberry Pi 4 and Fritzbox

Installation
1

Description:

Hello everyone,

I’m having trouble setting up DuckDNS on my Home Assistant installation. Here are my setup details:

  • Raspberry Pi 4
  • 32GB SD card imaged using Raspberry Pi Imager
  • Fritzbox router

Steps I Followed:

  1. Installed Home Assistant and started the setup.
  2. Installed the DuckDNS Add-on and configured it correctly.
  3. Set my WiFi IPv4 to static.
  4. Configured port forwarding on my Fritzbox for port 8123.
  5. Added the configuration snippet from the DuckDNS documentation into my configuration.yaml.
  6. Set my DuckDNS domain as the external address in Home Assistant.
  7. Restarted Home Assistant.

Issue:
After restarting, I can no longer connect to Home Assistant—neither via the local IP nor via the DuckDNS domain.

Has anyone experienced a similar issue? Any advice on what might be going wrong?

Thanks in advance for your help!

2

Not much to go after in that description.
There are like 100 guides to do such setup and every little one have there special thing.

It looks like you are setting up an unencrypted port and opening up to the internet and maybe it is lucky that you did not succeeded.
Portforwarding is really something you should think a few extra times over before doing it and it should definitely be encrypted then.
If at all possible, then go with a VPN setup instead.

3

I wanted to switch to port 443 after port 8123 is working but I never got that port to work

4

Port 443 is for HTTPS, which require a certificate and there is nothing in your description that mention a certificate setup.

Also remember that HA can only run one type of connection setup itself, which means it is either HTTP or HTTPS.
If you want both, then HA have to run HTTP and you would then have to run a proxy to supply a HTTPS to HTTP bridge, like NGinX.

1 Like
5

Good.

…for the record -please don’t do that. It literally takes microseconds to be pwnd. Chances are nothing happens - especially since this isn’t a windows box. But within seconds of opening the port you can expect port scans to start…

You can’t put an unprotected box on the Internet and expect it to be safe these days. Plan security from the start and if you don’t understand it don’t do it.

6

Duckdns creates a certificate or not? And my plan was using https only. But its simply not working.

7

DuckDNS is a dynDNS service.
You can add a certificate to your setup, but that will be from somewhere else, like Let’s Encrypt.

8

Duckdns only provides DNS resolution under thier url. A port is a port 443 is just a well known port.

Then you need something like Let’s Encrypt cert client to pull your certs. (what wally said.)

9

The Duck Dns Add On creates certs using Lets Encrypt. I know how to set up the https connection. But I dont know where my mistake is. I mean my homeassistant wont show the login page after restart

10

What error do you get?
Does the console connected directly to the HA server say anything?
What guide did you use?
Did you install NGinX?