Hi everyone. For years I had a duckdns domain combined with Home Assistant generated and always updated with the DuckDns addon. I recently created a ThingsBoard server and I had the terrible idea of using the same domain on port 10443 instead of 443 and I created a certificate with Caddy which worked perfectly.
yesterday the Home Assistant certificate expired and this is not renewed by the addon because upon checking it realizes that the certificate for that domain is valid until March. But this is actually what ThingsBoard does.
So I created a new domain for ThingsBoard with a new certificate but I can't revoke the old one because I can't find the same one as its private key. how could I solve it?
Here is a list of issued certificates crt.sh | green-home.duckdns.org, the latest being 2024-12-25. Why not just start serving up the latest certificate?
So it runs locally and not remotely, so no certificate (private key) for your domain is in third party hands which you actually might want to revoke? Because if it's just locally, there's no need to revoke.
How does revoking come into play with "get the certificate working again"?
It's probably a better idea to just explain what you have and what you want, so we can help you with that, instead of asking for something very specifically which probably isn't necessary, such as revoking a certificate.
The only reason to revoke a Certificate is when the Private Key has been compromised. If you're doing a fresh install, or anything like that - you can just forget the Certificate ever existed*. If you've accidentally deleted your Private Key, you can also just forget the Certificate ever existed.
When you revoke a Certificate, you're not just removing it locally - you're setting forth a global mechanism across the SSL ecosystem that reports the Certificate as Invalid and Untrustworthy. That's just not necessary in these situations.
* If you can move the Certificate, Key and Account info to the new server - you should do that.
On Home Assistant if you go to the indicated domain, you will see that the certificate has expired. This is handled by the DuckDns Addon. If I restart the addon this log appears
# INFO: Using main config file /data/workdir/config
Processing green-home.duckdns.org
+ Checking domain name(s) of existing cert... unchanged.
+ Checking expire date of existing cert...
+ Valid till Feb 22 00:47:17 2025 GMT (Longer than 30 days). Skipping renew!
I could try to create a new one with certbot without setting up crontab for renewal. once this expires I think the addon will take care of renewing it. Do you think this could be a solution?
I agree, but I don't understand why duckdns then notices that there is a certificate that hasn't expired and consequently doesn't update. all certificates created in December were created with certbot or Caddy on another server using the same domain.
Does Home Assistant and Caddy place the certificates and private keys in the same location as Certbot?
How are the certificates and private keys being copied to the target server?
Good morning everyone, I uninstalled the addon, loaded an old Home Assistant backup and now the certificate has renewed successfully. Thank you all for your patience