the full domain name of your site (this will be made [public]((https://www.certificate-transparency.org/) upon issuance anyhow)
the command line you ran
the output of that command
name and version of your operating system and your web server
Ubuntu 18.04.6 LTS
what type of hosting provider you are using, if applicable
Amazon Lightsail VPS, domain & DNS with Amazon Route 53
I can login to a root shell on my machine (yes or no, or I don't know):
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
Yes, Plesk Obsidian v18.0.48
The version of my client is (e.g. output of
certbot-auto --versionif you're using Certbot):
Plesk Let's Encrypt Extension 3.1.2-823
Plesk SSL It! Extension 1.11.2-1547
I'm definately at the bottom of the learing curve, so I'd like some advice regarding a wildcard certificate that doesn't work for one of my subdomains. Maybe worth adding that this is just a personal site that I'm learning with - nothing at all critical
I secured my domain with a 'normal' Let's Encrypt domain a while ago (>1 year). I replaced this with a wildcard SSL Cert via LetsEncrypt at the start of December. It's working fine for my main domain, and also for the typical "webmail.domain.tld" subdomains. However, for one particular subdomain it isn't working. Since then I've tried a few things to fix, and then asked Plesk to "Reissue Certificate". This hasn't solved by problem.
What is particularly strange (to me at least) is that when I access my main domain, my browser is showing the dates related to the most recent certificate. That also applies for my other subdomains. But when I look at my problematic subdomain, my browser is retrieving the original (borked) certificate from early December.
Why would this subdomain hang on to the old certificate? Can I force it to be revoked and use the latest certificate? Or am I asking all the wrong questions?
Thanks in advance!