this post was submitted on 09 Jul 2024
10 points (100.0% liked)
Mastodon
4849 readers
3 users here now
Decentralised and open source social network.
founded 4 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Sounds like the cert is missing a required SAN name. I used namecheap and Let's Encrypt together before. I had to ensure that
*.ziviz.us
andziviz.us
were both provided to certbot. I used manual DNS challenges, and it looked like this:What if I told you that the cert says the SAN is valid for the Synology DDNS but not the SAN that I entered (domain.tld)
If you ensured both the subdomain and the domain name were provided when using certbot, then it could be a case where the server is still using a previous cert. I had issues where changing the cert in NameCheap did not immediately take affect. (In the NameCheap CPanel console, cert would be fine, but actually visiting the site would still present the old cert for a while.) There were at least a couple times where it only presented the new cert after I fully removed the old one from Cpanel. Other than that, running out of ideas.