Oracle Cloud Infrastructure Documentation

HTTP Status Code Errors

HTTP Status codes you might encounter when using Vision, and the steps to troubleshoot them.

HTTP Status Code: 400 Bad Request

Fix a process that returns the HTTP Status Code: 400 Bad Request.

A process doesn't return expected results.

You see this error: 400 Bad Request

Cause:

A client error.

Remedy:

Check the request URI, headers, and body for more information.

HTTP Status Code: 401 Unauthorized

Fix a process that returns the HTTP Status Code: 401 Unauthorized.

A process doesn't return expected results.

You see this error: 401 Unauthorized

Cause:

The request lacks valid authentication credentials.

Remedy:

Confirm the correct policies have been added. The policies include those for accessing Object Storage, should the pretrained or customer model need access to Object Storage.

HTTP Status Code: 404 Not Found

Fix a process that returns the HTTP Status Code: 404 Not Found.

A process doesn't return expected results.

You see this error: 404 Not Found

Cause:

The resource can't be found.

Remedy:

Check the request to confirm you're accessing the correct resource.

HTTP Status Code: 409 Conflict

Fix a process that returns the HTTP Status Code: 409 Conflict.

A process doesn't return expected results.

You see this error: 409 Conflict

Cause:

The request conflicts with the current state of the resource.

Remedy:

Wait for the resource to move to an appropriate state.

HTTP Status Code: 429 Too Many Requests

Fix a process that returns the HTTP Status Code: 429 Too Many Requests.

A process doesn't return expected results.

You see this error: 429 Too Many Requests

Cause:

The requests are being throttled.

Remedy:

Increase the resource limits. Log a ticket with Oracle Support.

HTTP Status Code: 500 Internal Server Error

Fix a process that returns the HTTP Status Code: 500 Internal Server Error.

A process doesn't return expected results.

You see this error: 500 Internal Server Error

Cause:

The server had an unexpected issue.

Remedy:

Review the server log files.