Summary
Error 502 occurs when using a new API connector in Airbyte, despite successful testing. UI displays ‘Airbyte is temporarily unavailable HTTP(502)’. How to resolve?
Question
Hey all. I have Airbyte running locally via abctl local install. I create a new API connector and test it successfully, but when I go to use the connector I get a 502 on the check_connection browser call, and I get an error in the UI that says something like “Airbyte is temporarily unavailable HTTP(502).” Is there something I can do to get around this?
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
["error-502", "api-connector", "abctl-local-install", "check-connection", "airbyte-unavailable"]
for debugging
install kind https://kind.sigs.k8s.io/docs/user/quick-start/#installation and check logs
kind export logs --name=airbyte-abctl kind-logs
in kind-logs directory you will find all the logs
Hi <@U07SL82GSGY> I wonder if you managed to resolve this issue? As I’m having the same issue.
Hey Ohad, I haven’t had time to do what Przemysław suggested. If you have time to try that and post your results here that would be great.
Hi <@U07SL82GSGY>, yeah, I did that, and I got lots logs, but it didn’t lead me anywhere.
The issue in my case is the lack of internet access from the container, to verify it you can do:
docker exec -it [container_id] /bin/bash
apt update # check if you get any timeouts, if you do it means you have the same issue as mine.```
In my case, I have Tailscale installed on the box, and I'm using and Exit Node, which is causing this issue.
I'm still trying to figure out how to resolve it, as a temporary test removing the Exit Node has resolved the issue for me.
I think I was just low on RAM when I was trying this originally. I was able to setup a source and destination once a freed up more memory.