This is the part that stands out the most to me: “certificate has expired”. Not really a topic we’re going to be able to control from the plugin side. I’m curious if cURL is trying to use a different certificate or if the intended one is having some issues.
That is what I thought also, we just installed the certificate yesterday, and the SSL check I run show that it won’t expire for at least a year.
Something to note is that we don’t use cURL directly in the plugin, we use WordPress’ HTTP API for the calls it makes. Internal to that is what ends up choosing cURL as the “best option”.
As an idea to help with this, contacting your hosting support or any sort of available system admin may help track down the source of the expired certificate being used here.
Our hosting support did not find any expired certificates. Not sure what to try now.
Have tried changing the php.ini file to look for the cacert.pen file as suggested by another thread. Unfortunately that did not work, have also tried point to different other certificates.
Let me check with a couple things, and I’ll get back to you.
Hey @jlatham can you provide us exactly when you’re receiving these errors? For example immediately after connecting? Certain area of the settings for the plugin? When creating a form?
We are able to install the plugin with no issues. We are also able to “connect” our account with now issues.
After we connect the account and click on “Settings”,”Add New Form”, and “Lists” we see the error.
Passed this information on to some other people in our support team.
I do know that the plugin uses Constant Contact’s PHP SDK, and in turn that library uses Guzzle for HTTP calls. Internally, one person has brought up that they had similar Guzzle errors in their local environment and it was related to certificate problems in their server paths.
A slight stretch, but I have had someone internally chime in with that they once or twice saw some issues when there was any sort of signup plugins for anything, not necessarily just a signup for Constant Contact. Can you think of anything like that with the site in question?
Other than that, my thoughts are ending up circling back that somewhere on the site’s server and through the overall process here, an expired certificate is ending up getting used.
Any changes or updates on this front @jlatham Hopefully a solution was found.
