Duckdns stop working and i got this fauld

Installation Home Assistant OS
1

i cant connct to hassio any more whit duckdns.
it worked very well but now somehing happend and i cant find what is wrong.
i already tried a new install andchanging the port and incert https:// but no change at all.
i search for answer but cant something egual .

this show up in the log

# INFO: Using main config file /data/workdir/config
+ Account already registered!
[13:36:25] INFO: KO
# INFO: Using main config file /data/workdir/config
Processing abc,duckdns.org
 + Signing domains...
 + Generating private key...
 + Generating signing request...
Error Loading request extension section SAN
548272361024:error:2207507C:X509 V3 routines:v2i_GENERAL_NAME_ex:missing value:crypto/x509v3/v3_alt.c:512:
548272361024:error:22098080:X509 V3 routines:X509V3_EXT_nconf:error in extension:crypto/x509v3/v3_conf.c:47:name=subjectAltName, value=DNS:abc,duckdns.org

my config looks like this.

http:
  api_password: !secret http_password
  base_url: https://abc.duckdns.org:8123
  ssl_certificate: /ssl/fullchain.pem
  ssl_key: /ssl/privkey.pem

iam using hassio 0.100.3. on raspberry pi 4 1gb 64 and duckdns 1.10
what to do now?

2

Did you just update?

Read the breaking changes about api password:

3

i didnot update to 0.101

4

Have your certificates expired?

5

no that is ok

6

found one , must be . fault but it still doesnot work.
but log is changed back to ok.
but still cant connect to hassio

# INFO: Using main config file /data/workdir/config
+ Account already registered!
[14:23:26] INFO: OK
89.180.68.73
NOCHANGE
# INFO: Using main config file /data/workdir/config
Processing abc.duckdns.org
 + Creating new directory /data/letsencrypt/abc.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 abc.duckdns.org
 + 1 pending challenge(s)
 + Deploying challenge tokens...
OK + Responding to challenge for abc.duckdns.org authorization...
 + Challenge is valid!
 + Cleaning challenge tokens...
OK + Requesting certificate...
 + Checking certificate...
 + Done!
 + Creating fullchain.pem...
 + Done!
[14:29:25] INFO: OK
**.***.73
NOCHANGE
7

Why doesnot work duckdns?

8

The KO response from duckdns means it was unable to update your domain with your current IP address.
API password in http is now depreciated - you can’t use that anymore.
Do you have router forwarding setup for 8123?
I tried to connect to your http://89.180.68.73:8123/ but it won’t connect so I expect not.