Closed grandeljay closed 3 years ago
It seems that your system has an outdated root certificate. Just use the internal rendering engine.
@silas229 I think so. @grandeljay your certificate on your server may be outdated or bad. You need to check it. Closing since this is not a bug.
I know is very old (and closed) but for anyone getting here from a search…
For about the last 24 hours the MJML API has a cert problem again. This can be seen on a fully-upgrade Debian Bookworm system, with ca-certificates reinstalled and so on.
One work-around would be to add CURLOPT_SSL_VERIFYPEER => false
and CURLOPT_SSL_VERIFYHOST => false
to src/Http/CurlApi.php
but for obvious reasons, it's not ideal.
Another option is to get Let's Encrypt's R3 cert:
curl -o /usr/local/share/ca-certificates/lets-encrypt-r3.pem https://letsencrypt.org/certs/lets-encrypt-r3.pem
ln -s /usr/local/share/ca-certificates/lets-encrypt-r3.pem /etc/ssl/certs/
update-ca-certificates
and update src/Http/CurlApi.php
around line 53-ish:
...
$response = $this->curl->request($this->apiEndpoint . '/render', [
CURLOPT_CAINFO => '/etc/ssl/certs/lets-encrypt-r3.pem',
CURLOPT_RETURNTRANSFER => true,
...
Hopefully, this helps someone else. I'm probably going the route of self-hosting the API in the near future.
As the title mentions, rendering MJML doesn't seem to work anymore and I get this error. It stopped working on my live site too, so I can't help but wonder if recent core and plugin updates may be related to this.
Any help would be greatly appreciated!