I have been fighting Home Assistant for the past four weeks. This week I have made it farther than any other time, but I am still struggling to understand what is wrong with my configuration.
I am running Home Assistant Supervised on a Debian 12 VM.
Here are all the modules and versions:
Home Assistant 2023.7.3
Supervisor 2023.07.1
Frontend 20230705.1 - latest
My goal is to get Home Assistant to interface with my existing Samsung SmartThings solution. This requires the use of a public certificate with all the parts and pieces working together before I can integrate Home Assistant with SmartThings. I have a domain via Cloudflare - bloomc.us. I have tried to follow the instructions to get a public certificate on my HA server.
I believe I finally completed this a couple days ago, but I still think something is not quite right.
Here is my Let’s Encrypt integration configuration. FYI. There is a bug in this add-on as it creates a DNS => DNS level when it only needs one DNS level entry.
domains:
- "*.bloomc.us"
email: <[email protected]>
keyfile: privkey.pem
certfile: fullchain.pem
challenge: dns
dns:
provider: dns-cloudflare
cloudflare_api_token: <redacted>
Here are the logs from the Let’s Encrypt integration with the Cloudflare information:
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/file-structure.sh
cont-init: info: /etc/cont-init.d/file-structure.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun lets-encrypt (no readiness notification)
s6-rc: info: service legacy-services successfully started
[18:19:13] INFO: Selected DNS Provider: dns-cloudflare
[18:19:13] INFO: Use propagation seconds: 60
[18:19:13] INFO: Use CloudFlare token
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Requesting a certificate for *.bloomc.us
Waiting 60 seconds for DNS changes to propagate
Successfully received certificate.
Certificate is saved at: /data/letsencrypt/live/bloomc.us/fullchain.pem
Key is saved at: /data/letsencrypt/live/bloomc.us/privkey.pem
This certificate expires on 2023-10-22.
These files will be updated when the certificate renews.
NEXT STEPS:
- The certificate will need to be renewed before it expires. Certbot can automatically renew the certificate in the background, but you may need to take steps to enable that functionality. See https://certbot.org/renewal-setup for instructions.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
If you like Certbot, please consider supporting our work by:
* Donating to ISRG / Let's Encrypt: https://letsencrypt.org/donate
* Donating to EFF: https://eff.org/donate-le
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped`
These logs lead me to believe the HA server is getting a public certificate from Cloudflare, However, I cannot get to my HA server from the Internet - https://ha.bloomc.us:8123.
I get the following error when I try to integrate SmartThings with Home Assistant:
If anyone can point me in the right direction I would appreciate it.