General issues, or "An error occurred. Please try again or contact our support"
To troubleshoot the problem, please reproduce the error and take a look into the WHMCS gateway log. The gateway log records all requests and responses made by the module, so it may contain useful information about the cause of the problem.
If you don't find any relevant entries in the gateway log, try enabling the module debug log and reproduce the error again. This may create a log entry with more detailed information about the issue.
By reviewing the logs, you should be able to determine the cause of the problem. If the error message is not clear, please provide the request and response in plain text. This will allow us to better understand the issue and assist in finding a resolution.
Also, please ensure that you followed the installation guide.
HTTP status 500
If the callback file is manually accessed via the browser, an error response will be output, and the HTTP status will be set to 500.
The callback file is not designed to be manually accessed. If it is, an HTTP status code of 500 is the expected response. For security purposes, only calls from Stripe are permitted. If you wish to test the callback, you may do so using the Stripe test mode if necessary.
If a Stripe callback results in an HTTP status of 500, it's likely that the webhook secret key is incorrect. In such a case, relevant information will be logged in the module debug log. However, please note that the module debug log will also contain entries regarding manual accesses of the callback file, which should be ignored.