Blank page and 304 error on Airbyte webapp URL after deployment on EKS

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

Summary

After deploying Airbyte v1.2.0 using helm-charts on EKS, encountering a blank page and 304 error at the webapp URL despite everything being up and running. Works when service is exposed locally. Seeking assistance for this issue.


Question

Hello team,

I have deployed airbyte v1.2.0 using helm-charts on k8s(EKS) , everything is up and running but yet at webapp URL Iam having a blank page and getting 304
Iam using ImplementationSpecific path /airbyte . Also when I expose the service locally it works.
Anyone faced the same issue?


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", "v1.2.0", "helm-charts", "EKS", "webapp", "304 error", "blank page", "service", "expose", "issue"]
2

I see static files are looking for / path only, not sure how to rewrite it to look for /airbyte.

3

You need to dig more into ingress/nginx/reverse proxy topics
https://docs.nginx.com/nginx/admin-guide/web-server/reverse-proxy/
https://serverfault.com/questions/379675/nginx-reverse-proxy-url-rewrite

4

I think looks like this
https://github.com/airbytehq/airbyte/issues/8167

5

But not sure if someone did perform any workarounds

6

You might also check those configuration options in values.yaml:

  airbyteUrl: "..."
webapp:
  url: "..."```
7

Nope the same issue, I see still static files trying to be pulled of / path only