Troubleshooting

Table 5-2 HTTP Status Code

Problem	Solution
401	Invalid, expired, or missing token. Verify that you are using the a client ID and secret from the correct IAM service, that the token has not expired, that the token is valid (for example echo cURL script), and the token is not missing. This can also occur if requests are not routed through the expected OCI Service Gateway path, which can result in a 401 Unauthorized response.
403	Internal error (for example, misconfigured load balancer). Submit a support ticket with the details of the API invocation (for example, a cURL script)
404	Incorrect API URL, for example, unrecognized path component. Verify API URL
200	Response is: { "msg":"Internal error, cannot connect to upstream service", "detail":"java.net.ConnectException: Connection refused (Connection refused)"} Submit a support ticket with the details of the API invocation (for example, a cURL script)