Account already registered!
[22:13:39] INFO: Starting DuckDNS…
[22:13:42] WARNING: KO
[22:13:42] INFO: Renew certificate for domains: juan---------.duckdns.org https://juancoenda.duckdns.org and aliases:
INFO: Using main config file /data/workdir/config
Processing https://juan--------.duckdns.org with alternative names: juancoenda.duckdns.org
Signing domains…
Generating private key…
Generating signing request…
Could not open file or uri for loading private key from /data/letsencrypt/https://juan--------.duckdns.org/privkey-1727226824.pem
28EB7CE9187F0000:error:1608010C:STORE routines:inner_loader_fetch:unsupported:crypto/store/store_meth.c:360:No store loader found. For standard store loaders you need at least one of the default or base providers available. Did you forget to load them? Info: Global default library context, Scheme (/data/letsencrypt/https : 0), Properties ()
[22:18:45] WARNING: KO
Hello, I am having this duckdns error when it runs, I have checked everything and I don’t know what else to do, Let’s Encrypt generates all the certificates correctly, the problem is that it does not send them to the same destination as where it is requested ducks. How can I fix this? I appreciate every help.
FINALLY THIS SOLVED PART OF MY ISSUE!!!
I have been on HA for 5 hours trying to install DuckDNS and add Samsung SmartThings integration since I got the HA Green out of the box. Plenty of comments and posts show http or https in the domain, only one person (WallyR) sorted that so thank you. Trouble was when I found that solution the first time round, I didn’t yet know about the erroneous white space character at the start of the duckdns token. And when I found that one, I forgot about the https or http or nothing in the domain in DuckDNS configuration screen.
BOTH the white space removed from the token AND removal of http or https from domain in DuckDNS configuration screen are required to get DuckDNS to run successfully.
But there’s more… As SmartThings still failed to install, I added a manual edit of configuration.yaml file (recommended in many similar posts) - using the ADD-ON called File Editor, which by default is set to INVISIBLE in the sidebar full of handy apps this one is clearly not handy, so no need to be visible… … I can’t remember how I made it visible again now (it was about 4 hours ago) but that’s also necessary.
This killed local access to my home assistant Green from my laptop altogether. My phone managed to reach it through the HA app, using the duckdns address xxxx.duckdns.org - but my laptop couldn’t reach it at all. After one attempt to add SmartThings from the phone app, I now can’t reach it from my phone either.
Another component is apparently patience - one user remarked they waited some 10 minutes for files to appear in their SSL directory.
THAT WAS (and is still) UNNECESSARILY HARD… And thank you.
I still can’t install SmartThings. But DuckDNS completed ok. It’s 3.55am. I’m going to bed. I can’t believe thousands of people are reading some of these forum posts and nobody picked up that initial setup of even the HA Green is a nightmare…