Received an email the other day saying my ertificate (or certificates) for the names listed below will expire in 20 days for nabu.casa.
Should I be concerned about this?
2 Likes
2 Likes
FWIW I just got one this morning as well.
The address is provided is a nabu casa IP address, not something pointing to my home. And I do not use remote access. So it appears nabu casa creates certs in our name (and email address) at their facility. Not suggesting that’s bad, but it certainly looks like it is something under their control not ours?
I’m just ignoring it, hopefully on June 24th things still work.
Received similar e-mail. Came across this post and assumed it would automatically renew. Today, I’ve noticed that my Remote UI is reporting unavailable. Just attempted to connect remotely and receive a SSL error.
Home Assistant Cloud is reporting the following for Remote Control
“Remote access is being prepared. We will notify you when it’s ready.”
Anyone else encountering this?
A reboot yesterday didn’t resolve the problem, but this AM, Remote UI reconnected with a Home Assistant restart.
I’ve gotten a couple emails about this as well, the most recent one saying it’s expiring in 10 days. That’s really cutting it close if they are auto-renewing. I imagine these should auto-renew before the 30 day warning email goes out.
Just checked my certificate and it’s been renewed, now showing expiry September 2019
I’ve had a couple of these emails and am now what appears to be renewal failures in the logs:
2019-06-11 00:00:16 ERROR (MainThread) [hass_nabucasa.acme] Can’t set challenge token to NabuCasa DNS!
2019-06-11 00:00:16 WARNING (MainThread) [hass_nabucasa.remote] Renew of ACME certificate fails. Try it lager again
Anyone else in this situation?
Any suggestion on fixes appreciated.
My remote connection failed late last night (UK) - I happened to notice while I was porting some scheduled scripts from Python2 to Python3.
A restart of HomeAssistant resolved the issue, including a certificate renewal.
Also worth noting that 0.94.3 has been released with some fixes for certificates ( * Fix errors when renewing remote UI certs (#24481)) although this wasn’t necessary for my renewal. I’m still on 0.93.2 although intending to upgrade this weekend.
Covered here: FAQ
Specifically:
I received an email from Let’s Encrypt. Do I need to renew my own certificates?
You do not need to do anything. The certificates for your instance will renew automatically as long as your subscription is active
1 Like
I have the same issue:
2019-06-22 00:00:18 ERROR (MainThread) [hass_nabucasa.acme] Can’t set challenge token to NabuCasa DNS!
2019-06-22 00:00:18 WARNING (MainThread) [hass_nabucasa.remote] Renew of ACME certificate fails. Try it lager again
Are you updated to 94.4? There were fixes regarding cert renewals in .2 and .3 (but you might as well go for .4)
I also got this expires July 1 2023 for the summer cabin.
At home it still works…
But I suspect that the root to the evil is the mobile broadband.
The speed varyies from 0,09 to 15 Mbps…
I have put an order for a fibre, cause this sucks!
1 Like
And once again!
Three month since last time!
I had to shut everything down, preparing for the fiber connection. The tube is digged in to the house.
Now I’m just waiting for them to blow the fiber…
But when I reconnectet everything, and started it all up, I could not connect via Nabu Casa, they are “preparing…” . Which seems that there is a problem with the certificate from Let’s Encrypt.
At home there is no problem. I blame it on the junky mobile broadband provider.
I hope that the fiber connection will work in a month or so. Then I can use the Pfsense firewall, and almost have the same setup as at home!
One and a half week to get the external access working.
Probably there will be some delay with the fiber.
The guys that plowed the tube did a really great job on my property
But on the road and other places, not that great, it is a disaster to say the least!
They will not blow the fiber until this is fixed…