Problem with lets encrypt, home assistant and duckdns

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g., so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domains are:,,

I ran this command: for the two first domains I am using an add on from home assistant, for solhjemmet I am running the commands from the dehydrated tool from github ( commands: ./dehydrated --register --accept-terms, ./dehydrated -c. Which I suspect is at the back end of the addon from home assistant (haven't been looking).

It produced this output:
All seems fine I get the that everything is fine. Sorry can't paste the return messages here, I dont have the return availabe. But I cannot achieve what I want for any of the domains, the two first are for the same server, the latter for another. I cannot manage to remotely connect to my home assistant on the servers, it might be the port forwarding, (set up with 443->8123 and the ip adress of the server, which is made static) but it might be other issues..

My web server is (include version):

First is a Compulab fitlet mini computer, second is a raspberry pi 4

The operating system my web server runs on is (include version):
First is a Linux Mint 19.1 Tessa, second is raspberry OS buster

My hosting provider, if applicable, is:
telenor, don't think this is applicable though
I can login to a root shell on my machine (yes or no, or I don't know):
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
Well, sort of the for the first, not so for the pi
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): Not using certbot

My question: As I have written it might not be the encryption that is my issue, but when investigating all parts of my problem I bumped into something here on your pages, to check with Here are the results of that check: I understand nada of this, but it indicates that something is wrong I guess could, you enlighten me? The output is more or less the same for all three domains

Hi @dan-sol

these warnings are completely unrelevant.

DNS cookies aren't relevant if you want to create a certificate.

DNSVis dos not reveal a problem that would prevent LE.
I do see three different IPs (is any of these correct?):




This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.