Hi, I’m hosting mastodon for personal use on subdomain.domain.tld — it has a valid ssl cert. The issue is that when I set the vanity server name to domain.tld (no subdomain) and create a Let’s Encrypt cert for domain.tld. The namecheap ssl cert checker says that the Hostname doesn’t match the Common Name or/and the SANs.

I have domain.tld redirect via an Alias record to my Synology server (just like the subdomain) but for some reason it’s fine on the subdomain but not for the root domain.

Any one have any experience with this? TIA.

You are viewing a single thread.
View all comments View context
1 point

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.

permalink
report
parent
reply

Mastodon

!mastodon@lemmy.ml

Create post

Decentralised and open source social network.

https://joinmastodon.org/

GitHub

Community stats

  • 100

    Monthly active users

  • 155

    Posts

  • 946

    Comments