I don’t understand what’s happening right now, before it was working, but now I can issue as many certificates as I want, webmail.support-e-mail.com keep showing as http and https doesn’t work, and when I analyse that with internet tools it says certificate mismatch for cpanel url.
Up to 5 certificates can be issued per exact same set of hostnames every 7 days.
Wait 7 days till you can issue a certificate for the same set of domains (mail.support-e-mail.com and webmail.support-e-mail.com). I don’t know what you did but you issued 5 certificates in 45 minutes for the same set of domains.
One thing I can totally say: I didn’t touched anything
1 :
Could not open file or uri for loading certificate from /usr/local/hestia/data/users/me/ssl/mail.support-e-mail.com.crt
40070BD0007F0000:error:16000069:STORE routines:ossl_store_get0_loader_int:unregistered scheme:../crypto/store/store_register.c:237:scheme=file
40070BD0007F0000:error:80000002:system library:file_open:No such file or directory:../providers/implementations/storemgmt/file_store.c:267:calling stat(/usr/local/hestia/data/users/me/ssl/mail.support-e-mail.com.crt)
Unable to load certificate
2 :
Could not open file or uri for loading certificate from /home/me/conf/mail/support-e-mail.com/ssl/support-e-mail.com.crt
40876C43997F0000:error:16000069:STORE routines:ossl_store_get0_loader_int:unregistered scheme:../crypto/store/store_register.c:237:scheme=file
40876C43997F0000:error:80000002:system library:file_open:No such file or directory:../providers/implementations/storemgmt/file_store.c:267:calling stat(/home/me/conf/mail/support-e-mail.com/ssl/support-e-mail.com.crt)
Unable to load certificate
It will depend on how the mail server sending you emails is configured. Most should have no issue using port 25 without TLS, but some will try to send them via TLS, and in this case, it will depend on whether they accept the certificate announced by your mail server (which is not the one for the domain they are sending to).
You could issue a new certificate if you add a new subdomain to that certificate, webmail.support-e-mail.com, mail.support-e-mail.com and for example botefa.support-e-mail.com. The problem is that you can’t do that using Hestia, you should try a third party acme client and once you get the certificate, add it to your mail domain in Hestia.
Waow thank you so much for all these informations, I understand a bit better now, is gmail.com going to have issues with that you think?
Otherwise I just issued a certificate with cloudflare, it seems to have worked, but I’m not that technical and I’m wondering if will cause issues using cloudflare certificate?
I don’t know, but that’s easy to test, just send a mail from gmail to your domain and you will know the answer.
Which one? Trusted certificates are only “valid” if you are using Cloudflare as a proxy (which you can’t, at least for the mail subdomain, because Cloudflare doesn’t proxy mail ports). If you issued a Cloudflare Origin Certificate, those certificates are valid but only trusted by Cloudflare, so you’ll face the same issues as if you had issued a self-signed certificate.
Argh, yes I issued a cloudflare origin certificate, I guess I’ll just have to wait then
Anyway if I miss e-mails it should be in /var/log/exim4 in either main.log or reject.log?
Actually I have nothign special excepted some things I don’t understand like:
2025-02-26 02:53:44 no host name found for IP address 195.211.191.25
2025-02-26 02:54:21 no host name found for IP address 194.187.176.44
2025-02-26 02:57:27 no host name found for IP address 60.211.206.17
2025-02-26 03:02:12 no host name found for IP address 195.211.191.25