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

[hars]

Not too sure man! I’m pretty new to HA myself, just set it up a month ago and still learning.

Click on the about page by going to the dev tools down the bottom of the sidebar, very end icon: ( i )

Maybe something in there will help you troubleshoot?

[Varjo]

Does this require hass.io or can I use this on a normal home assistant install?

[hars]

All add-ons require hass.io:

Home Assistant vs. Home Assistant Core

[Klagio]

@hars

Make a note of the CloudFlare name server

Newb here.
I created a new name in freenom, created an account in cloudflare and added a site (the one created in freenom).
Now in CloudFlare its written “pending nameserver update” under my site

I don’t get which are the nameserver I have to put in freenom

[Florian]

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

[Klagio]

Found, thanks

[andrewlphilpott (Andrew Philpott)]

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.

[pjo (Paul Ogilvie)]

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?

[hars]

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.

[hars]

More info:

Connectivity Issues - duckdns

Hi Guys Suddenly started having issues today, my duckdns (inc letsencrypt) setup has been working fine since last September. All of a sudden today I’m unable to connect to my HA on the duckdns when on the internal network. Was advised it could be a nat loopback issue but nothing has changed on my modem or router, no firmware updates etc. For some reason now I can access it via internal IP address on my wired desktop PC, but if I try and connect on my iPhone, the only way I can get it to work …

[monaco]

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:

• mydomain.com shows my web page
• home.mydomain.com would show what I have now under myname.duckdns.org:8123
  Can you also help with that?

[apop]

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

[hars]

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.

[fernandex00 (Fernando Tapia S)]

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

[Argo]

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

[fenster89411]

@hars

3. Home Router

• Forward desired public facing port (TCP & UDP) to your Hassio local IP & port (default local port is 8123).

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?

[hars]

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

[GuitarSkater]

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?

[hars]

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.

[GuitarSkater]

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.