Guide: How to set up DuckDNS, SSL, and Chrome Push Notifications

Configuration
43

I have the exact same issue… Have you found away around this yet?

44

your domain address that you are trying to verifiy is missing the “/local” as per the docs.

45

I have managed to get the HTML5 domain verification stuff done but…

I cant get the slider to switch on with my HassIO install where I have just now set up the HTML5 component. As far as I’m aware I have completed all the prerequisites, domain has been verified and HTML details listed under notify.yaml

can someone please help me?

46

anyone??? I dont understand why the push notifications slider wont turn on. This is the issue with all devices I have tried it with

47

hello, thanks for the tutorial, forgive in the installation of duckdns, when you access the raspberry by ssh in step number 7, to create the directory mkdir duckdns, is done from the user of the pi or from user home assistant?
regards, thankyou

49

I’m having the same problem as those above me with this step. Has anyone found out how to get around this problem?

50

For those still struggling, this tutorial here works

51

Hi,

Tried the above steps couldn’t connect from remote network after adding ssl certificate to configuration.yaml

Need help

52

Do you portforward your public port 443 to HA? Do you use reverse proxy? It is very easy to setup one and working well, you manage whole SSL on it and talks to HA via http

53

Hi Srubar,
Yes I did port forwarding with 443 to HA
It is working fine.

Thanks,
Jagan

54

I used this guide and it works. Didn’t setup the chrome bit.
Now I’ve got an email from let’s encrypt to update my certificate. Can this be done automatically?

55

Why are 80% of your steps not part of the DuckDNS install guide through hassio. Is it just hassio that makes it different? This is the second “guide” I’ve read that mentions creating certbot folders but that is not mentioned anywhere in the “official” guide. I’m getting really frustrated because so far NOTHING has worked like any of the guides show. It always seems there are multiple details left out. I haven’t even been able to get SSH to work yet and it took 3 days to get Samba Share working. I can’t move forward with SmartThings implementation until I have a dns and duckdns has not worked yet for the two days I’ve spent with it. Something is right because I can’t access locally with http anymore, only https but I get a “site not secure” warning on chrome. When I try to access online remotely I always get a time out error. Please point me to specific detailed instructions for making duckdns work.

56

A few quick questions:

  1. Are you running HassIO?
  2. If so, did you use the DuckDNS add-on?
  3. Have you opened the correct port in your router?

As for the certificate error in Chrome when accessing using https and the local IP, that is because you don’t have a certificate which is allocated to that address. With all things set up and working the certificate will be allocated to the DuckDNS address, not your local IP, so that error will still remain and is not an issue (there are ways to stop it, but that’s for later).

This guide is NOT for the HassIO add-on. I would suggest using that if you are running HassIO. Using that add-on you don’t need to worry about Lets-Encrypt as that functionality is built in.

57
  1. Yes, Im running hassio.
  2. Yes, I followed every set to the letter to install DuckDNS
  3. Yes, my router ports are forwarded: 443>8123, 8123>8123
    I can only connect locally using https now, I can ping my DuckDNS url but cannot connect to the url no matter what I try. It seems like a lot of people are having problems even though a lot don’t. I wish I was part of the latter group.
58

when run

./certbot-auto certonly --standalone --standalone-supported-challenges http-01 --email [email protected] -d YOURSUBDOMAIN.duckdns.org

receive

certbot: error: unrecognized arguments: --standalone-supported-challenges http-01

59

I found this discussion on DigitalOcean:

It seems like as of Certbot 0.33.0 which was released a couple of months ago and according to the official documentation, --standalone-supported-challenges had been deprecated for a long time and does the same thing as --preferred-challenges .

Certbot 0.33.0 Release - #2 by orangepizza - Client dev - Let's Encrypt Community Support

Source: