It’s still down 
Anyone has any other idea of a replacement?
i have reinstalled HA and install DUCKDNS as usual… log indicate for OK ( which means settings are correct) but i cannot log my HA using duckdns,
i also changed from PI 3B+ to Pi 4 , Static IP defined by routed and i have updated the MAC address
I have no idea why you’d change the mac address of your pi, just change the association on your router to assign your preferred address to the HA instance and have the port forwarding to the same address.
Check out : -
MAC address changed as i am using new PI,
Port forwarding was updated as well without any change
That’s just nuts!
My duckdns domain stopped working after a while, although I didn’t change any settings. Remote acces adress (https…mydomain…duckdns.org) works if accessed from local network, but fails to load from outside, it shows briefly loading page then this error
https://mydomain.duckdns.org:xxxxx/auth/authorize?response_type=code&redirect_uri=https%3A%2F%2Fmydomain.duckdns.org%3Axxxxx%2F%3Fauth_callback%3D1&client_id=https%3A%2F%2Fmydomain.duckdns.org%3Axxxxx%2F&state=eyJoYXNzVXJsIjoiaHR0cHM6Ly9oYWlzdXMuZHVja2Rucy5vcmc6NTE5NzkiLCJjbGllbnRJZCI6Imh0dHBzOi8vaGFpc3VzLmR1Y2tkbnMub3JnOjUxOTc5LyJ9 might be temporarily down or it may have moved permanently to a new web address.
ERR_FAILED
My config file looks like this
Configure a default setup of Home Assistant (frontend, api, etc)
default_config:
homeassistant:
external_url: “https://mydomain.duckdns.org:xxxxx”
internal_url: “https://homeassistant.local:8123”
duckdns:
domain: mydomain
access_token: xxxxxx
http:
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem
Text to speech
tts:
- platform: google_translate
group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml
lovelace:
mode: yaml
vacuum: - platform: xiaomi_miio
host:…
I noticed though that in Home Assistant Cloud settings, Remote control tab doesn’t stay enabled after refresh.