Skip to content

Connection Errors#

This page covers the most common third-party connection issues for end users — not server deployment.

Customer-selected third-party connectors#

Invalid API key#

Applies to optional connectors that require customer-provided API keys or tokens.

Common symptoms:

  • Returns 401 / Unauthorized
  • Message says key invalid, quota exceeded, or forbidden

Resolution:

  • Re-check that the API key was copied in full
  • Confirm whether your account tier supports the API you are calling
  • If using a team-shared key, ask your admin whether it has expired or the quota is exhausted

AWS tools#

Invalid credentials#

Common errors:

  • InvalidClientTokenId
  • NoCredentialsError
  • RequestExpired

Resolution:

  • Check the Access Key ID and Secret Access Key
  • If using temporary credentials, confirm the Session Token has not expired
  • Confirm the default region is entered correctly
  • Severe clock skew can also cause request expiry errors

Insufficient permissions#

Common errors:

  • AccessDenied
  • UnauthorizedOperation

Resolution:

  • Ask your admin to grant the required read-only permissions
  • Check the permission requirements in the specific tool's documentation

Elasticsearch / Kibana / Splunk#

Certificate error#

Common symptoms:

  • Self-signed certificate error
  • SSL verification failure

Resolution:

  • Follow the tool configuration page instructions to disable strict certificate verification
  • Or switch to the correct certificate and endpoint provided by your admin

Authentication failure#

Common symptoms:

  • 401 Unauthorized
  • invalid token

Resolution:

  • Check the API key, username, or password
  • Do not mix multiple authentication methods
  • Confirm your account can access the target instance

Jira / Confluence#

Invalid token or wrong URL#

Resolution:

  • Confirm the platform URL matches your organization's actual address
  • Regenerate or update the API token
  • Do not mix Cloud and Server/Data Center authentication formats