Connection Problems with Custom Domain Forwarded to Nabu Casa

I recently started my trial of Nabu Casa and for convenience I setup a custom domain name that forwards to my Nabu Casa url. It works in some situations but I have the following issues:

  1. Using https version of the url in a browser returns the following error though the http version works fine (it just redirects to my Nabu Casa url in the address bar).

This site can’t be reached
took too long to respond.
Try:

  • Checking the connection
  • Checking the proxy and the firewall
    ERR_CONNECTION_TIMED_OUT
  1. Using even the http (non-s) version of the custom url in the companion app on iOS throws a 404 error despite working from other devices. I can browse to the url via http fine in Safari on the same iPhone and see it redirect to the Nabu Casa URL just like it does on desktop. I can also use the custom url in the 3rd party Wall Panel app on my Android tablet and it forwards and works as expected. I have been unable to test the official companion app on my Android tablet though.

First issue isn’t really a problem since it directs to the https when it forwards to the Nabu Casa url anyway but I’m curious why https for the custom domain doesn’t work.

Do you have certificate setup for custom domain?

Typing https is not enough.
You must acquire a cert and have some mechanism that append that cert to the domain

If you simply add https to domain and forward to nabu casa https will Not work. Since the nabu casa cert doesn’t match custom domain.

Many use nginx or Apache as reverse proxy on their server. Their domain sends request to nginx/Apache where the ssl cert is provided. After this, the request is sent to HA or nabu casa for you. SSL cert functions like ID. When my browser shows at your site I need you to show me ID and verify you are who you say when I get there. If you are not doing this, this is issue?

This makes some sense but I would expect to get an SSL error not a timeout like I’m getting. Did some quick searching and it appears a cert error is what should happen with a 301 redirect which is how this it setup and I confirmed via curl -v.

The problem occurs when you try to do a 301 or 302 redirect to an SSL URL (HTTPS URL) but the SSL certificate for that URL does not match the domain. It will throw a warning message saying the connection is untrusted or that there is a problem with the website’s security certificate in the user’s browser.
How to properly use SSL redirects without getting certificate error messages - JasonSamuel.com

Probably a moot point because a cert error will cause other headaches so I will likely just stick to http (which properly redirects to the https Nabu Casa url anyway) but it’s weird it times out.

Issue 2 is more problematic for me.