Trouble Installing Packages on Local Dev

I think I’m just missing something here, so I’m not submitting this as an issue as of yet: At some point on my local dev copies (3.0.0-alpha3 specifically) I lost the ability to install or update packages. I’m getting this curl ssl error in the modx logs:

[2021-10-19 22:10:16] (ERROR @ [...]/GIT-Projects/revolution/core/vendor/
guzzlehttp/guzzle/src/Handler/CurlFactory.php : 211) 
GuzzleHttp\Exception\RequestException sending GET package for provider cURL error 60: SSL certificate problem: certificate has expired 
(see for

Note that all else works as expected in the manager and on the front end, all on https. I’m running MAMP on macos and believe I remember not having this problem a month or so ago. Has anyone had this issue? Thanks for any clues you can give… :wink:

It looks like the SSL certificate at has expired.

You can set CURLOPT_SSL_VERIFYHOST=false in the code (if you can find the place to do it), but it makes your site less secure. It’s probably best to report it as a bug here and wait for a fix at

Yes, that’s what I would have thought. However, a non-local installation of the 3.0.0-alpha3 (packaged) release I installed back in June is working fine.

Now, interestingly, I just tried the most simple thing on my local dev install — changed the provider to (instead of https://…) — and it works fine. Note that my external install mentioned above does successfully connect with https.

Could it have something to do with using LetsEncrypt for its cert? Maybe guzzle/curl doesn’t like that. As I’m sure you know normally you have to explicitly trust LE certs. That it behaves differently local vs external is baffling me.

The SSL certificates at are certainly not expired. I’m viewing the main site and the rest subdomain and not seeing any issue with the certificates.

Can you try updating mamp? Someone else had a similar issue with accessing the modmore provider last week, which was solved by an update. That came with a new version of curl and openssl that resolved the problem IIRC

1 Like

Actually, it looks like the certificate chain needed to be updated on a few of our certs in order for them to work in some environments. Should be good now.

@markh @opengeek - Yes, that did the trick. Thank you so much for pointing me in the right direction!

1 Like