No general local HA access via HTTP and IP after installation.

[keno198]

Hi, I hope I'm in the right place and someone can help me.

I've set up the tesla http proxy with DuckDNS and NGINX using this (https://github.com/alandtse/tesla/wiki/Proxy-setup-with-DuckDNS-and-NGinx) guide. Everything works fine and I was able to integrate the Tesla via the Tesla custom integration. Commands also work.

Before the installation I did not use DuckDNS and accessed HA from outside via nabu.casa. Locally I accessed HA via the IP or homassistant.local.

Now to my problem:

Since the installation, I can no longer access HA locally via http://192.168.**.***:8123/ at all. Using https instead of http, i.e. https://192.168.**.***:8123/, I get the following error message:

net::ERR_CERT_COMMON_NAME_INVALID
Subject: MYDOMAIN.duckdns.org

Issuer: E6

Expires on: 14.02.2025

Current date: 22.11.2024

PEM encoded chain:

I can ignore the warning and then access. However, this is not possible via the companion app, for example, and it is generally rather unpleasant.

My question:

Did I do something wrong or am I missing a step?

Translated with DeepL.com (free version)