DuckDns Let' Encrypt wont' encrypt

Configuration
1

Hello,

I use the duckdns-letsencrypt-addon but it’s not encrypted.
So when I try to open https://hxxxxxm.duckdns.org:8123 nothing happens.
Http works fine (without encryption).

I use a ipv6 hassio and maybe thats the problem?

I already opened the ports 8123, 443, 80 over the option “IPv6 Host Exposure” in my router.

The log-files looking good:

6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
# INFO: Using main config file /data/workdir/config
+ Account already registered!
[20:28:05] INFO: OK
95.xxx.59.165
NOCHANGE
[20:28:05] INFO: Renew certificate for domains: hxxxxxm.duckdns.org and aliases: 
# INFO: Using main config file /data/workdir/config
Processing hxxxxxm.duckdns.org
 + Checking domain name(s) of existing cert... unchanged.
 + Checking expire date of existing cert...
 + Valid till Jun  6 10:56:49 2022 GMT (Longer than 30 days). Skipping renew!

Here is my config file:

aliases: []
domains:
  - hxxxxxm.duckdns.org
lets_encrypt:
  accept_terms: true
  algo: secp384r1
  certfile: fullchain.pem
  keyfile: privkey.pem
seconds: 300
token: xxx

Thank you for help!

2

Try this video. Sounds like you need to get a few things changed on port forwarding. You should be able to call https://xxxxxx.duckdns.org and have it connect.

3

You also have to configure HA to use the certificates:

http:
  ssl_certificate: /ssl/fullchain.pem
  ssl_key: /ssl/privkey.pem
4

Thank you, I totally forgot it!
Now it works fine.