Duckdns reboot issue

Configuration
21

I do not use “base_url” has been depreciated in HA 0.110 .

HTTP - base_url is deprecated and replaced by an internal_url and external_url core configuration setting "in the UI ". - (@frenck - #35224) (basic config docs) (http docs)

Concerning the guides , for the moment I use the HA doc for Duckdns addon as it should be sufficient for DDNS and LetsEncrypt certificate

About

Duck DNS is a free service that points a DNS (sub-domains of duckdns.org) to an IP of your choice. This add-on includes support for Let’s Encrypt and automatically creates and renews your certificates. You need to sign up for a Duck DNS account before using this add-on.

Remote access is working using http + 2FA for the moment with Duckdns but I do not want to switch to Duckdns+LetEnscrypt + NGINX before basic configuration with Duckdns works (https)

22

So what’s you duckdns configuration ?
Can you show me ?

23

Here it is :

lets_encrypt:
  accept_terms: true
  certfile: fullchain.pem
  keyfile: privkey.pem
token: xxxxxxxx
domains:
  - xxxx.duckdns.org
aliases: []
seconds: 300
24

does it works like this ?
and you configuration.yaml , can you show me ?

25

Like this part of Duckdns addon works for ddns + remote access using http only no https

The configuration file with http part commented because it prevents HA to start/restart

# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml
sensor: !include sensor.yaml
notify: !include notify.yaml
alarm_control_panel: !include alarm.yaml
#  customize: !include customize.yaml

homeassistant:
  media_dirs:
    media: /config/media/music
  allowlist_external_dirs:
    - /config/media/camera
  auth_mfa_modules:
    - type: totp
# HTTPS with DuckDNS 
# http:
#  ssl_certificate: /ssl/fullchain.pem
#  ssl_key: /ssl/privkey.pem

#
26

and with this setup you can access remotely on your HA server ?

27

with http integration commented , I can access remotely using https but the certificate is not valid

So i am always back to this http integration issue

Other topic with same issue with Duckdns+Letencrypt addons

28

I tested again after my head rested during several days and it works with http integration enabled in configuration.yaml file.

I think I made mistakes somewhere when testing with http and not with https in local network as it should be ( https://192.168.1.x:8123 works )