When DuckDNS is configured, I can't get access to the dashboard locally anymore

1

Hi Guys,

I’m trying for a while now to get remote access via DuckDNS to my hassio running on a Odroid C2.
When I configure the http in the configuration.yaml, I lose connection to the dashboard in any way, the remedy is to outcomment the HTTP in the config via Samba and then reboot Hassio to get local access again.

The logging for Hassio doesn’t give an error at all.
I port forwarded 443 External to 8123 Internal to the IP address of the Hassio.
Online port checker tells me that the 443 port is open when configured.

Configuration.yaml

http:
  base_url: my-domain.duckdns.org
  ssl_certificate: /ssl/fullchain.pem
  ssl_key: /ssl/privkey.pem

Duckdns config

lets_encrypt:
  accept_terms: true
  certfile: fullchain.pem
  keyfile: privkey.pem
token: My_token
domains:
  - my-domain.duckdns.org
seconds: 300

Duckdns Logging

# INFO: Using main config file /data/workdir/config
+ Account already registered!
[22:00:46] INFO: OK
MY_IP_ADDRESS
NOCHANGE
# INFO: Using main config file /data/workdir/config
Processing my-domain.duckdns.org
 + Checking domain name(s) of existing cert... unchanged.
 + Checking expire date of existing cert...
 + Valid till Jul 30 14:43:33 2020 GMT Certificate will not expire
(Longer than 30 days). Skipping renew!
[22:06:01] INFO: OK
MY_IP_ADDRESS
NOCHANGE

Does anyone have a clue what might be the issue?

2

I found that the SSL did not work properly and when the HTTP component is configured, connection non-SSL is not working anymore either.

I have used the method below to have local non-SSL connection and remote SSL with DuckDns and Nginx proxy following the link to the guide below.

All connections are working properly now.

1 Like