DuckDNS - SSL certificate not valid

Third party integrations
1

Hi
I very new with HA and have recently setup my own HA instance running in virtualbox on my home server. HA is running just fine locally, and like many other I would like to access HA remotely.
I have followed a few guides (e.g. official from Github) on how to configure a secure connection with DuckDNS and Let’s Encrypt. I’m now able to access HA at https://www.xxxx.duckdns.org, however Chrome complains that my certificate is invalid.

image

My DuckDNS Config:

aliases: []
domains:
  - xxxxxxx.duckdns.org
lets_encrypt:
  accept_terms: true
  algo: secp384r1
  certfile: fullchain.pem
  keyfile: privkey.pem
seconds: 300
token: 22b0xxxxxxxxxxxxxx4a

My configuration.yaml

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

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

I have banging my head against the wall for some time and would very much appreciate some input on how I may resolve this issue.

Note that in my network I have double NAT. My modem is configured to forward public 443 to 8123, and my router from 8123 to 8123.

Thanks.

2

I don’t think the www. in front of your URL is valid…it should just be https://yourhost.duckdns.org

3

Wow, now I truly feel like an idiot. Thank you so much!

4

LOL, all good and glad it works. Welcome to HA btw! You are in for a lot of fun!