I previous used my custom domain (ha.mydomain.com) through Cloudflare(d) and Let's Encrypt, but I had some issues so I changed over to Nabu Casa. I've set up my custom domain with Nabu Casa.
I just received a warning that my certificate for ha.mydomain.com will expire soon. I'm not sure whether I still need Let's Encrypt to auto-renew my certificate at this point?
I wasn't able to find anything about this via Google or Discord search. Thanks for your help!
#Do I need Let's Encrypt w/ Nabu Casa and a custom domain?
keen hare
balmy lodge
No, HA cloud takes care of that
keen hare
No, HA cloud takes care of that
That's what I was hoping to hear. 🎉
Thanks for the quick help!
keen hare
Now that my certificate has expired, I get the following error in Home Assistant:
Logger: homeassistant.components.cert_expiry.coordinator
Source: components/cert_expiry/coordinator.py:48
integration: Certificate Expiry (documentation, issues)
First occurred: 1:07:56 PM (2 occurrences)
Last logged: 1:07:56 PM
Certificate validation error: ha.mydomainame.net [1]
Any idea why this might be the case?
I'm getting the following error when starting Home Assistant and I suspect it's the cause of some other issues I'm having.
Wondering if it's related, i.e. Google Assistant can't reach HA because the cert is expired?
Logger: homeassistant.core
Source: core.py:551
First occurred: 1:07:56 PM (1 occurrences)
Last logged: 1:07:56 PM
Something is blocking Home Assistant from wrapping up the start up phase. We're going to continue anyway. Please report the following info at https://github.com/home-assistant/core/issues: template.sensor, hacs, tplink.number, script, cover, wled.light,
[list of 50+ more items],
hassio.update, bluetooth, wake_word, persistent_notification The system is waiting for tasks: {<Task pending name='Task-2352' coro=<AbstractConfig.async_initialize.<locals>.sync_google() running at /usr/src/homeassistant/homeassistant/components/google_assistant/helpers.py:114> wait_for=<_GatheringFuture pending cb=[Task.task_wakeup()]> cb=[set.remove()]>}
If you are sure you configured your domain correctly, following the steps on the nabu casa page and don't have it still pointing your DNS records to cloudflare, I'd suggest you open a ticket with NC directly
keen hare
If you are sure you configured your domain correctly, following the steps on the...
Thanks again, Josef!
If you are sure you configured your domain correctly,
I'm not entirely sure, to be honest.
I was working with ChatGPT yesterday trying to figure out if I have the correct configuration.
Not asking you to slog through troubleshooting with me, but does any of this look alarmingly wrong to you?
I'm particularly suspect of the http: section in configuration.yaml. I'm not sure whether it's required for Nabu Case. (When I enable it, I lose local access via http://<ip>:8123.)
sage bolt
Nabu casa remote doesn’t need any of the http: config