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
Adding even more grammar, you could use “Had no”, for lack of possession, like
It had no tooling for the fs?
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.
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.
Yeah, I guess. It seems wasteful to need 8GB just to run an OS and browser especially after Microsoft was pushing server core specifically to go the opposite route with resource utilization on servers.
They are necessitating 8GB of RAM. for what?! Like, it would be a struggle to find a machine with less than 8GB still being sold new, sure, but why does the OS need that RAM?
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.