Hi,
I am getting the error below when I make request to enroll user endpoint:
string(784) "HTTP/1.1 500 Internal Server Error Server: nginx Date: Tue, 29 Sep 2020 10:41:09 GMT Content-Type: application/json Content-Length: 255 Connection: keep-alive X-SERVED-BY: l73c015 X-CORRELATION-ID: 1601376069_678_361947923_l73c015_VDP_WS X-APP-STATUS: 500 Cache-Control: no-cache, no-store, must-revalidate Pragma: no-cache Expires: 0 ,-1 X-Frame-Options: SAMEORIGIN X-XSS-Protection: 1; mode=block X-Content-Type-Options: nosniff Strict-Transport-Security: max-age=2592000;includeSubdomains X-Cnection: close {"correlationId":"907f94c4-3b66-4be0-86b1-764e359f454d","responseDateTime":"Tue Sep 29 10:41:09 GMT 2020","responseStatus":{"code":"FAILED","message":"Request failed.","responseStatusDetails":[{"errorCode":"500","errorMessage":"Internal Server Error."}]}}
I am also wondering if this error could be as a result of the proxy values. could someone advise on what the value of the proxy params below should be, pls
//curl_setopt($curl, CURLOPT_PROXY, '');
//curl_setopt($curl, CURLOPT_PROXYPORT, '');
// curl_setopt($curl, CURLOPT_PROXYTYPE, '');
Thank you
Solved! Go to Solution
Hey @BH,
I'm happy to help you resolve the issue. Can you please try again and let us know if the issue persists. Thanks for providing the information below. I'll work on logging an incident to our engineering team to investigate the issue and someone will reach out to you soon with the incident number for tracking purposes.
Thank you for your message.
I have tried again and again with no luck. I have also tried to call another endpoint using the test data provided and the response is still 500 Internal Server Error.
Please, kindly help look into this.
Thank you
Hey @BH,
I've logged INC10213740 for our engineering team to investigate and resolve the 500 internal server error issue. Please let us know if you have questions and someone will be happy to help.
Hey @BH,
After further investigation of the logs, the engineering team found that it's failing validation because a field is null when it shouldn't be. Can you please verify that your request is properly filled out or please send us your request details?
As we obtain more information about your request, please note that the proxy parameters are only relevant if you're making API calls from behind a proxy yourself. Please let us know if you have questions, we're happy to help.
Hi @BH,
Does the issue persist? Can you share your test results with us? We haven't heard back from you in a while. If the issue persists, please confirm. If we don't hear from you, we'll close the incident INC10213740 as resolved. Let us know of any questions, we're happy to help.