Trouble accessing Airbyte UI on private server without FQDN

Summary

User is facing a 502 bad gateway error when trying to access Airbyte UI on a private server without FQDN. They have configured the host as airbyte.local and added the private IP to /etc/hosts file. Looking for alternative solutions.


Question

Hi Airbyte team, I am trying to install aibyte using kubernetes on an on prem server that has no FQDN. I followed the instructions in the documentation - https://docs.airbyte.com/deploying-airbyte/

And when it came to configuring ingress, with reference to previous slack conversations, I had put host as airbyte.local as my server don’t have a FQDN. And also added the private ip to my /etc/hosts file in my local machine from where I am trying to use the Airbyte’s Ui.

After that, when I try to access the Ui - I get 502 bad gateway error.

Please let me know if I can try something different to access Airbyte hosted on a private server



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

["airbyte", "kubernetes", "private-server", "ingress", "502-bad-gateway", "FQDN"]