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 and ziviz.us were both provided to certbot. I used manual DNS challenges, and it looked like this:
certbot certonly --manual --preferred-challenges dns
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Please enter the domain name(s) you would like on your certificate (comma and/or
space separated) (Enter 'c' to cancel): ziviz.us *.ziviz.us
Not an expert, but I think it's Angular Leaf Spot. It seems to match at least, damage is not passing veins, looks like the underside of the leaves have white stuff on them. It does not look like there is a cure if so though, at least, not one I have found searching the internet.
Adding even more grammar, you could use "Had no", for lack of possession, like
It had no tooling for the fs?
Definitely this. The data is not likely gone, but before doing anything that could make things worse, try and get a full copy of the SD card somewhere. From there you may safely try repairing the partition or data carving tools.
Accounting details, sensitive credentials for sys admin use, HIPAA data, PII etc. there's just so much crap understood to be temporarily unlocked, viewed, and then immediately deleted or locked again. Even home users shouldn't turn this thing on, check your bank? Balance and account details now always available. Use a password manager? Whatever you looked at is likely captured.
Probably not quite what you are thinking of, but Sakuna: Of Rice and Ruin is supposed to be pretty accurate... for rice farming specifically.
Seems right to me. I thought maybe it was fixed in the time since the comment but the cert looks like it was issued at the start of the month.
I'd imagine a berry of some sort. There could be a berry we still eat that pre-humans also ate. Wouldn't surprise me.
Ah crap, yeah, I forgot about that, you're right.
Keep in mind both options require enabling remote control from Windows settings. It's off by default if I recall right.
If you have another windows pc, you can use the built-in remote desktop. Or, from Linux you can install a Microsoft rdp compatible client like remmina. (Edit: If using Windows Pro on the target machine, for either of these options)
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.