Once i run Airbyte on my local, i am seeing the following error.

{
  "i18nKey": "errors.http.badGateway",
  "i18nParams": {
    "status": 502
  },
  "name": "HttpError",
  "requestId": "b9H3Q3Pg6aZKn4LMM313xE",
  "request": {
    "url": "/api/v1/web_backend/config",
    "method": "GET"
  },
  "status": 502,
  "response": "<!DOCTYPE html>\n<html>\n<head>\n<title>Error</title>\n<style>\nhtml { color-scheme: light dark; }\nbody { width: 35em; margin: 0 auto;\nfont-family: Tahoma, Verdana, Arial, sans-serif; }\n</style>\n</head>\n<body>\n<h1>An error occurred.</h1>\n<p>Sorry, the page you are looking for is currently unavailable.<br/>\nPlease try again later.</p>\n<p>If you are the system administrator of this resource then you should check\nthe error log for details.</p>\n<p><em>Faithfully yours, nginx.</em></p>\n</body>\n</html>\n"
}

HTTP 502 Bad Gateway on Local Airbyte Install This is a known issue with local Airbyte installations (using

abctl

). The root cause is typically a missing or mismatched bearer token between the worker and the workload API server, causing an

Unauthorized

error that surfaces as a 502. Workaround You can fix this by manually generating and applying a matching auth token to both services. Run the following commands:

KUBECONFIG="${HOME}/.airbyte/abctl/abctl.kubeconfig"
NAMESPACE="airbyte-abctl"
SECRET_NAME="airbyte-abctl-workload-api-secrets"

WORKLOAD_TOKEN=$(openssl rand -hex 32)
echo "Generated token: $WORKLOAD_TOKEN"

kubectl delete secret "$SECRET_NAME" -n "$NAMESPACE" --ignore-not-found --kubeconfig "$KUBECONFIG"

kubectl create secret generic "$SECRET_NAME" \
  --from-literal=bearer-token="$WORKLOAD_TOKEN" \
  -n "$NAMESPACE" \
  --kubeconfig "$KUBECONFIG"

kubectl set env deploy/airbyte-abctl-workload-api-server \
  -n "$NAMESPACE" \
  WORKLOAD_API_BEARER_TOKEN="$WORKLOAD_TOKEN" \
  --kubeconfig "$KUBECONFIG"

kubectl set env deploy/airbyte-abctl-worker \
  -n "$NAMESPACE" \
  WORKLOAD_API_BEARER_TOKEN="$WORKLOAD_TOKEN" \
  --kubeconfig "$KUBECONFIG"

kubectl rollout restart deploy/airbyte-abctl-workload-api-server -n "$NAMESPACE" --kubeconfig "$KUBECONFIG"
kubectl rollout restart deploy/airbyte-abctl-worker -n "$NAMESPACE" --kubeconfig "$KUBECONFIG"

[GitHub Issue #65574] Alternatively, if you prefer to set the token manually from inside the container:

# Find your container ID
docker ps

# Enter the container
docker exec -it <containerID> bash

# Inside the container:
BEARER_TOKEN=$(openssl rand -hex 16)

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"

kubectl -n airbyte-abctl rollout restart deployment airbyte-abctl-worker
kubectl -n airbyte-abctl rollout restart deployment airbyte-abctl-workload-api-server

[GitHub Issue #66692] Notes • This has been reported as a platform infrastructure issue, not a connector-specific bug, and has been routed to the Airbyte platform team for a permanent fix. [GitHub Issue #65574] • Multiple users have confirmed the above workaround resolves the issue across different connectors. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.