Troubleshooting Errors

Suggest Edits

Why is my integration offline?

Apono integration can be offline for different reasons, such as invalid network communication, misconfigured credentials, or other misconfigurations.
To see why integration is offline, view the status message on the integration.

After you've identified the error, here is a quick guide to help resolve it.

Infrastructure Errors

1. Connector Unreachable

Error message: Connector Connector Name is unreachable.
The error occurs when the connector is not reachable by Apono.

What can cause this error?

  • The Connector is down
    The Connector can be down if it is deleted from the environment.
  • There is a network connectivity issue
    If the Connector is on a network with no outbound communication allowed, it will not be discovered by Apono.

Troubleshooting

Identifying the issue:

  • Checking the Connector in AWS CloudFormation.
  • Checking the Connector in GCP Deployment Manager.
  • Checking the Connector Deployment is up.

Resolving the issue:

  1. When the Connector is up again, it automatically reconnects Apono.
  2. Refresh the integration to see the updated status.

2. Integration Unreachable

Error message: Integration Name is unreachable.
The error occurs when the integration is not reachable to the Connector.

What can cause this error?

  • The integrated service is down
    The Integration can be down if the integrated service is down in the environment.
  • There is a network connectivity issue
    The Connector should have network access to the integrated service/resource.

Troubleshooting

Identifying the issue:

  • Validate the Instance is up and running
  • Validate the Subnet you've specified when integrating
  • Validate the Security Group you've specified when integrating
  • Validate network connectivity in GCP or AWS
  • Validate network connectivity in Kubernetes

Resolving the issue:

  1. When the network connectivity issue is resolved, or the integration service is up again, the will Connector will automatically reconnect to the integrated resources.
  2. You can force an update by selecting Refresh.

3. Secret Unreachable

Error message: Secret Secret Name is unreachable.
The error occurs when the secret configured for in the integration is not reachable by the Connector.

What can cause this error?

  • The secret does not exist
    No secret with the specified name was found. Check for typos
  • Missing permissions to the secret
    The Connector does not have sufficient privileges to access the secret.

Troubleshooting

Identifying the issue:

  • Validate the region as you've specified in the integration.
  • Validate the secret name as you've specified in the integration.
  • Validate you've tagged the secret with the tag apono-connector-read: true

Resolving the issue:

  1. When the error is resolved, the integration status will be updated automatically.
  2. You can force an update by selecting Refresh.

4. Secret Invalid

Error message: Secret Secret Name is invalid.
The error occurs when the secret is misconfigured in the secret store.

What can cause this error?

  • Username field is missing
  • Password field is missing
  • Username or password incorrect

Troubleshooting

Identifying the issue:

  • Navigate to your secret in the secret store and validate the.username and password fields exist.
  • Copy the username and password, try to connect to the integration (based on the integration parameters specified in the Apono Integration page), and try using the secret manually to validate it is correct.

Resolving the issue:

  1. When the secret parameters have been corrected, the integration status will be updated automatically.
  2. You can force an update by selecting Refresh.

Application Errors

1. Integration Name resource discovery failed

Error message: Discovery of resources failed.
The error occurs when the Connector fails to sync resources from an integration.

What can cause this error?

  • Missing permissions

Troubleshooting

Identifying the issue:

  • Validate that you have added the secret has the necessary permissions required by the integration.
  • Navigate to your secret in the secret store and validate the.username and password fields exist.
  • Copy the username and password and try to connect to the integration (based on the integration parameters specified in the Apono Integration page) and try using the secret manually to validate it is correct.

Resolving the issue:

  1. When the secret parameters have been corrected, the integration status will be updated automatically.
  2. You can force an update by selecting Refresh.

2. Failed Provisioning

Error message: X failed requests in the last day
The error occurs when requests in Apono fail to invoke the provisioning functions properly.

What can cause this error?

  • Missing permissions

Troubleshooting?

Identifying the issue:

  • Validate that you have added the secret has the necessary permissions required by the integration.
  • Navigate to your secret in the secret store and validate the.username and password fields exist.
  • Copy the username and password, try to connect to the integration (based on the integration parameters specified in the Apono Integration page), and try using the secret manually to validate it is correct.
  • Validate that you can grant and revoke access to a user.

Resolving the issue:
For each failed attempt, you can view the issue in the Activity Page.

Updated 6 months ago