Something not quite right with my let's encrypt

[boe1]

my config.json is:
{
"settings": {
"cert": "support.mydomain.com",
"_minify": true,
"port": 443,
"redirectPort": 80

},
"letsencrypt": {
"email": "[email protected]",
"names": "support.mydomain.com",
"production": false
}
}

I went ahead to the console and did a resetserver.
The page reloads - I still get the certificate error and if I look at the cert I get

Common Name (CN) support.mydomain.com
Organization (O)
Organizational Unit (OU)
Common Name (CN) MeshCentralRoot-46785f
Organization (O) unknown
Organizational Unit (OU)
Issued On Monday, January 1, 2018 at 12:00:00 AM
Expires On Friday, December 31, 2049 at 12:00:00 AM

So it looks like letsencrypt isn't giving it a cert

I am able to get to support.mydomain.com on both via http: and https: externally - I just get the cert error and the cert isn't from letsencrypt.

[boe1]

I found this in my mesherrors but no idea what it means

------- 3/5/2023, 7:47:19 PM ---- 1.1.4 --------

(node:7256) UnhandledPromiseRejectionWarning: Error: EPERM: operation not permitted, open 'C:\Program Files\Open Source\MeshCentral\meshcentral-data\letsencrypt-certs\staging.crt'
at Object.openSync (fs.js:458:3)
at Object.writeFileSync (fs.js:1283:35)
at C:\Program Files\Open Source\MeshCentral\node_modules\meshcentral\letsencrypt.js:198:28
at processTicksAndRejections (internal/process/task_queues.js:97:5)
(node:7256) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:7256) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.