Home Assistant, DUCK DNS cert not going my way

[macnet1]

I'm a newbie looking for a wee bit of help folks, this is my challenge today

My domain is: thompsonhouse.duckdns.org

Port 80 and 443 are open im unsure were 1078 is coming from

[07:38:56] INFO: Selected http verification
[07:38:56] INFO: Detecting existing certificate type for thompsonhouse.duckdns.org
Saving debug log to /var/log/letsencrypt/letsencrypt.log
[07:38:59] INFO: No certificate found - using 'ecdsa' key type.
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Requesting a certificate for thompsonhouse.duckdns.org

Certbot failed to authenticate some domains (authenticator: standalone). The Certificate Authority reported these problems:
Domain: thompsonhouse.duckdns.org
Type: connection
Detail: 144.6.109.151: Fetching https://thompsonhouse.duckdns.org:1078/.well-known/acme-challenge/RskaVjZDlHbkN1EIqBmPP5CWSjmnhH-UFX4k5xjT0HU: Invalid port in redirect target. Only ports 80 and 443 are supported, not 1078

Hint: The Certificate Authority failed to download the challenge files from the temporary standalone webserver started by Certbot on port 80. Ensure that the listed domains point to this machine and that it can accept inbound connections from the internet.

Some challenges have failed.
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

[Rip]

@macnet1

thompsonhouse.duckdns.org

Hi @macnet1
There seems to be some issues here.
The certificate being served is for:
Common Name: tplinkwifi.net
You are using the wrong cert.

 thompsonhouse.duckdns.org
A records for  thompsonhouse.duckdns.org: Domain does not exist
AAAA records for  thompsonhouse.duckdns.org: Domain does not exist
MX records for  thompsonhouse.duckdns.org: Domain does not exist
NS records for  thompsonhouse.duckdns.org: Domain does not exist
CNAME records for  thompsonhouse.duckdns.org: Domain does not exist
TXT records for  thompsonhouse.duckdns.org: Domain does not exist
SOA records for  thompsonhouse.duckdns.org: Domain does not exist

I don't get it...

host thompsonhouse.duckdns.org
thompsonhouse.duckdns.org has address 144.6.109.151
thompsonhouse.duckdns.org has IPv6 address 2002:9006:6d97:1:42ae:30ff:fef6:c018
thompsonhouse.duckdns.org mail is handled by 50 thompsonhouse.duckdns.org.

Nslookup shows:

nslookup thompsonhouse.duckdns.org
Server:         127.0.0.53
Address:        127.0.0.53#53

Non-authoritative answer:
Name:   thompsonhouse.duckdns.org
Address: 144.6.109.151
Name:   thompsonhouse.duckdns.org
Address: 2002:9006:6d97:1:42ae:30ff:fef6:c018

But crt.sh shows you have obtained certs recently:

crt.sh | 13275935750

Letsdebug shows a serious issue:

Test result for thompsonhouse.duckdns.org: Fatal

So I am actually not sure how to take the "bullet out of your foot" here.
no offence intended
Some Volunteer here may show you and me what is happening here. I am not even sure what questions I should be asking for clarification.
But your ports are suspect:

PORT    STATE    SERVICE
22/tcp  filtered ssh
80/tcp  open     http
443/tcp closed   https

I think I'll wat for someone smarter than me to contribute to this thread..

And what is going on here with your redirect? ::
Location: https://thompsonhouse.duckdns.org:1078/
Please Advise.

https://wheregoes.com/trace/20242973685/

[webprofusion]

I'd guess that your router is currently not forwarding https (tcp port 443) all the way through to your Home Assistant server which would be why it's serving it's own certificate.

If you want to serve publicly then you need to use your public IP in DNS but personally I prefer using Tailscale with Home Assistant then if I'm away I can run tailscale on my phone to connect.