Support custom domains for remote control about hass-nabucasa HOT 5 CLOSED

Is there anything the community can do to help you on this issue?

from hass-nabucasa.

👋 For everyone following this issue:

You can now add this to the account page if you are running Home Assistant 2023.9.2 or newer.
More details here: https://nabucasa.com/config/remote/#using-a-custom-domain

from hass-nabucasa.

This is something we eventually want to do but that's not currently on the roadmap.

from hass-nabucasa.

I realize following does more / not exactly what you asked for as it requires you to run additional docker container and forward ports on router, but if you're in position to do so (homelab enthusiast etc) it works great to access ha (or anything you run locally) from outside with user friendlier secure https address.

I use https://github.com/jc21/nginx-proxy-manager + wildcard dynamic dns (can be proper domain too doesn't have to be ddns) for accessing all my services from outside. It will automagically create and renew LetsEncrypt certs for all the domains and has a very user friendly ui to set it all up.

So for example for HA I use ha.myhost.ddns.net, so in npm ui I create proxy host for incoming domain ha.myhost.ddns.net and proxy it to w/e host runs ha, then accessing https://ha.myhost.ddns.net will access my ha from anywhere securely.

Maybe someone finds this helpful

from hass-nabucasa.

Has this been added to the roadmap yet? I've been hoping for this feature for quite a while. Another user posted a possible way to support this by changing a couple of lines of code to allow a user to add a secondary/alternate domain to the lets encrypt cert: https://community.home-assistant.io/t/allow-nabu-casa-cloud-instance-to-be-accessed-via-custom-dns-cname-hostname/258221 (last post in the thread).

I basically have the same reason as he does for not wanting to use hugalafutro's helpful suggestion, because I don't want to open / port forward ports to my internal home network.

from hass-nabucasa.