Fatal error: Uncaught GuzzleHttp\Exception\RequestException

Fatal error: Uncaught GuzzleHttp\Exception\RequestException

The Fatal error: Uncaught GuzzleHttp\Exception\RequestException: cURL error can be displayed in the Scriptcase interface in two situations
  1. When using the Google-integrated Calendar application
  2. When using the Google Drive API
So that the error doesn't happen anymore, follow the step by step below:

Download and Rename the File

1 - Download the cacert.pem file by clicking on the link below.

2 - After download, rename the cacert.pem file to curl-ca-bundle.crt


When trying to rename the file, a dialog box will appear asking you to confirm the change of the file extension. Click Yes to confirm.

Move and Edit the php.ini file

3 - After renaming the file, place it in the directory ..\NetMake\v9-php73\components\php\extras

The location of the extras folder varies depending on the settings made in your installation.
When using our installer with default values, the folder can be found in the directory below:
  ..\NetMake\v9-php73\components\PHP\


4 - Access the php.ini file located at ..\NetMake\v9-php73\components\php\


5 - After opening the file, locate the line ;curl.cainfo = ""


6 - Change the contents of this line to:
curl.cainfo = "caminho_completo\NetMake\v9\components\php\extras\curl-ca-bundle.crt"


Restart the Apache Service

7 - To finish applying the changes, restart the apache service.
Press windows + R to open the windows run.


8 - Type services.msc and click OK


9 - On the services screen, look for ApacheScriptcase9php73, select the service and click on restart.


10 - Wait for the process to end, after the end, google resources within Scriptcase can be used normally.
​




    • Related Articles

    • PHP error level - error_reporting

      The error_reporting directive in php.ini defines the levels of errors that PHP will report, the levels of errors are:   Errors and Logging Value Constant Description Note 1 E_ERROR (integer) Fatal run-time errors. These indicate errors that can not ...

    • Fatal error: Allowed memory size

      When such errors occur, it is because the memory_size feature within the server's php.ini must be increased twice or as much as necessary. 1. Find the php.ini file with these sample paths: Linux: /opt/NetMake/v9/components/apache/conf Windows: ...

    • Fatal error: Array and string offset access syntax with curly braces is no longer supported

      You can come across this error when running a login application created by a security module generated before Scriptcase 9.8. This error occurs only in an environment with PHP 8 or superior because of a change in the array elements access, that now ...

    • Fixing the Oracle Connection Error: ORA-12154

      Fixing the Oracle Connection Error: ORA-12154: TNS:could not resolve the connect identifier specified To fix this error when connecting to an Oracle database, follow the steps below: 1. Create the tnsnames.ora file Create a file named tnsnames.ora ...

    • Connection error: error_profile_test_module

      When we deploy a project and we find this type of error: "Connection error: error_profile_test_module" This error normally occurs when you use a different production environment DBMS Type than the development environment. To solve this, access your ...