Title: [Plugin: Constant Contact for WordPress] Fatal Protocol Error when activating plugin
Last modified: August 19, 2016

---

# [Plugin: Constant Contact for WordPress] Fatal Protocol Error when activating plugin

 *  [kims126](https://wordpress.org/support/users/kims126/)
 * (@kims126)
 * [15 years, 9 months ago](https://wordpress.org/support/topic/plugin-constant-contact-for-wordpress-fatal-protocol-error-when-activating-plugin/)
 * Hi. I’ve tried installing this plugin several times and I keep getting the following:
 *     ```
       Warning: fgets() [function.fgets]: SSL: fatal protocol error in /nfs/c04/h02/mnt/62344/domains/trainwithshane.com/html/wp-content/plugins/constant-contact-api/class.cc.php on line 1913
   
       Warning: Cannot modify header information - headers already sent by (output started at /nfs/c04/h02/mnt/62344/domains/trainwithshane.com/html/wp-content/plugins/constant-contact-api/class.cc.php:1913) in /nfs/c04/h02/mnt/62344/domains/trainwithshane.com/html/wp-includes/pluggable.php on line 890
       ```
   
 * Any ideas?

Viewing 5 replies - 1 through 5 (of 5 total)

 *  Plugin Author [Zack Katz](https://wordpress.org/support/users/katzwebdesign/)
 * (@katzwebdesign)
 * [15 years, 9 months ago](https://wordpress.org/support/topic/plugin-constant-contact-for-wordpress-fatal-protocol-error-when-activating-plugin/#post-1674713)
 * Are you on a Windows server running PHP? You should ask your hosting company.
 * Apparently it’s caused by Windows servers ([http://bugs.php.net/23220](http://bugs.php.net/23220))
 *  Thread Starter [kims126](https://wordpress.org/support/users/kims126/)
 * (@kims126)
 * [15 years, 9 months ago](https://wordpress.org/support/topic/plugin-constant-contact-for-wordpress-fatal-protocol-error-when-activating-plugin/#post-1674727)
 * No, it’s not Windows, it’s Linux. What version of PHP does it require? Perhaps
   that may be the issue.
 *  Plugin Author [Zack Katz](https://wordpress.org/support/users/katzwebdesign/)
 * (@katzwebdesign)
 * [15 years, 9 months ago](https://wordpress.org/support/topic/plugin-constant-contact-for-wordpress-fatal-protocol-error-when-activating-plugin/#post-1674729)
 * It requires PHP 5. Do you run 5?
 *  Thread Starter [kims126](https://wordpress.org/support/users/kims126/)
 * (@kims126)
 * [15 years, 9 months ago](https://wordpress.org/support/topic/plugin-constant-contact-for-wordpress-fatal-protocol-error-when-activating-plugin/#post-1674732)
 * I think that was it. I checked my settings and I had it set to 4 instead of 5.
   Going to try it now. Thanks!
 *  [Jer Clarke](https://wordpress.org/support/users/jeremyclarke/)
 * (@jeremyclarke)
 * [15 years, 8 months ago](https://wordpress.org/support/topic/plugin-constant-contact-for-wordpress-fatal-protocol-error-when-activating-plugin/#post-1674961)
 * Zack: If PHP4 causes an error like that maybe there should be a displayed message
   on the settings page if people are running PHP4, something big and red (.error)
   saying that authentication won’t work.

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘[Plugin: Constant Contact for WordPress] Fatal Protocol Error when activating
plugin’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/constant-contact-api_f6e5e6.svg)
 * [Constant Contact for WordPress](https://wordpress.org/plugins/constant-contact-api/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/constant-contact-api/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/constant-contact-api/)
 * [Active Topics](https://wordpress.org/support/plugin/constant-contact-api/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/constant-contact-api/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/constant-contact-api/reviews/)

 * 5 replies
 * 3 participants
 * Last reply from: [Jer Clarke](https://wordpress.org/support/users/jeremyclarke/)
 * Last activity: [15 years, 8 months ago](https://wordpress.org/support/topic/plugin-constant-contact-for-wordpress-fatal-protocol-error-when-activating-plugin/#post-1674961)
 * Status: not resolved