Jeremy Plummer
11/25/2025, 3:05 PMkapa.ai
11/25/2025, 3:05 PMabctl or Kubernetes. - The Airbyte instance may not be fully started, or some containers/pods may have failed to initialize. - There could be network issues, reverse proxy (e.g., nginx) misconfiguration, or resource constraints (CPU, memory) causing services to be unavailable. - Sometimes, the error can also be triggered by connector-specific issues or timeouts when attempting to connect to the source or destination. Common troubleshooting steps from the knowledge sources: - Ensure all Airbyte services are running and healthy. For Kubernetes-based deployments, check pod and deployment status with kubectl rollout status commands. - If using abctl, make sure the authentication tokens (WORKLOAD_API_BEARER_TOKEN, INTERNAL_API_AUTH_TOKEN) are set and match across relevant services. You may need to manually set and synchronize these tokens, then restart the affected deployments [[Problem with source and destination configuration on version 1.8.3](https://github.com/airbytehq/airbyte/issues/66692)]. - Restarting Airbyte containers or pods often resolves transient 502 errors, especially after initial startup or configuration changes [[Nginx reverse proxy tells 502 until containers restarted](https://discuss.airbyte.io/t/3239)]. - Review Airbyte and proxy (e.g., nginx) logs for more detailed error messages. If the error persists after these steps, it may be related to a specific connector or a deeper infrastructure issue. In such cases, reviewing the logs of the relevant Airbyte services (e.g., airbyte-abctl-worker, airbyte-temporal, etc.) can provide more insight [[source-file error 502 - Error on airbyte-abctl-worker](https://github.com/airbytehq/airbyte/issues/65574)]. In summary, the 502 error means Airbyte's backend is not able to process your request due to a service being unavailable or misconfigured. Checking service health, synchronizing tokens, and restarting services are recommended first steps.