I created the CNAME in my Domain hosting account and ensured they were pointing back to my public IP using a Wildcard.
I updated the Letsencrypt docker in UnRaid to match the CNAMEs created and can confirm that the docker is return a Server Ready result, indicating that the Sub-domains have been configured correctly and working.
I updated the config files for Sonarr and Radarr to again match the CNAMEs, but every time I try to visit the site page, it redirects me to my modem login page not the webpage for Sonarr or Radarr as expected.
Your third A record is pointless, it applies to the fourth level domain matchett-tech.com.matchett-tech.com
Your CNAMEs are also pointless, your second A record does the same thing more efficiently (one less dns query).
(You can probably find a more efficient way to write the second A record, @ as IP? or move to an ANAME record to @ – see your dns docs – ANAME is similar to CNAME but only carries A and AAAA records over, not all the others, not CAA, especially.)
Please explain how else someone is meant to learn new things without try and failing at them? I am just asking for some assistance with this, no need to be condescending.
running an acme client inside a docker container is a painful process even for expert users. really. it’s an utter mess of shared volumes and more bullshit. probably acme.sh can do it in a less painful way, but it’s painful nonetheless.
I don't know how docker works. I don't know what Unraid is. Never used one of these tools / environments. This is a Letsencrypt forum. If you have trouble with one or with the combination of such solutions, please ask in a specialized forum.
And if something complex doesn't work. "Use a simpler solution" is always the better way.
Create a solution with a standard nginx. Then you can add the next step.
Your cname needs to be edited to point at the site you want. So example my.ddns.com etc or wherever. Then you configure ddns to point at your IP, then setup the client that updates your IP, but in your case that won’t be necessary since you have a static IP. One last thing the ports will need to be added. Say you wanted to have people login to your server via login like you would just add www.mysite.com:8080 for example…nobody really notices since they’re clicking a link. Second option you can port forward from your free ddns to the correct port. I hope this helps…