after we upgraded airbyte from 1.7.2 to 1.80 and then also ugraded snowflake dstination verison to lastest 4.0.45 nad postgres sourc to 3.8.1 then getting below error while creatign new connection and also while retesting saved source

Looking at your screenshots, you're getting "Airbyte is temporarily unavailable. Please try again. (HTTP 502)" after upgrading from Airbyte 1.7.2 to 1.8.0, affecting both new connection creation (Postgres → Snowflake) and retesting saved sources. This is a known issue reported by multiple users after upgrades. The root cause is typically a mismatched

WORKLOAD_API_BEARER_TOKEN

between the Worker and Workload API Server pods — API calls get rejected with 401 Unauthorized, which surfaces as a 502 to the UI. [502 error issue] Workaround (for abctl-based deployments) 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 [502 error issue; similar report] For Helm-based deployments If you're using Helm, set the same token across all three deployments:

TOKEN=$(openssl rand -hex 24)

kubectl -n <your-namespace> set env deployment/airbyte-abctl-workload-api-server \
  WORKLOAD_API_AUTH_HEADER=Authorization \
  WORKLOAD_API_BEARER_TOKEN=$TOKEN

kubectl -n <your-namespace> set env deployment/airbyte-abctl-worker \
  WORKLOAD_API_AUTH_HEADER=Authorization \
  WORKLOAD_API_BEARER_TOKEN=$TOKEN

kubectl -n <your-namespace> set env deployment/airbyte-abctl-server \
  WORKLOAD_API_AUTH_HEADER=Authorization \
  WORKLOAD_API_BEARER_TOKEN=$TOKEN

kubectl -n <your-namespace> rollout restart deploy/airbyte-abctl-workload-api-server airbyte-abctl-worker airbyte-abctl-server

[502 error issue] > Note: Also be aware that Airbyte 1.7+ introduced a breaking change for ingress — the

webapp

service was merged into

server

and is no longer independently deployable. If you have custom ingress rules pointing to

airbyte-webapp

, those need to be updated as well. [ingress update docs] 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.