#alias can not be used, please contact support. Custom Domain - DNS Set and Validated.

1 messages · Page 1 of 1 (latest)

loud nebula
#

I tried to setup my Custom Domain and its not saving. Anyone experience this?

iron silo
#

Have you used it with a different Nabu Casa account?

#

It will be held for 90 days after that account was deleted, or after the alias was disabled, for security reasons. It is recommended to use a different CNAME until that time (or just a different CNAME in general, there's an unlimited number you could use)

loud nebula
#

i got past that, but my custom domain gives a 404 error, the remote address works fine and i can login, but my domain gives a 404

#

@iron silo

iron silo
#

did you restart ha after validating it?

loud nebula
#

nevermind its working now

#

yes i did

iron silo
#

it takes a minute or so for your ha server to request and download the certificate for the alias

#

you might want to delete the domain you are mentioning here

loud nebula
#

i will, the app is saying cert mismatch

#

any ideas @iron silo

iron silo
#

delete and re-add your server in the app?

loud nebula
#

did that same message

#

should i restart again?

#

hmm same error @iron silo

iron silo
#

uninstall or clear data for it

loud nebula
#

already tried clearing cache and then data no change, should i try uninstalling

iron silo
#

there's no issue with the cert, it's whatever data the app or device is holding on to

#

or use your nabu casa url in the app

loud nebula
#

uninstalling and reinstalling same problem

#

interesting the casa url worked but my domain didnt

loud nebula
#

@iron silo

The Android app is rejecting https://myhome.papalpenguin.com because the TLS certificate being presented is for a different hostname: your screenshot shows the certificate “Issued To” is lb9ckdtvjqeb62izgmxbsxg7nupiboso.ui.nabu.casa, not myhome.papalpenguin.com. A browser can appear “fine” if you’re being redirected/forwarded to the .ui.nabu.casa address, but the app does strict hostname validation and fails when the cert name doesn’t match the URL you entered.

Any chance this might be the reason​

iron silo
#

Check the certificate details at Settings > Home Assistant Cloud > Security Options > More details

loud nebula
#

Certificate information
Certificate expiration date: April 5, 2026 at 10:15 AM
(will be automatically renewed)

Certificate fingerprint: b2d1df9c61642354ef0dcf57d443567dc551178e

Alternative names:

lb9ckdtvjqeb62izgmxbxsg7nupiboso.ui.nabu.casa
myhome.papalpenguin.com

#

the screenshot was from my browser

#

@iron silo it looks like two different certificates

#

do I need to get a seperate cert for my domain

#

hmm using my domain via browser on my pc, home assistant keeps not wanting to connect

#

hmm if you have any ideas, ill just use the nuba.casa link for now

iron silo
#

what you're seeing is correct. You might try restarting your router?

loud nebula
#

yeah i can try that