Unable to connect to Home Assistant. Custom domain w/Nabu Casa

Hi folks, hope you’re all doing well.

I’m planning to raise a bug feedback request on this one, but was hoping for some advice first please.

I’ve had HA for years, and have been using the DuckDNS add-on for most of that time. I also subscribe to Home Assistant Cloud from Nabu Casa, and so have a private url from that too.

I’ve had no connection issues with the DuckDNS or Nabu Casa Cloud urls at all - they always connects first time, every time, whether I’m at home or out and about.

In 2023.9 I was very excited to see that I could use the Remote UI alias feature to add an alias using my personal domain into the mix too. I moved all my sessions, apps, etc over to the new personal domain without issue.

However, a few times a day, when trying to connect, I get the below. This is the same across multiple devices, multiple users, multiple browsers, home and out-and-about etc.

If I bash “retry now” a bit, after a 10 second or so wait, it connects and I’m back up and running without issue for a while until it happens again.

It’s only with the personal URL, and my ui.nabu.casa and DuckDNS urls both continue to work without issue.

What logs should I look to include if I were to raise this as a bug? I’ve looked through the logs and it doesnt seem like there are any - it’s as if the browser cannot connect to the server, so I can’t imagine that HA Core is seeing much if anything on it’s side if anything.

Thanks in advance for your help, all ideas appreciated! :grinning::beer:

Screenshot 2023-10-06 at 10.50.57 am

Who hosts your alias url?

It’s hosted with Hover.

Screenshot above - I only have the CNAMEs for _acme- and my home assistant prefix in there.

As that obvioulsy is cloud based and the only major thing you added… if it smells like a duck and walks like a duck…

Did you manage to get this fixed?

If it’s like me with Gandi, you will need to add a final “.” at the end of the CNAME value like “xxxxx.nabu.casa.”