Troubleshooting endpoint errors

If an error occurs when StorageGRID attempts to communicate with a specific endpoint, a message is displayed on the Dashboard and the error message is shown in the Last Error column on the Endpoints page.

Determining if an error has occurred

If any endpoint errors have occurred within the past 7 days, the Dashboard in the Tenant Manager displays an alert message. You can go the Endpoints page to see more details about the error.
endpoint error message on the Dashboard

When you go to the Endpoints page, you can review the more detailed error message in the Last Error column. This column displays only the most recent error message for each endpoint, and it indicates how long ago the error occurred. Errors in red occurred within the past 7 days.


screenshot of Endpoints page showing Last Error column

Checking if an error is still current

Some errors might continue to be shown in the Last Error column even after they are resolved. To see if an error is current or to force the removal of a resolved error from the table, select the radio button for the endpoint, and click Test.

Clicking Test causes StorageGRID to validate that the endpoint exists and that it can be reached with the current credentials. The connection to the endpoint is validated from one node at each site.

Resolving endpoint errors

If an endpoint error occurs, you can use the message in the Last Error column to help determine what is causing the error. Some errors might require you to edit the endpoint to resolve the issue. For example, a CloudMirroring error can occur if StorageGRID is unable to access the destination S3 bucket because it does not have the correct access permissions or the access key has expired. The message is "Either the endpoint credentials or the destination access needs to be updated," and the details are "AccessDenied" or "InvalidAccessKeyId."

If you need to edit the endpoint to resolve an error, clicking Save causes StorageGRID to validate the updated endpoint and confirm that it can be reached with the current credentials. The connection to the endpoint is validated from one node at each site.