@kapa.ai

unknown status code returned: Status 500

│ {"status":500,"type":"<https://reference.airbyte.com/reference/errors>","title":"unexpected-problem","detail":"An

│ unexpected problem has occurred. If this is an error that needs to be

│ addressed, please submit a pull request or github

│ issue.","documentationUrl":null,"data":{"message":"Something went wrong in

│ the connector. logs:Something went wrong in the connector. See the logs for

│ more details."}}

The error you're seeing is a generic Airbyte HTTP 500 "unexpected-problem" response. Based on the knowledge sources, this can be caused by several different underlying issues. Here are the most common causes and steps to investigate: Common Causes 1. Connector-side issue (OAuth / authentication) If you're configuring a source via OAuth, the connector itself may be failing. One known case is with Google Analytics 4 via OAuth — the connection fails with this exact error, while the service account JSON method works fine. [GA4 OAuth issue] Workaround: Try using a non-OAuth authentication method (e.g., service account JSON) if available for your connector. 2. Platform infrastructure issue (Kubernetes/Helm deployments) The error can stem from the connector-sidecar being unable to write output to the Airbyte workload API server (

DocStoreAccessException

). This is related to missing authentication tokens (

WORKLOAD_API_AUTH_HEADER

,

WORKLOAD_API_BEARER_TOKEN

) not propagating to sidecar containers. [HTTP 500 issue] Workaround (Kubernetes): Ensure

API_AUTHORIZATION_ENABLED=true

is set in your ConfigMap and that the workload API auth environment variables are properly configured. 3. Cache problem (OSS/abctl) In some cases, a stale server cache causes 500 errors when listing or configuring connectors. [500 on connector config] Workaround: Restart the

airbyte-server

component and retry. 4. Workspace not found If the workspace ID referenced in your configuration doesn't exist or isn't accessible, you may see a

ConfigNotFoundException

wrapped in a 500. [S3 Terraform 500] Workaround: Verify the workspace ID is correct and accessible. General Debugging Steps 1. Check the connector logs — The error message says "See the logs for more details." In the Airbyte UI, navigate to the connection/source and inspect the full logs. 2. Inspect the network request — Use browser DevTools (Network tab) to capture the full traceback from the API response. 3. Provide context when reporting: ◦ Airbyte version ◦ Deployment method (Docker Compose, Kubernetes/Helm, abctl) ◦ Connector name and version ◦ Whether this is a new install or a regression after an upgrade If the issue persists, consider opening a GitHub issue at airbytehq/airbyte with the above details. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.