Trouble accessing Airbyte webapp after installation on GCP with Helm

Slack Knowledge Base Q&A Platform Questions
, , , ,
1

Summary

User facing issues accessing Airbyte webapp on GCP after installation with Helm. Troubleshooting involves firewall rules, port forwarding, and localhost address.


Question

Hello guys, I just installed Airbyte with Helm on GCP and I’m having some problems connecting to the webapp via my browser.

I’m 100% sure that my deployment is up and running, as can be seen on screenshot_1.

I created a firewall rule that allows traffic on port 8080 (I even tested it by serving a hello-world page on port 8080 and it works - screenshot 2)

After stopping serving the hello-world page, I enabled port-forwarding on kubectl and it’s working (screenshot_3 and screenshot_4).

However, even though the firewall rule works and the port-forwarding is running, I still can’t access Airbyte from my browser. I keep getting an “Unable to connect” error message (screenshot_5).

I believe it has something to do with the “127.0.0.1” address shown in screenshot_3, as curling the page from the machine itself works.

Can someone please offer me a hand here?


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", "helm", "gcp", "firewall-rule", "port-forwarding", "localhost-address"]
2

What was the command you’ve used for SSH Tunneling may I know? I tried it using PowerShell but it kept loading with no response at all!

3

Once I had port forwarding running on the server, I Executed this command on my local terminal:

gcloud --project=<my-project-id> beta compute ssh <my-instance-name> -- -L 8080:localhost:8080 -N -f

I’m using GCP so the ssh command is a bit different, but I think you should be able to translate this to whichever cloud provider you’re using

4

Update: SSH tunnelling solved it for me and I didn’t even had to use the firewall rule I’d created. Now I’m facing an issue where Airbyte fails to set up a destination, returning a HTTP 502 error