Summary
User is facing HTTP 504 error when trying to add a custom destination connector in Airbyte. The connector was successfully added on MacOS but not on Linux VMs. User has tried different VM types, allowed ports in firewall, and checked logs using k9s.
Question
Hi,
I haven’t been able to add a custom destination connector from the UI because it shows an HTTP 504
error.
I developed a Google AppSheet custom destination connector using Python CDK, built it locally, pushed it to a <https://hub.docker.com/r/vetatech/airbyte-destination-appsheet|public registry in Docker Hub>, and then successfully added it through the UI in my local machine by pulling from the public registry (no need to use the kind load docker-image
command). My Airbyte instance was installed in my local machine (MacOS) using abctl
.
Then, several times, I replicated the same steps in a fresh GCP VM of different types, including an n1-standard-8 (8 vCPUs, 30 GB memory), with no success; it always threw a 504 HTTP
error. Even after using the kind load docker-image
command, it kept failing and not showing the connector in the UI). I allowed all the ports, protocols, and IP addresses in the firewall of the VM and installed Airbyte using abctl
with and without --insecure-cookies
and --low-resource-mode
flags.
I followed the suggestion of <@U05JENRCF7C> of using k9s
to check the pods (thanks for taking the time ), and the logs are in the screenshots, but I can’t figure out what they mean and how to tackle it.
In short, adding a custom destination connector works in abctl-MacOS but not in abctl-Linux (tested on Debian and Ubuntu).
Has anyone encountered this issue recently? Would you happen to have any advice on how to fix it? Thanks community.
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.