I have Hass.io with FreeDNS and SSL set up with the Let’s Encrypt add-on which has been working fine. Now I have registered my own domain and would like to add this as well.
I added the new domain to the Let’s Encrypt config as shown below (opened port 80 for the http challenge) and started the Let’s Encrypt service to renew / create the certificates, but I am not sure it worked. When using the new domain name (https://www.new-domain.com:443) to connect to HA it comes up as not secure / certificate error.
{
"email": "[email protected]",
"domains": [
"xxxxxxx.privatedns.org",
"*.new-domain.com"
],
"certfile": "fullchain.pem",
"keyfile": "privkey.pem",
"challenge": "http",
"dns": {}
}
Do I also need to add the new domain in the configuration.yaml file. If so, how? This is how it is in the config today:
http:
base_url: https://xxxxxxx.privatedns.org:8123
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem
Edit:
I see now from the Let’s Encrypt log file that there is no mention of the added new domain. Is there something else I need to do when adding a domain to the Let’s Encrypt config?
Saving debug log to /var/log/letsencrypt/letsencrypt.log
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Processing /data/letsencrypt/renewal/xxxxxxxx.privatedns.org.conf
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Cert not yet due for renewal
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
The following certs are not due for renewal yet:
/data/letsencrypt/live/xxxxxxxx.privatedns.org/fullchain.pem expires on 2020-04-06 (skipped)
No renewals were attempted.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -