Issues with LetsEncrypt

Configuration
1

Good afternoon,
I have managed successfully to point my internal IP to chosen domain with Duck DNS.

However, whenever I am trying to acquire a certificate to encrypt my connection with Let’s Encrypt I am out of luck. At the beginning I have tried to setup DuckDNS addon in Hassio with following configuration frontend crashes. My addon configuration:

{
  "lets_encrypt": {
    "accept_terms": true,
    "certfile": "/ssl/fullchain.pem",
    "keyfile": "/ssl/privkey.pem"
  },
  "token": "[****]",
  "domains": [
    "****.duckdns.org"
  ],
  "seconds": 300
}

My configuration.yaml looks like this:

http:
base_url: “***.duckdns.org:8123”
ssl_certificate: “/ssl/fullchain.pem”
ssl_key: “/ssl/privkey.pem”

And I have forwarded 443 port to 8123.

Despite my efforts, whenever I save my settings and try to login I get this error message on the browser:

image
image1110×770 17.6 KB

2

In comparing your configuration.yaml to mine (I am using same tools as you), my base url does not have the colon or port number. My base URL is: ***.duckdns.org

Give that a try and hopefully it fixes it.

3

By the way I used this guide https://home-assistant.io/docs/ecosystem/certificates/lets_encrypt/

4

I have tried all possible configurations but all of them caused same result - frontend crash.

Additionally I tried to use Putty to setup LetsEncrypt. I didn’t have any isues to setup DuckDNS. However, whenever I tried run certbot client
wget https://dl.eff.org/certbot-auto
I received such error in Putty

image
image992×103 5.3 KB

:frowning:

5

Is there anything in the log files? Does the user that runs HA have the correct permissions to the certificate files?

6

If you are using hass.io, then you should only setup the duckdns add-on. I would remove both add-ons and then just set up the duckdns add-on.