Problem in configuration with duckdns

Configuration
1

Hi to all, I have installed home assistant supervisor with docker on my raspberry pi 4 with the last raspberry so 32 bit.
It’s work fine but I have a integration problem with duckdns.
I have installed, configured and run add-on, the log it’s all ok.
When I put this string
http:
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem
In the end of configuration.yaml, after reboot I can’t access to home assistant in local and in remote.
I try many times but the results is ever the same.
I don’t understand what I wrong.
Thanks to any reply

2

After completing the installation you now have to access home assistant with https:// not http://.

3

Also in local network?

4

Yes.

You will also have to add a certificate exception in your web browser if navigating to the ip address as the security certificate is for the domain, not the ip address.

5

Thank you so much! It works good.
Now doesn’t work android app, I have changed http in https but only work on browser

1 Like
6

Unfortunately I can’t help you there I use the iOS app.

If it works in a browser on your phone it should work in the app.

7

There is no way to “add an exception” in the Android app, afaik.
My workaround: Add a manual DNS entry in my local router pointing the FQDN to the local IP of HA.

8

Oh right. Yeah same for iOS. I just used the duckDNS address and relied on hairpinning in my router.

9

Or that, ofc.
I actually did the DNS workaround without knowing hairpinning was a thing, so I don’t actually know if my router supports it :wink:

10

Now I am watching to use remotely, I have home connection by sim

11

If your ISP uses CGNAT it will not work with DuckDNS.

12

Yes I know, now I watching to another solution, but for now only money solutions

13

I just created a guide to have a reverse proxy working with CGNAT