Changing from DuckDns to DynuDns

Hi Community

I have used DuckDns for a long time, but with Google Home integration (Not Nabu Casa), system lacks.

Reading many topics here, I have switched to DynuDns and using the DynuDns addon

Configuration runs and returns a statuscode 200, so all should be good.

I can use the xxx.giize.com to access my system, but calling HA in a browser returns no safe connection.

Looking in chrome, Certificate is stil DuckDns.
I have even tried multi-dns add-on, but that did hang on Domains are changed and never finishes

any suggestion on what I am missing

Marinus

Seems like in the \SSL\ directory the certfile: fullchain.pem & keyfile: privkey.pem are still there from what DuckDNS created.

You can check that. Back it up them up, then delete them and see if the DynuDns creates new ones.

Hi Roderik,

renamed themand ran letsencrypt, returned an error mising api key.

Ran dynu dns add on, it reported succefull 200, but no new keys in /ssl/

I managed to create new keys in /ssl/ by asking letsencrypt to challange http instead of dns
Restarting HA, it worked, thks.

BTW, is it not possible to have to ssl certificates?
thks
Marinus