New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Guzzle/Http calls fail in WHMCS #5
Comments
Confirmed. Not able to use the addon. Getting this error: [WHMCS Application] ERROR: GuzzleHttp\Exception\ClientException: Client error: |
What error are you confirming? The error you have pasted here seems to be raised because you've used incorrect credentials. This is most likely a misconfiguration in your installation. The error you are getting is:
To be clear, the specific bug this issue addresses only affects the internal update mechanism in WHMCS, all other functionality is unaffected. |
Ok, thanks for clarifying. Will check the configuration.
…--
sjoerd
:wq
Op 21 jul. 2019 om 14:20 heeft ju5t ***@***.***> het volgende geschreven:
What error are you confirming? The error you have pasted here seems to be raised because you've used incorrect credentials. This is most likely a misconfiguration in your installation. The error you are getting is:
Error 401: {"error":"No access to bank"}
To be clear, this specific bug this issue addresses only affects the internal update mechanism in WHMCS, all other functionality is unaffected.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
The latest version of WHMCS should resolve this. Closing this issue. Please open a new issue if you see this on the latest version of WHMCS, in that case, there might be something else going on. |
picqer/moneybird-php-client
requires Guzzle 6 or higher. WHMCS includes version 5. As WHMCS includes third party modules in its update process it fails because it suddenly uses Guzzle version 6 instead of 5. Some of the parameters WHMCS passes to Guzzle are invalid in version 6.Unfortunately, this breaks the update mechanism in WHMCS.
The text was updated successfully, but these errors were encountered: