Encryptions issues with DuckDNS in v. 3.12

Installation
1

Hi,

After I updated to version 3.12 my duckdns login dosent work over with https only http.
It was working fine prior to the update.

From the DuckDNS log:

INFO: Using main config file /data/workdir/config

  • Account already registered!
    [20:55:22] INFO: OK
    XX.XX.XX.XX
    NOCHANGE

INFO: Using main config file /data/workdir/config

Processing Domain.duckdns.org

  • Creating new directory /data/letsencrypt/domain.duckdns.org …
  • Signing domains…
  • Generating private key…
  • Generating signing request…
  • Requesting new certificate order from CA…
  • Received 1 authorizations URLs from the CA
  • Handling authorization for domain.duckdns.org
  • 1 pending challenge(s)
  • Deploying challenge tokens…
    OK + Responding to challenge for domain.duckdns.org authorization…
  • Challenge is valid!
  • Cleaning challenge tokens…
    OK + Requesting certificate…
  • Checking certificate…
  • Done!
  • Creating fullchain.pem…
  • Done!
    [21:00:59] INFO: OK

DuckDNS config:
'lets_encrypt:
accept_terms: ‘true’
certfile: fullchain.pem
keyfile: privkey.pem
token: token-from-duckdns
domains:

Router is set to forward port 443 to 8123 to my RPI IP adress.

Connecting with http://domain.duckdns.org:443 works perferctly. But I preffer having the connection enrypted.

Any idea on whats wrong?

2

If you can still reach it using http:// in a browser, then your configuration is wrong in your configuration.yaml. When configured correctly you can only use https://

A common mistake that users make is removing the # but leaving a space in front of http: like this
image

The above is the same as having no configuration for http: at all;

It needs to be all the way to the left in your configuration.yaml file like this

image