Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
No, you're not. Let's Encrypt certificates are valid for just 90 days, so could never have an expiry date in 2026. It's the self-signed certificate you're seeing there, which indeed has the exact same expiration date: "Sep 14 03:59:57 2026 GMT".
I'm not sure about the expiration time of Let's encrypt certificates. Creating a certificate from Let's encrypt in MDaemon server is used by clicking Create certificate and then clicking Restart servers as shown in the picture I just sent.
But we are, and they are only valid for 90 days. Therefore, any cert expiring in 2026 could not have come from Let's Encrypt. Either you didn't follow the instructions correctly, or issuance of the cert failed. The instructions tell you that:
There will be a LetsEncrypt.log file generated in the \MDaemon\Logs (default location) directory.
Have you checked that log file to see what happened?
btw do you know what handles lighttpd? not sure if that's even on same server: I don't think Mdeamon can use http-01 when it's sitting no server: and its version is too old to be installed from Mdaemon
It seems that the "create certificate" button for "MDaemon" creates a self-signed cert.
Without having read the instructions...
[I like (not) to do that sometimes]
I would "delete" that self-signed cert and use the options in "Let's Encrypt" ONLY.
[then if that doesn't work... I might try the instructions OR a search engine]