Can't connect through duckdns (solved in posts 5 & 6)

[stevemann (Stephen Mann (YAML-challenged))]

It’s been weeks since my DuckDns domain has been able to connect to my Home Assistant. I am wondering if I have a problem with Lets Encrypt. According to Remote access for Home Assistant:

After you check your configuration from the command line and then restart Home Assistant you’ll need to use https:// to access your system, even from your local network.

Now is a good time to check that you can access it using https:// - knowing it works will help you later if you run into issues.

But, https does not work here:
http://192.168.1.57:8123/ opens Home Assistant.
https://192.168.1.57:8123/ returns:

This site can’t provide a secure connection
192.168.1.57 sent an invalid response.

My current Lets Encrypt configuration is as created by installing the DuckDns add-on:

accept_terms: true
algo: secp384r1
certfile: fullchain.pem
keyfile: privkey.pem

I also tried (based on the information here):

accept_terms: true
algo: secp384r1
certfile: /ssl/fullchain.pem
keyfile: /ssl/privkey.pem

Neither works.

Any ideas for troubleshooting?
Note: in one of my earlier attempts to fix this, I deleted the DuckDns add-on and reinstalled it.

[Tinkerer (aka DubhAd on GitHub)]

Iit sounds like you didn’t add the required lines to http:, see All SSL types in the guide you followed.

[stevemann (Stephen Mann (YAML-challenged))]

@Tinkerer

it sounds like you didn’t add the required lines to http:, see All SSL types in the guide you followed.

Thanks. This is certainly more progress than I’ve made on my own. I appreciate the assistance.
Now, http://192.168.1.57:8123 returns, as expected:

This page isn’t working
192.168.1.57 didn’t send any data.

Curiously, https://192.168.1.57:8123 returns
This server could not prove that it is 192.168.1.57; its security certificate is from sxxx.duckdns.org.

('xxx’is my DuckDns domain)

BUT, https://xxx.duckdns.org:/8123 does work on my local network and off network. This is real progress!

Now the bad news?
Upon restarting Home Assistant, I am getting an “Invalid Config” notification:

Invalid config
The following integrations and platforms could not be set up:

ssdp (Show logs)
dlna_dms (Show logs)
default_config (Show logs)

And the logs:

Logger: homeassistant.setup
Source: setup.py:205
First occurred: 2:43:22 PM (2 occurrences)
Last logged: 2:43:25 PM
Setup failed for dlna_dms: (DependencyError(…), ‘Could not setup dependencies: ssdp’)
Setup failed for default_config: (DependencyError(…), ‘Could not setup dependencies: ssdp’)

Logger: homeassistant.setup
Source: setup.py:205
First occurred: 2:43:22 PM (2 occurrences)
Last logged: 2:43:25 PM
Setup failed for dlna_dms: (DependencyError(…), ‘Could not setup dependencies: ssdp’)
Setup failed for default_config: (DependencyError(…), ‘Could not setup dependencies: ssdp’)

Logger: homeassistant.components.cert_expiry
Source: helpers/update_coordinator.py:215
Integration: Certificate Expiry (documentation, issues)
First occurred: 2:43:41 PM (1 occurrences)
Last logged: 2:43:41 PM
Error fetching xxx.duckdns.org data: Connection refused by server: xxx.duckdns.org:443

---

Do these errors mean anything to you?

[Tinkerer (aka DubhAd on GitHub)]

You need to check the log file for information about why ssdp wasn’t set up.

[Tinkerer (aka DubhAd on GitHub)]

@stevemann

Error fetching xxx.duckdns.org data: Connection refused by server: xxx.duckdns.org:443

Earlier you said you needed to use port 8123… so that’s why that’s failing

[stevemann (Stephen Mann (YAML-challenged))]

@Tinkerer

Earlier you said you needed to use port 8123… so that’s why that’s failing

I understood that I need both ports 443 and 8123 forwarded in my router. However, I looked at the router again and I had port 443 going to 8123. I changed it to 443 -to- 443 and that error is gone.

---

On the other errors. The log files don’t tell me much (and they are off-topic for my DuckDns question). But here is my log file. If you have any tips for me, thank you. Otherwise, I will mark the thread as solved.

Home Assistant Core
Unable to set up dependencies of dlna_dms. Setup failed for dependencies: ssdp
10:42:57 PM – (ERROR) setup.py - message first occurred at 10:42:55 PM and shows up 5 times
Setup failed for dlna_dms: (DependencyError(…), ‘Could not setup dependencies: ssdp’)
10:42:43 PM – (ERROR) setup.py - message first occurred at 10:42:40 PM and shows up 2 times
Unable to set up dependencies of dlna_dms. Setup failed for dependencies: ssdp
10:42:43 PM – (ERROR) setup.py - message first occurred at 10:42:40 PM and shows up 2 times
Error handling when_setup callback for frontend
10:42:33 PM – (ERROR) helpers/network.py - message first occurred at 10:42:33 PM and shows up 2 times

dlna_dms
dlna_dms = DLNA Digital Media Server integration
I have a lot of Alexa Echo devices that integrate as media_player.xxx and they all appear to be working.

The first occurrence of this error:
Log Details (ERROR)
Logger: homeassistant.setup
Source: setup.py:381
First occurred: 10:42:55 PM (5 occurrences)
Last logged: 10:42:57 PM

Unable to set up dependencies of dlna_dms. Setup failed for dependencies: ssdp
Unable to set up dependencies of upnp. Setup failed for dependencies: ssdp

ssdp
ssdp = Simple Service Discovery Protocol (part of UPnP)
The only integration I have on the list in the documentation is my Samsung phone, and the integration appears to be working.

[Tinkerer (aka DubhAd on GitHub)]

You (still) need to look in the file on disk, home-assistant.log, and look for the first mention of ssdp to find out why SSDP is failing. Once you fix that the other problems will go away.

[stevemann (Stephen Mann (YAML-challenged))]

I am starting a new thread since this has nothing to do with the original topic.