akhilesh.kumar178
07/16/2026, 6:36 PMkapa.ai
07/16/2026, 6:36 PMWORKLOAD_API_BEARER_TOKEN between the Worker and Workload API Server pods. Workload API calls get rejected with a 401 Unauthorized, which surfaces as a 502 error in the UI. [HTTP 502 Issue]
Fix / Workaround If you're running Airbyte via abctl (self-hosted), follow these steps:
1. Find your container ID:
docker ps
2. Enter the container:
docker exec -it <containerID> bash
3. Inside the container, run the following:
# Check current pod status
kubectl -n airbyte-abctl get pods
# Generate and apply matching auth tokens to both services
BEARER_TOKEN=$(openssl rand -hex 16)
echo "Generated token: $BEARER_TOKEN"
kubectl -n airbyte-abctl set env deployment/airbyte-abctl-worker \
WORKLOAD_API_BEARER_TOKEN="$BEARER_TOKEN" \
INTERNAL_API_AUTH_TOKEN="$BEARER_TOKEN"
kubectl -n airbyte-abctl set env deployment/airbyte-abctl-workload-api-server \
WORKLOAD_API_BEARER_TOKEN="$BEARER_TOKEN"
# Restart both services
kubectl -n airbyte-abctl rollout restart deployment airbyte-abctl-worker
kubectl -n airbyte-abctl rollout restart deployment airbyte-abctl-workload-api-server
# Wait for rollouts to complete
kubectl -n airbyte-abctl rollout status deployment airbyte-abctl-worker
kubectl -n airbyte-abctl rollout status deployment airbyte-abctl-workload-api-server
[HTTP 502 Fix] [Related Issue]
Alternative (Helm deployment) If you're on a Helm-based deployment, you can also set the token across all three deployments:
TOKEN=$(openssl rand -hex 24)
kubectl -n airbyte-abctl set env deployment/airbyte-abctl-workload-api-server WORKLOAD_API_AUTH_HEADER=Authorization WORKLOAD_API_BEARER_TOKEN=$TOKEN
kubectl -n airbyte-abctl set env deployment/airbyte-abctl-worker WORKLOAD_API_AUTH_HEADER=Authorization WORKLOAD_API_BEARER_TOKEN=$TOKEN
kubectl -n airbyte-abctl set env deployment/airbyte-abctl-server WORKLOAD_API_AUTH_HEADER=Authorization WORKLOAD_API_BEARER_TOKEN=$TOKEN
kubectl -n airbyte-abctl rollout restart deploy/airbyte-abctl-workload-api-server airbyte-abctl-worker airbyte-abctl-server
[HTTP 502 Fix]
Multiple users have confirmed this resolves the issue. After the rollout completes, try retesting your Postgres source again. đ 0 button đ 0 button âšī¸ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.