I set up an external URL for my HA instance via Duck DNS & port forwarding on my router. Is this gonna impact functionality in any way?

I just noticed I couldn’t access HA over the internal URL anymore in the companion app and “Add Integration” buttons also didn’t work.

I fixed these issues by entering the Duck DNS external URL where the internal URL is supposed to be in the companion app and entering the new https internal URL in the my.home-assistant.io page.

Despite those problems being solved, I became a little worried, considering that these were issues the guy who made the tutorial I followed didn’t mention.

What are your experiences with this? Could there be further issues down the line?

That shouldn’t happen, as the internal and external urls are seperated for a reason. :slight_smile:

Have you configured the setting for the “home” wifi? This setting is necessary for the internal url to work.

I’ve started getting the error “the certificate for this server is invalid” in my Home Assistant companion app and can’t access Home Assistant from it anymore. I don’t know if this is because I changed one of the routers in my mesh or if it happened independently of it. On top of that, I occasionally get an unsafe-website warning in Chrome which I have to click through in order to get to HA on my PC.

It’s clear these issues are related to the port-forwarding I’ve done as I haven’t had them before that.

No, where do I find it? What do I configure?

Fixed it by following another tutorial that included an extra step to fix an issue my FritzBox router specifically has (in the top comment) and that did 2 other things differently too from the one I used before.
If the issue reoccurs I’ll try using Nginx as a Reverse Proxy because someone on Reddit recommended that to me.