Moved from DuckDNS to Nabu Casa, can't seem to be able to use local IP

Configuration
1

Hi everyone,

I recently decided to switch from DuckDNS to Nabu Casa, but I’m still having trouble with local access. This has always been an issue for me (even before the switch) since my SSL certificates were never valid, and I constantly had to approve the “unsafe” IP in my browser and had to use the external URL for internal access too.

I was hoping that using Nabu Casa would simplify things and resolve these problems, as it removes a lot of third-party dependencies. However, I’m still facing the same issue: I have to use the external URL for all my mobile apps because they won’t accept the local IP.

I followed the advise from this older thread and removed the ssl_certificate: and ssl_key: from http: in the config.yaml as well as the other steps but it seems like the only thing that I can do is putting in the nabu casa url in the local network field, anything else fails, whether it’s my local IP with HTTP or without HTTPS I get the error:

Invalid local network URL - You have configured an HTTPS certificate in Home Assistant. This means that your internal URL needs to be set to a domain covered by the certificate.

Screenshot 2025-10-22 at 13.44.20
Screenshot 2025-10-22 at 13.44.20640×671 36.6 KB

If I press on automatic for the local url field, even then there’s an error:

Screenshot 2025-10-22 at 13.44.24
Screenshot 2025-10-22 at 13.44.24640×671 36.6 KB

I don’t know what else to do, from what I read, I suspect that there might be something stuck regarding the old SSL certificates, but I’d love to hear some hints on how to sort this out.

2

Normally, users that have Nabu Casa do not have SSL configured internally, as you do. Nabu Casa has their own certificates to provide SSL to the outside.

You way want to consider how relevant it is to you to have SSL on the LAN side. It can be done, the warning signs in the dialogs pretty much explain what it is you need to do to get it right. But the question is what are you trying to guard against.

1 Like
3

What do you have under the ‘http:’ in your configuration.yaml

4

I just figured it out, it seems that for some reason, when editing the config.yaml via Studio Code Server, something didn’t fully save my changes, or rather, an older version restored after restarting. I kept opening Studio Code and didn’t see it there but it was visible when I checked it via terminal.

I did a hard edit via terminal and it immediately worked.