“Fatal error: message ‘cURL error 7: Failed to connect to api.constantcontact.co

Good day @aardvarkgirl

Basically at the moment, for whatever reason, the plugin was not able to successfully connect and communicate with the Constant Contact API server before timing out.

While this answer/example below references Twitter’s api, the sentiment will be the same with Constant Contact’s

“The error Failed to connect to api.twitter.com port 443: Connection refused generally means that your server can’t connect to api.twitter.com. Sometimes that’s caused by a firewall blocking connections, sometimes that’s caused by your IP being blocked by Twitter, sometimes there is an ISP between your server and Twitter that is broken.”

Borrowed from https://github.com/abraham/twitteroauth/issues/517

May offer some suggestions and ideas to check in with.

Thank you for your reply.

I contacted my hosting provider, InMotion, and they stated since the end of the error said “Warning: Error while sending QUERY packet. PID=4175194 in /home/ACCOUNTHERE/public_html/wp-includes/wp-db.php on line 1924” that I needed to optimize the database to fix that query and it should fix the issue.

I backed up everything and I installed the plugin they suggested, WP Optimize, and while it removed the WARNING at the end, the error is still there:

Fatal error: Uncaught exception ‘GuzzleHttp\Ring\Exception\ConnectException’ with message ‘cURL error 7: Failed to connect to api.constantcontact.com port 443: Connection timed out’ in /home/angierbaptistchu/public_html/wp-content/plugins/constant-contact-forms/vendor/constantcontact/guzzlehttp/ringphp/src/Client/CurlFactory.php:126 Stack trace: #0 /home/angierbaptistchu/public_html/wp-content/plugins/constant-contact-forms/vendor/constantcontact/guzzlehttp/ringphp/src/Client/CurlFactory.php(91): GuzzleHttp\Ring\Client\CurlFactory::createErrorResponse(Array, Array, Array) #1 /home/angierbaptistchu/public_html/wp-content/plugins/constant-contact-forms/vendor/constantcontact/guzzlehttp/ringphp/src/Client/CurlHandler.php(96): GuzzleHttp\Ring\Client\CurlFactory::createResponse(Array, Array, Array, Array, Resource id #494) #2 /home/angierbaptistchu/public_html/wp-content/plugins/constant-contact-forms/vendor/constantcontact/guzzlehttp/ringphp/src/Client/CurlHandler.php(68): GuzzleHttp\Ring\Client\CurlHandler->_invokeAsArray(Ar in /home/angierbaptistchu/public_html/wp-content/plugins/constant-contact-forms/vendor/constantcontact/guzzlehttp/guzzle/src/Exception/RequestException.php on line 49

Should I be able to ping api.constantcontact.com? I can ping api.twitter.com and get replies, but api.constantcontact.com times out for me, regardless of what computer and network I’m on.

Thank you.

The warning from the QUERY packet feels like it’s unrelated to the actual issue at hand, but we won’t rule it out completely.

Regarding the pinging, out of curiosity, what method are you using to test this?

Unresponsiveness for the endpoint is very likely going to fall out of scope for being an issue with the plugin itself, and more an issue on the other end of the line. The plugin is doing what it can, but without a result to work with, it simply can’t continue.

To see if we can recreate on our own installs, what actions are you taking here? Just trying to connect your Constant Contact account to your WP install?

@aardvarkgirl Did you ever find resolution for this error? or is it still showing up for you?

I’m getting what looks like the same error:

Fatal error: Uncaught GuzzleHttp\Ring\Exception\ConnectException: cURL error 7: Failed to connect to api.constantcontact.com port 443: Connection timed out in /home/girard9/public_html/wp-content/plugins/constant-contact-forms/vendor/constantcontact/guzzlehttp/ringphp/src/Client/CurlFactory.php:126 Stack trace: #0 /home/girard9/public_html/wp-content/plugins/constant-contact-forms/vendor/constantcontact/guzzlehttp/ringphp/src/Client/CurlFactory.php(91): GuzzleHttp\Ring\Client\CurlFactory::createErrorResponse(Array, Array, Array) #1 /home/girard9/public_html/wp-content/plugins/constant-contact-forms/vendor/constantcontact/guzzlehttp/ringphp/src/Client/CurlHandler.php(96): GuzzleHttp\Ring\Client\CurlFactory::createResponse(Array, Array, Array, Array, Resource id #749) #2 /home/girard9/public_html/wp-content/plugins/constant-contact-forms/vendor/constantcontact/guzzlehttp/ringphp/src/Client/CurlHandler.php(68): GuzzleHttp\Ring\Client\CurlHandler->_invokeAsArray(Array) #3 /home/girard9/public_html/wp-content/plugins/constant- in /home/girard9/public_html/wp-content/plugins/constant-contact-forms/vendor/constantcontact/guzzlehttp/guzzle/src/Exception/RequestException.php on line 49

I contacted my hosting provider (also InMotion), who stated a direct CURL to the api.constantcontact.com URL comes back with a 596 error, so it is an issue with that server.

This error shows up on the front end wherever the plugin is called, and also in the dashboard, I’m unable to view any of the plugin pages.

Any other ideas of things to try?

Is this before or after you tried to connect your account? Just in case, are you able to trigger a disconnect for the account to get things back to mostly normal so the site still functions?

If necessary, would you be willing to contact us away from the forums so we could debug things privately?

After the account was connected. I did try disconnecting, which still throws the same error. When reconnecting the account I get the following error:

Warning: array_key_exists() expects parameter 2 to be array, string given in /home/girard9/public_html/wp-content/plugins/constant-contact-forms/includes/class-settings.php on line 850

Warning: Cannot modify header information – headers already sent by (output started at /home/girard9/public_html/wp-content/plugins/constant-contact-forms/includes/class-settings.php:850) in /home/girard9/public_html/wp-includes/pluggable.php on line 1219

It still seems to connect the account, but still produces the errors above.

I’d be willing to contact away from the forums.

That second error is set to be addressed in the next version of the plugin, and we can help hotfix it in the meantime as well.

Please contact [email protected] and CC [email protected] and we’ll see what we can do soon.

I am getting this error message too. Also with the second warning message and I am with in inmotion hosting too:

The error that we saw on your page is:
Fatal error: Uncaught GuzzleHttp\Ring\Exception\ConnectException: cURL error 7: Failed to connect to api.constantcontact.com port 443: Connection timed out in /home/kalypsowellness/public_html/wp-content/plugins/constant-contact-forms/vendor/constantcontact/guzzlehttp/ringphp/src/Client/CurlFactory.php:126 Stack trace: #0 /home/kalypsowellness/public_html/wp-content/plugins/constant-contact-forms/vendor/constantcontact/guzzlehttp/ringphp/src/Client/CurlFactory.php(91): GuzzleHttp\Ring\Client\CurlFactory::createErrorResponse(Array, Array, Array) #1 /home/kalypsowellness/public_html/wp-content/plugins/constant-contact-forms/vendor/constantcontact/guzzlehttp/ringphp/src/Client/CurlHandler.php(96): GuzzleHttp\Ring\Client\CurlFactory::createResponse(Array, Array, Array, Array, Resource id #1086) #2 /home/kalypsowellness/public_html/wp-content/plugins/constant-contact-forms/vendor/constantcontact/guzzlehttp/ringphp/src/Client/CurlHandler.php(68): GuzzleHttp\Ring\Client\CurlHandler->_invokeAsArray(Array) #3 /home/kalypsowellness in /home/kalypsowellness/public_html/wp-content/plugins/constant-contact-forms/vendor/constantcontact/guzzlehttp/guzzle/src/Exception/RequestException.php on line 49
Warning: Error while sending QUERY packet. PID=1205 in /home/kalypsowellness/public_html/wp-includes/wp-db.php on line 1924

Good day @ezradallas

Based on the error provided, the site/server you’re using the plugin on is having trouble connecting to the api.constantcontact.com site. This problem could be stemming from either side of this process. If at all possible, can you check with your hosting support to see if they can find anything that would be preventing successful connection from your side? We haven’t had many reports that I’ve been made aware of for issues on our end, but please note I’m not ruling that possibility out completely.

It could be something like a security firewall or some sort of blacklisting preventing the connection from succeeding.

Thank you. I will check