@kapa.ai, i am getting 502 to at the time of source creation, where i can check the logs

To investigate a 502 error when creating a source, you’ll want to look at: 1. Sync / job logs in the UI - Go to the connection’s Job History tab. - Click the three dots next to the relevant job and select View logs. - You can also Download logs from the same menu to search locally for

Error

,

Exception

, or

Fail

across attempts. [[Browsing logs](https://docs.airbyte.com/platform/operator-guides/browsing-output-logs)] 2. Worker / server / Temporal pod logs (self‑hosted) Since 502s on source creation often come from backend issues (worker, Temporal, auth, etc.), check the pod/container logs for: -

airbyte-worker

(or

airbyte-abctl-worker

if installed via

abctl

) -

airbyte-server

-

airbyte-temporal

In similar 502 issues, the key clues were in the worker and temporal logs, not in the UI itself. [[502 timeout thread](https://discuss.airbyte.io/t/1207); [GKE 502 issue](https://discuss.airbyte.io/t/594); [abctl 502 issues](https://github.com/airbytehq/airbyte/issues/65567; https://github.com/airbytehq/airbyte/issues/65574)] If you share the specific worker/server logs around the time you see the 502, it’s usually possible to pinpoint the cause.