PHP Fatal error: Uncaught Error: Call to undefined function GuzzleHttp

  • Resolved neilgee

    (@neilgee)


    2 years, 11 months ago

    Getting a critical error trying to back up db to BackBlaze

    Have used same credentials on other sites with no issues. 

    [08-Dec-2021 00:12:56 UTC] PHP Fatal error:  Uncaught Error: Call to undefined function GuzzleHttp\Psr7\uri_for() in /home/woodsbut/public_html/wp-content/plugins/backwpup/vendor/aws/aws-sdk-php/src/Api/Serializer/RestSerializer.php:35
Stack trace:
#0 /home/woodsbut/public_html/wp-content/plugins/backwpup/vendor/aws/aws-sdk-php/src/Api/Serializer/RestXmlSerializer.php(25): Aws\Api\Serializer\RestSerializer->__construct(Object(Aws\Api\Service), 'https://s3.us-w...')
#1 /home/woodsbut/public_html/wp-content/plugins/backwpup/vendor/aws/aws-sdk-php/src/Api/Service.php(90): Aws\Api\Serializer\RestXmlSerializer->__construct(Object(Aws\Api\Service), 'https://s3.us-w...')
#2 /home/woodsbut/public_html/wp-content/plugins/backwpup/vendor/aws/aws-sdk-php/src/ClientResolver.php(662): Aws\Api\Service::createSerializer(Object(Aws\Api\Service), 'https://s3.us-w...')
#3 /home/woodsbut/public_html/wp-content/plugins/backwpup/vendor/aws/aws-sdk-php/src/ClientResolver.php(276): Aws\ClientResolver::_default_serializer(Array)
#4 /home/woodsbut/public_html/wp-content/plugins in /home/woodsbut/public_html/wp-content/plugins/backwpup/vendor/aws/aws-sdk-php/src/Api/Serializer/RestSerializer.php on line 35
[08-Dec-2021 00:13:11 UTC] PHP Fatal error:  Uncaught Error: Call to undefined function GuzzleHttp\Psr7\uri_for() in /home/woodsbut/public_html/wp-content/plugins/backwpup/vendor/aws/aws-sdk-php/src/Api/Serializer/RestSerializer.php:35
Stack trace:
#0 /home/woodsbut/public_html/wp-content/plugins/backwpup/vendor/aws/aws-sdk-php/src/Api/Serializer/RestXmlSerializer.php(25): Aws\Api\Serializer\RestSerializer->__construct(Object(Aws\Api\Service), 'https://s3.us-w...')
#1 /home/woodsbut/public_html/wp-content/plugins/backwpup/vendor/aws/aws-sdk-php/src/Api/Service.php(90): Aws\Api\Serializer\RestXmlSerializer->__construct(Object(Aws\Api\Service), 'https://s3.us-w...')
#2 /home/woodsbut/public_html/wp-content/plugins/backwpup/vendor/aws/aws-sdk-php/src/ClientResolver.php(662): Aws\Api\Service::createSerializer(Object(Aws\Api\Service), 'https://s3.us-w...')
#3 /home/woodsbut/public_html/wp-content/plugins/backwpup/vendor/aws/aws-sdk-php/src/ClientResolver.php(276): Aws\ClientResolver::_default_serializer(Array)
#4 /home/woodsbut/public_html/wp-content/plugins in /home/woodsbut/public_html/wp-content/plugins/backwpup/vendor/aws/aws-sdk-php/src/Api/Serializer/RestSerializer.php on line 35
Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support Syde Niklas

    (@niklasinpsyde)

    Hi @neilgee,

    This problem is usually caused by multiple plugins loading a different version of the same dependency. In this case, GuttleHttp. So it doesn’t have to do anything with the Backblaze credentials.
    If you disable all other plugins except for BackWPup, then the backup should work.
    If you re-enable the other plugins in small batches and try again to start a backup, then you should find out which other plugin causes the conflict. It could be a plugin with an AWS integration when looking at where the error is triggered.

    The next major version BackWPup 4.0 should resolve errors like this, but in the current version 3.10.0, these issues may be difficult to resolve as we are providing backward compatibility towards relatively old PHP and WordPress versions.
    But if you can tell us with which other plugin the conflict occurs, we could look further into possible options.
    Thanks!

    Kind regards,
    Niklas

    Thread Starter neilgee

    (@neilgee)

    Hi Niklas,

    This is the plugin causing the issue: WooCommerce Xero

    https://woocommerce.com/products/xero/

    Regards

    Thread Starter neilgee

    (@neilgee)

    Let me know if you need a copy of it for testing purpose.

    Plugin Support Syde Niklas

    (@niklasinpsyde)

    Hi @neilgee,

    Thanks for checking.
    You could send us a copy of the conflicting plugin via mail if you include a link to this thread: [email protected]
    To be honest with you, I think it’s rather unlikely that we can find a temporary workaround that does not involve using untested pre-alpha software, but we can take a look at the interaction for sure.
    Thank you!

    Kind regards,
    Niklas

    Thread Starter neilgee

    (@neilgee)

    Ok Niklas no worries have sent an email.

    Plugin Support happyAnt

    (@duongcuong96)

    @neilgee since the case is considered as done, I close the issue here.
    Please let us know in case you need any help!

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘PHP Fatal error: Uncaught Error: Call to undefined function GuzzleHttp’ is closed to new replies.