DuckDNS Setup

Installation Home Assistant OS
51

I changed the base url to what you suggested above and restarted my home assistant. And both of those ports are forwarded just like you posted above.

52

If your using hassio and installed the duckdns addon, then your config.yaml must not contain the ports in the base url

base_url: https://mydomain.duckdns.org

The only port forwarding you will need is the 443 > 8123, once done visit the page https:\mydomain.duckdns.org without mentioning any port numbers and it should work.

1 Like
53

Thanks for trying to help. I wasnt able to get it work.and figured out my issue. I have an AT&T ZTE Homebase LTE modem. Although it has port forwarding settings in the device menu and they appear to function. They actually do not. I did a lot of searching and it seems as though AT&T blocks the port forwarding on their end.

54

Go to your Raspberry Pi, shut it down, pull out the SD card and stick it into an SD card reader on your pc, find the file named wpa_supplicant.conf on the SD card boot drive.

Are you using the pi over WiFi or Ethernet?
If WiFi then you need to set that file up for WiFi, if Ethernet, set it up for Ethernet, don’t set it up for WiFi and Ethernet. Google for how they file should be formatted for either WiFi or Ethernet.

Save, stick it back in your pi, go do what you’ve been doing to set up the duckdns add-on. Might need to uninstall the add-on then reinstall.

If all that fails and you’re using your pi over WiFi, then set up the wpa_supplicant.conf file for Ethernet and plug your pi in.

Doing that should fix it. I struggled with duckdns for 4 or 5 months, it was the wpa_supplicant.conf file, or it was because I was using the pi with WiFi

55

Thanks for the reply. I did try with WiFi and with Ethernet. I am back to using wifi now. I think I have narrowed down to the fact that my home internet is LTE and AT&T is blocking any external access to my network. Hate to say it but I gave up on it. Spent way too many hours trying to figure it out. I would love to have it working but gotta have a life outside of this.

56

I had similar issues and none of the above steps solved the problems I had. I found a complete set of steps in another forum which did work at once. This is a full reset of DUCKDNS and LETSEncrypt

Step 1. Uninstall DuckDNS from HassIO.
Step 2. Goto your routers port forwarding settings. Forward port 80 external to 80 internal at your pi’s IP. Do the same with 443 external to 443 internal at your pi’s IP.
Step 3. Re-Install DuckDNS with your key, accept terms and domain and start the add-on. Keep refreshing the logs down the page to ensure that DuckDNS has created the certs. This may take 10-15 mins it did for me.
Step 4. Once DuckDNS has created the certificates add these lines to your configuration.yaml
http: base_url: https://my-domain.duckdns.org ssl_certificate: /ssl/fullchain.pem ssl_key: /ssl/privkey.pem api_password: Secure password
Save.
Step 5. Go into your routers port forwarding settings delete the port forward 80 external to 80 internal and change 443 external to 8123 internal at your pi’s IP.
Step 6. Restart Home Assistant and navigate to https://my-domain.duckdns.org or whatever your domain is. Enter your password set in api_password: and log into Home Assistant.
This video is also a good guide- https://youtu.be/BIvQ8x_iTNE
Hope this helps! If this still didn’t work your ISP may block ports 80 and 443. You can usually check their website to see what ports the block or call them.

6 Likes
57

I’ll give this a try this weekend. I have DuckDNS add-on work as far as it creates the certificates and doesn’t give me any errors. Maybe I have my configuration yaml settings wrong. I’ve tried several settings that others have posted but not this one.

Thanks

58

This solved my recurrent issues. Thank you so much. I suspect that the issue for me had been not having the port 80 -> 80 and 443 -> 443 mappings setup and activated for the duckdns install and certificate generation.

I cannot thank you enough - this has been bugging me for months

59

I’m glad it was helpful … :sunglasses:

I tried so many instructions always with different results, but this seems to be a solid solution.

60

Oh alright I should have asked about your internet. At least there’s home assistant cloud now though, that would take care of it.

61

I have one problem…I can access remotely and from my PC, but not from my phone when I am connected to my LAN

62

So your router does not allow loopback… this is your router, not duckdns.

63

i think thhe same, the only problem is that i cant access throw my phone when i am connected to my LAN … if yu could help me please

64

either get a router that allows loopback or use the local ip address

1 Like
65

thanks i allready fix it, it was my phone, i change the DNS1 to my rp3 address

66

this is a nightmare…
I get the certificates DONE with port 80 to 80 , 443 to 443, 8123 to 8123 after this I change the yaml
like this:
base_url: “https://xxx.duckdns.org”
ssl_certificate: “/ssl/fullchain.pem”
ssl_key: “/ssl/privkey.pem”
api_password: xxx

save and change the ports like 80 to 8123, 443 to 8123 and 8123 to 8123
reset hassio and never can access to frontend, internal ip nothing duckdns url nothing

I haven`t api_password with the new authoritation after 77.2 but if I remove it still the same

could you help please

67

You can check the certificates are DONE but I can`t access via internal ip orduckdns

INFO: Using main config file /data/workdir/config

  • Generating account key…
  • Registering account key with ACME server…
  • Done!
    Tue Sep 25 20:20:46 CEST 2018: OK
    xxx.xxx.xxx.xx
    NOCHANGE

INFO: Using main config file /data/workdir/config

  • Creating chain cache directory /data/workdir/chains
    Processing xxxx.duckdns.org
  • Creating new directory /data/letsencrypt/xxxx.duckdns.org …
  • Signing domains…
  • Generating private key…
  • Generating signing request…
  • Requesting new certificate order from CA…
  • Received 1 authorizations URLs from the CA
  • Handling authorization for xxxxxx.duckdns.org
  • 1 pending challenge(s)
  • Deploying challenge tokens…
    OK + Responding to challenge for xxxxx.duckdns.org authorization…
  • Challenge is valid!
  • Cleaning challenge tokens…
    OK + Requesting certificate…
  • Checking certificate…
  • Done!
  • Creating fullchain.pem…
  • Done!
68

I’ve got the ports 8123, 443 and 80 forwarded to themselves, re-installed DuckDNS add-on but can’t get the certificates to be created. I only get “KO” with the timestamp. Nothing else.
I followed this guide but kept getting errors both in Config and DuckDNS startup. So, I tried the advice above to uninstall the add-on and change port forwarding until the certificates are created.
Any help is appreciated.
Thank you
BTW, BRUH video uses Putty but some guides do not. Which way is correct?

69

BTW, Found my port 80 and 443 is not visible from outside. 8123 is open. Checked with Comcast. Open on their end. Have all the ports correctly forwarded on the router page!!! Frustrating

70

Hi there and welcome to my world!

Having the same said issues. Have you set up the port forwarding on your router?

Have a look at this, good tutorial:

https://youtu.be/VUTPAoB27iQ

I’ve managed (I think) the port forwarding side of it but haven’t yet got a fixed IP address set up, struggling with that at the mo.

Please let me know if the video helps

Thanks