HTTP 504 error when setting up custom connector as a source


User is facing HTTP 504 error when setting up a custom connector as a source in Airbyte v0.50.38 deployed on K8s via Helm. User has confirmed successful API access outside of Airbyte.


:wave: Hey y’all, I’m working on v0.50.38 OSS (deployed on K8s via Helm), and I have successfully tested and published a custom connector. However, when I go to set up that connector as a source, I get a HTTP 504. Does anyone have any suggestions? I’ve confirmed I can hit the API (HTTP 200) outside of Airbyte as well.

This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want to access the original thread.

Join the conversation on Slack

["http-504-error", "custom-connector", "airbyte-v0.50.38", "k8s-deployment", "helm", "api-access"]

I’ve validate that connection is successful through the low-code CDK for funsies too:

{"type": "LOG", "log": {"level": "INFO", "message": "Check succeeded"}}
{"type": "CONNECTION_STATUS", "connectionStatus": {"status": "SUCCEEDED"}}```

Looks like the manfiest check pod is returning with a 0 status