Hass.io Add-On: letsdnsocloud - Custom Domain SSL & DDNS

Installation Home Assistant OS
14

you can find your assigned Cloudflare namesevrvers in the DNS tab of your dashboard below the DNS records.

1 Like
15

Found, thanks

16

Thank you so much for this! I’ve been trying to get things working with DuckDNS and Let’s Encrypt for weeks, but this is so much better because it a) actually works and b) gives me a use for one of my spare domain names.

1 Like
17

so interestingly enough this seems to work - YAY!
but… I keep getting this error in my log…

2019-01-22 18:56:54 ERROR (MainThread) [homeassistant.core] Error doing job: SSL handshake failed
Traceback (most recent call last):
  File "uvloop/handles/stream.pyx", line 609, in uvloop.loop.UVStream._on_eof
  File "uvloop/sslproto.pyx", line 171, in uvloop.loop._SSLPipe.feed_ssldata
  File "/usr/local/lib/python3.6/ssl.py", line 689, in do_handshake
    self._sslobj.do_handshake()
ssl.SSLError: [SSL: HTTP_REQUEST] http request (_ssl.c:841)
2019-01-22 18:56:54 ERROR (MainThread) [homeassistant.core] Error doing job: SSL error errno:1 reason: HTTP_REQUEST
Traceback (most recent call last):
  File "uvloop/sslproto.pyx", line 504, in uvloop.loop.SSLProtocol.data_received
  File "uvloop/sslproto.pyx", line 204, in uvloop.loop._SSLPipe.feed_ssldata
  File "uvloop/sslproto.pyx", line 171, in uvloop.loop._SSLPipe.feed_ssldata
  File "/usr/local/lib/python3.6/ssl.py", line 689, in do_handshake
    self._sslobj.do_handshake()
ssl.SSLError: [SSL: HTTP_REQUEST] http request (_ssl.c:841)

ummm??? Same issue? Any ideas?

18

Yeah, it seems to be a common issue across a few add-ons:

https://github.com/home-assistant/home-assistant/issues/15579#

Maybe it’s the duckdns code I reused to perform the DNS challenge for Let’s Encrypt.

Haven’t had the time to troubleshoot this, will have another look when I have a chance.

19

More info:

21

I have my own domain that I use for website on some 3rd party servers. Now I’d like to use subdomain for accessing my homeassistant (with dynamic IP). For example:

2 Likes
22

Following this. I’d love to be able to do the same.

23

You would have to duplicate all of your current DNS records over to Cloudflare, switch your DNS over and then run the add-on. It’ll create a new separate A record for your subdomain.

Moving forward you would need to use Cloudflare for all of your DNS. Whether or not that suits your use case is up for you to decide.

24

Hi do you maganed to get it working with that provider?

25

Hi, sorry, I did not finish that. Can not say for sure

26

Apologies in advance , but im bricking the whole setup with port forwarding.

So all I do is 443->443 with internal pi box IP
or do I need 8123->8123 also?

27

443 -> 8123

That will map your default ssl port to your local install. When outside of your local network you won’t need to specify a port on the domain name. ie: https://yourdomain.com

1 Like
28

I have everything set up, however when I go to the domain, it defaults to my router. I’ve tried everything port forwarding-wise, but nothing seems to make it point to hass. It only works if I specify the port in the domain url. Anything else hits the router regardless of http, https, random ports. Any ideas?

29

Tough to troubleshoot without knowing what router and how you’ve set it up.

If you’ve set the port forwarding to any port but 443 then you’ll have to specify the port.

30

I’m starting to think it could be something else. I had a bunch of error files get generated when I was running the addon, so I think something was conflicting.

I haven’t had issues with the router before, I liked the idea of using my own domain vs duckdns

I’ll mess around with it and let you know what I find.

31

As someone who has tried to set up Letsencrypt and DuckDNS previously I can only say THANK YOU.

I know what I’ll be doing later tonight! :smiley:
Now to try and think of a catch domain with high WAF…

1 Like
32

I cant see the addon… I added the repo but the addon didnt show up… I checked the system log and found this:

19-04-11 11:54:50 INFO (MainThread) [hassio.addons.git] Clone add-on https://github.com/PhrantiK/hassio-addons repository
19-04-11 11:54:54 WARNING (MainThread) [hassio.addons.data] Can’t read /data/addons/git/3983e8d8/letsdnsocloud/config.json: required key not provided @ data[‘arch’]. Got None

Please help.

33

I fixed the warning but I don’t think that has anything to do with the addon showing up.

It’s right down the bottom of the page when you add the repo.

34

It wasn’t there previously. All my other add-ons were visible. But whatever you just did seemed to work as I can see it now :slight_smile:

As per home assistant docs, if an add-on does not appear after the repo was added, check the system logs for an error and let the repo owner know… :slight_smile:

Thanks dude!