LogoLogo
Documentation and Guides
Documentation and Guides
  • ABOUT APONO
    • Why Choose Apono
    • Security and Architecture
    • Glossary
  • GETTING STARTED
    • How Apono Works
    • Getting started
    • Access Discovery
    • Integrating with Apono
  • CONNECTORS AND SECRETS
    • Apono Integration Secret
    • High Availability for Connectors
    • Installing a connector with Docker
    • Manage integrations
    • Manage connectors
    • S3 Storage
  • AWS ENVIRONMENT
    • AWS Overview
    • Apono Connector for AWS
      • Installing a connector on EKS Using Terraform
      • Updating a connector in AWS
      • Installing a connector on AWS ECS using Terraform
    • AWS Integrations
      • Integrate an AWS account or organization
        • Auto Discover AWS RDS Instances
        • AWS Best Practices
      • Amazon Redshift
      • RDS PostgreSQL
      • AWS RDS MySQL
      • Integrate with EKS
      • AWS Lambda Custom Integration
      • EC2 via Systems Manager Agent (SSM)
  • AZURE ENVIRONMENT
    • Apono Connector for Azure
      • Install an Azure connector on ACI using Azure CLI
      • Install an Azure connector on ACI using PowerShell
      • Install an Azure connector on ACI using Terraform
      • Updating a connector in Azure
    • Azure Integrations
      • Integrate with Azure Management Group or Subscription
        • Auto Discover Azure SQL Databases
      • Azure MySQL
      • Azure PostgreSQL
      • Integrate with AKS
  • GCP ENVIRONMENT
    • Apono Connector for GCP
      • Installing a GCP connector on Cloud Run using CLI
      • Installing a GCP connector on GKE using CLI (Helm)
      • Installing a GCP connector on GKE using Terraform
      • Updating a connector in Google Cloud
    • GCP Integrations
      • Integrate a GCP organization or project
      • CloudSQL - MySQL
      • CloudSQL - PostgreSQL
      • Google Cloud Functions
      • Integrate with GKE
      • AlloyDB
  • KUBERNETES ENVIRONMENT
    • Apono Connector for Kubernetes
      • Installing a connector on Kubernetes with AWS permissions
      • Updating a Kubernetes connector
    • Kubernetes Integrations
      • Integrate with Self-Managed Kubernetes
  • ADDITIONAL INTEGRATIONS
    • Databases and Data Repositories
      • Microsoft SQL Server
      • MongoDB
      • MongoDB Atlas
      • MongoDB Atlas Portal
      • MySQL
      • Oracle Database
      • PostgreSQL
      • RabbitMQ
      • Redis Cloud (Redislabs)
      • Snowflake
      • Vertica
      • MariaDB
    • Network Management
      • SSH Servers
      • RDP Servers
      • Windows Domain Controller
      • AWS EC2 SSH Servers
      • Azure VM SSH Servers
      • Installing the Apono HTTP Proxy
    • Development Tools
      • GitHub
      • Rancher
    • Identity Providers
      • Okta SCIM
      • Okta Groups
      • Okta SSO for Apono logins
      • Google Workspace (Gsuite)
      • Google Workspace (GSuite) Groups
      • Azure Active Directory (Microsoft Entra ID)
      • Azure Active Directory (Entra ID) Groups
      • Jumpcloud
      • JumpCloud Groups
      • OneLogin
      • OneLogin Group
      • LDAP Groups
      • The Manager Attribute in Access Flows
      • HiBob
      • Ping Identity SSO
    • Incident Response Integrations
      • Opsgenie
      • PagerDuty
      • VictorOps (Splunk On-Call)
      • Zenduty
    • ChatOps Integrations
      • Slack integration
      • Teams integration
      • Backstage Integration
    • Secret Management
      • 1Password
  • WEBHOOK INTEGRATIONS
    • Webhooks Overview
    • Anomaly Webhook
    • Audit Log Webhook
    • Request Webhook
      • Custom Webhooks
      • Communications and Notifications
        • Slack Outbound Webhooks
        • Teams
        • Outlook and Gmail (Using Azure Logic App)
      • ITSM
        • Freshdesk
        • Jira
        • ServiceNow
        • Zendesk
        • Freshservice
        • ServiceDesk Plus
      • Logs and SIEMs
        • Coralogix
        • Datadog
        • Logz.io
        • Grafana
        • New Relic
        • SolarWinds
        • Sumo Logic
        • Cortex
        • Logpoint
        • Splunk
        • Microsoft Sentinel
      • Orchestration and workflow builders
        • Okta Workflows
        • Torq
    • Integration Webhook
    • Webhook Payload References
      • Audit Log Webhook Payload Schema Reference
      • Webhook Payload Schema Reference
    • Manage webhooks
    • Troubleshoot a webhook
    • Manual Webhook
      • ITSM
        • PagerDuty
  • ACCESS FLOWS
    • Access Flows
      • What are Access Flows?
    • Create Access Flows
      • Self Serve Access Flows
      • Automatic Access Flows
      • Access Duration
    • Manage Access Flows
      • Right Sizing
    • Revoke Access
    • Dynamic Access Management
      • Resource and Integration Owners
    • Common Use Cases
      • Ensuring SLA
      • Protecting PII and Customer Data
      • Production Stability and Management
      • Break Glass Protocol
    • Create Bundles
    • Manage Bundles
  • ACCESS REQUESTS AND APPROVALS
    • Slack
      • Requesting Access with Slack
      • Approving Access with Slack
      • Reviewing historical requests with Slack
    • Teams
      • Requesting Access with Teams
      • Approving Access with Teams
    • CLI
      • Install and manage the Apono CLI
      • Requesting Access with CLI
    • Web Portal
      • Requesting Access with the Web Portal
      • Approving Access with the Web Portal
      • Reviewing historical requests with the Web Portal
    • Freshservice
    • Favorites
  • Inventory
    • Inventory Overview
    • Inventory
    • Access Scopes
    • Risk Scores
    • Apono Query Language
  • AUDITS AND REPORTS
    • Activity Overview
      • Activity
      • Create Reports
      • Manage Reports
    • Compliance: Audit and Reporting
    • Auditing Access in Apono
    • Admin Audit Log (Syslog)
  • HELP AND DEBUGGING
    • Integration Status Page
    • Troubleshooting Errors
  • ARCHITECTURE AND SECURITY
    • Anomaly Detection
    • Multi-factor Authentication
    • Credentials Rotation Policy
    • Periodic User Cleanup & Deletion
    • End-user Authentication
    • Personal API Tokens
  • User Administration
    • Role-Based Access Control (RBAC) Reference
    • Create Identities
    • Manage Identities
Powered by GitBook
On this page
  • Troubleshooting Errors
  • Why is my integration offline?
  • Infrastructure Errors
  • 1. Connector Unreachable
  • 2. Integration Unreachable
  • 3. Secret Unreachable
  • 4. Secret Invalid
  • Application Errors
  • 1. Integration Name resource discovery failed
  • 2. Failed Provisioning

Was this helpful?

Export as PDF
  1. HELP AND DEBUGGING

Troubleshooting Errors

PreviousIntegration Status PageNextAnomaly Detection

Last updated 7 months ago

Was this helpful?

Troubleshooting Errors

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 .

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 .

integration
Activity Page