Title: Fatal error again
Last modified: June 21, 2019

---

# Fatal error again

 *  Resolved [Carin](https://wordpress.org/support/users/sparksfreebies/)
 * (@sparksfreebies)
 * [6 years, 11 months ago](https://wordpress.org/support/topic/fatal-error-again-6/)
 * I have deactivated the plugin, we just fixed an error a couple of weeks ago with
   IP addresses whitelisted, now we have this error
    An error of type E_ERROR was
   caused in line 89 of the file /home/nsjdslok/public_html/wp-content/plugins/constant-
   contact-formsOLD/vendor/guzzlehttp/guzzle/src/Exception/RequestException.php.
   Error message: Uncaught GuzzleHttp\Exception\ServerException: Server error response[
   url] [https://api.constantcontact.com/v2/lists?api_key=kawd2utg75a4aa7dgvvqzgjh](https://api.constantcontact.com/v2/lists?api_key=kawd2utg75a4aa7dgvvqzgjh)[
   status code] 504 [reason phrase] Gateway Timeout in /home/nsjdslok/public_html/
   wp-content/plugins/constant-contact-formsOLD/vendor/guzzlehttp/guzzle/src/Exception/
   RequestException.php:89 Stack trace: #0 /home/nsjdslok/public_html/wp-content/
   plugins/constant-contact-formsOLD/vendor/guzzlehttp/guzzle/src/Subscriber/HttpError.
   php(32): GuzzleHttp\Exception\RequestException::create(Object(GuzzleHttp\Message\
   Request), Object(GuzzleHttp\Message\Response)) #1 /home/nsjdslok/public_html/
   wp-content/plugins/constant-contact-formsOLD/vendor/guzzlehttp/guzzle/src/Event/
   Emitter.php(108): GuzzleHttp\Subscriber\HttpError->onComplete(Object(GuzzleHttp\
   Event\CompleteEvent), ‘complete’) #2 /home/nsjdslok/public_html/wp-content/plugins/
   constant-contact-formsOLD/vendor/guzzlehttp/guzzle/src/RequestFsm.php(91): GuzzleHttp\
   Event\Emitter->emit(‘complete’, Object(GuzzleHttp\Event\Comple
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Ffatal-error-again-6%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

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

 *  Thread Starter [Carin](https://wordpress.org/support/users/sparksfreebies/)
 * (@sparksfreebies)
 * [6 years, 11 months ago](https://wordpress.org/support/topic/fatal-error-again-6/#post-11660206)
 * I just realized the plugin had been renamed on the last break with OLD on the
   end of folder name , but somehow I was able to activate it even with the OLD 
   on folder name (and it never got removed) , I just went in through file manage
   and removed the OLD, do you think that was the problem?
 *  Plugin Author [Constant Contact](https://wordpress.org/support/users/constantcontact/)
 * (@constantcontact)
 * [6 years, 10 months ago](https://wordpress.org/support/topic/fatal-error-again-6/#post-11660538)
 * Good morning [@sparksfreebies](https://wordpress.org/support/users/sparksfreebies/)
 * The folder name shouldn’t make any difference for functionality of the plugin.
 * Is the error still happening, or did that part resolve itself?
 *  Plugin Author [Constant Contact](https://wordpress.org/support/users/constantcontact/)
 * (@constantcontact)
 * [6 years, 10 months ago](https://wordpress.org/support/topic/fatal-error-again-6/#post-11694979)
 * Any news or changes here Carin?
 *  Thread Starter [Carin](https://wordpress.org/support/users/sparksfreebies/)
 * (@sparksfreebies)
 * [6 years, 10 months ago](https://wordpress.org/support/topic/fatal-error-again-6/#post-11707949)
 * Hi thanks for asking! I have not reactivated the plugin yet because owner was
   collecting signups for a retreat, I will do so soon, but with the error above,
   did you see anything important I should be aware of?
 *  Plugin Author [Constant Contact](https://wordpress.org/support/users/constantcontact/)
 * (@constantcontact)
 * [6 years, 10 months ago](https://wordpress.org/support/topic/fatal-error-again-6/#post-11710996)
 * The biggest thing going with the error is that it simply timed out trying to 
   connect from your hosting server to our Constant Contact servers.
 * Will need to be re-tested when you’re able to, after the retreat signup window
   has closed. However, there’s not going to be much we can do from the standpoint
   of our plugin’s code to resolve that part. What we would be able to do, and are
   aiming to with 1.6.0, is better handling of errors like this where we at least
   don’t take the entirety of the website down.
 *  [contemplate](https://wordpress.org/support/users/contemplate/)
 * (@contemplate)
 * [6 years, 10 months ago](https://wordpress.org/support/topic/fatal-error-again-6/#post-11718836)
 * We are having the same issue and it takes down our site when people try to register
   for an account:
 * [10-Jul-2019 15:31:38 UTC] PHP Fatal error: Uncaught TypeError: Argument 3 passed
   to GuzzleHttp\Client::request() must be of the type array, string given, called
   in /home/leoadventures/public_html/wp-content/plugins/backwpup/vendor/guzzlehttp/
   guzzle/src/Client.php on line 89 and defined in /home/leoadventures/public_html/
   wp-content/plugins/backwpup/vendor/guzzlehttp/guzzle/src/Client.php:128
    Stack
   trace: #0 /home/leoadventures/public_html/wp-content/plugins/backwpup/vendor/
   guzzlehttp/guzzle/src/Client.php(89): GuzzleHttp\Client->request(‘createRequest’,‘
   GET’, ‘[https://api.con…&#8217](https://api.con…&#8217);) #1 /home/leoadventures/
   public_html/wp-content/plugins/constant-contact-forms/vendor/constantcontact/
   constantcontact/src/Ctct/Services/BaseService.php(65): GuzzleHttp\Client->__call(‘
   createRequest’, Array) #2 /home/leoadventures/public_html/wp-content/plugins/
   constant-contact-forms/vendor/constantcontact/constantcontact/src/Ctct/Services/
   ContactService.php(36): Ctct\Services\BaseService->createBaseRequest(‘c8fdb5dd-
   634f-4…’, ‘GET’, ‘[https://api.con…&#8217](https://api.con…&#8217);) #3 /home/
   leoadventur in /home/leoadventures/public_html/wp-content/plugins/backwpup/vendor/
   guzzlehttp/guzzle/src/Client.php on line 128
 *  [contemplate](https://wordpress.org/support/users/contemplate/)
 * (@contemplate)
 * [6 years, 10 months ago](https://wordpress.org/support/topic/fatal-error-again-6/#post-11718857)
 * Ok actually it looks like the issue is your plugin conflicts with the new version
   of BackWPup
 *  Plugin Author [Constant Contact](https://wordpress.org/support/users/constantcontact/)
 * (@constantcontact)
 * [6 years, 10 months ago](https://wordpress.org/support/topic/fatal-error-again-6/#post-11719127)
 * [@contemplate](https://wordpress.org/support/users/contemplate/) yours is similar
   in that there are errors occurring, but the source of your errors are different
   than that of Carin’s
 * Ultimately, both BackWPup and our plugin are both using a library named Guzzle,
   but they’re on different versions. Ours is very likely the older one because 
   we’re still technically supporting some older versions of PHP that necessitate
   the older Guzzle.
 * The issue is that BackWPup starts its work, but due to things in the proverbial
   backend, our copy is getting found and loaded first. At that point is when the
   conflict comes into play. We sadly don’t have a solution for this readily available,
   but we are looking into bumping our minimum supported PHP that would allow us
   to consequently upgrade our Guzzle as well. It’s our hope that at that point,
   errors like yours and some other peoples’ will go away.
 *  [contemplate](https://wordpress.org/support/users/contemplate/)
 * (@contemplate)
 * [6 years, 10 months ago](https://wordpress.org/support/topic/fatal-error-again-6/#post-11719204)
 * Is there any possibility to add a check first if the Guzzle library exists elsewhere
   OR if the backWPup plugin is installed to not load your library?
 * We had to disable the backwpup plugin to stop our site from crashing.
 *  Plugin Author [Constant Contact](https://wordpress.org/support/users/constantcontact/)
 * (@constantcontact)
 * [6 years, 10 months ago](https://wordpress.org/support/topic/fatal-error-again-6/#post-11719538)
 * We wish it were as easy as that, but the two still need to use their own and 
   there’s no great way to direct them to the right spots, even with checks for 
   existing loaded libraries.

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

The topic ‘Fatal error again’ is closed to new replies.

 * ![](https://ps.w.org/constant-contact-forms/assets/icon-256x256.png?rev=2951825)
 * [Constant Contact Forms](https://wordpress.org/plugins/constant-contact-forms/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/constant-contact-forms/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/constant-contact-forms/)
 * [Active Topics](https://wordpress.org/support/plugin/constant-contact-forms/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/constant-contact-forms/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/constant-contact-forms/reviews/)

 * 10 replies
 * 3 participants
 * Last reply from: [Constant Contact](https://wordpress.org/support/users/constantcontact/)
 * Last activity: [6 years, 10 months ago](https://wordpress.org/support/topic/fatal-error-again-6/#post-11719538)
 * Status: resolved