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:
Letsdebug shows a serious issue:
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.