Custom Domain through Nabu Casa not validated

Configuration
1

Hello,

I want to access my Home Assistant with a custom subdomain home.example.com but it does not work.
My domain has been registered at Namecheap.com for years.

Here a the steps I followed:

  • Go to https://account.nabucasa.com/
  • In the Settings page, section “Add Custom Domain”, I type my subdomain home.example.com
  • I’m asked to add two CNAME records so I go to namecheap.com
  • Select my domain name and got to “Advanced DNS” section
  • I add first CNAME record with host = home.example.com, value = 123456789fakevalue098765432.ui.nabu.casa and TTL = Automatic
  • I add second CNAME record with host = _acme-challenge.home.example.com, value = _acme-challenge.123456789fakevalue098765432.ui.nabu.casa and TTL = Automatic
  • Go back to Nabu Casa, click on “Validate”
  • Both records fail to be validated
  • I wait 72 hours and it is still failing.

Any idea?
Thank you for your help.

Julien

2 Likes
3

Solved the issue for me…

For me it was this: account.nabucasa.com gives you the info to copy to make your CNAME records. but this info is not exactly to be copied! In your example:

  • I add first CNAME record with host = home.example.com, value = 123456789fakevalue098765432.ui.nabu.casa and TTL = Automatic

Just copy:
host = home (without .example.com)
value = 123456789fakevalue098765432.ui.nabu.casa. (note the DOT at the end!!!)

  • I add second CNAME record with host = _acme-challenge.home.example.com, value = _acme-challenge.123456789fakevalue098765432.ui.nabu.casa and TTL = Automatic
  • Go back to Nabu Casa, click on “Validate”

Just copy:
host = _acme-challenge.home (without the .example.com)
value = _acme-challenge.123456789fakevalue098765432.ui.nabu.casa. (again note the DOT at the end)

This fixed it for me! Hope it helps you!

14 Likes
4

Thank you for your support, it works for me too now. :+1:

5

Having this issue as well, also using Namecheap.

6

Hey folks! I ran into the same issue today and was about to start up a support ticket, until I tried this:

I am using Cloudflare for DNS and I was using home.example.com with literally home as the subdomain prefix. After changing it to ha.example.com, it started working properly and validated. (Note to double check all the above suggestions too!) Not sure what was going on, but maybe try changing your subdomain prefix to something else to see if that kicks something somewhere in the chain :slight_smile:

1 Like
7

I’m still fighting to get this working with TransIP. Adding the dot at the end for the acme challenge worked, but not so much for the ha subdomain. I’m a little surprised that such a feature is still not working well after a number of years.

8

Spent days trying to get this working and then found you… :superhero: