Hi @kapa.ai I am not able to access my self hosted Airbyte deployed on Kubernetes When accessed domain where I have hosted it nothing is getting shown at https://airbyte.<company_domain>.io/ Getting below error -> Through Developer Tools: Failed to load resource: the server responded with a status of 404 ()

I'm sorry to hear that you're having trouble accessing your self-hosted Airbyte instance. Based on the information provided, it seems like there might be an issue with your ingress configuration or port forwarding setup. Here are a few things you can check: 1. Ingress Configuration: Ensure that your ingress configuration is correctly set up to route traffic to the Airbyte webapp service. You can refer to the [Airbyte documentation on configuring ingress](https://docs.airbyte.com/enterprise-setup/implementation-guide#configuring-ingress) for more details. 2. Port Forwarding: If you're trying to access Airbyte locally, you might need to set up port forwarding. The command to do this should look something like this:

bash export POD_NAME=$(kubectl get pods --namespace airbyte -l "<http://app.kubernetes.io/name=webapp|app.kubernetes.io/name=webapp>" -o jsonpath="{.items[0].metadata.name}")   export CONTAINER_PORT=$(kubectl get pod --namespace airbyte $POD_NAME -o jsonpath="{.spec.containers[0].ports[0].containerPort}")   kubectl --namespace airbyte port-forward $POD_NAME 8080:$CONTAINER_PORT

You can find more details in the [Airbyte documentation on setting up port forwarding](https://docs.airbyte.com/deploying-airbyte/#6-set-up-port-forward-for-ui-access). 3. Namespace: If you're using a custom namespace, you need to specify the namespace in the port-forward command. You can find more details in this [Airbyte forum post](https://discuss.airbyte.io/t/259). 4. Server Logs: Check the server logs for any errors. You can do this by running

kubectl logs <pod_name>

where

<pod_name>

is the name of your Airbyte server pod. This [Airbyte forum post](https://discuss.airbyte.io/t/2408) provides an example of how to check the server logs. If you're still having trouble after checking these things, please provide more details about your setup (e.g., the output of

kubectl get pods

,

kubectl get svc

, and any error messages you're seeing in the logs) so we can help you troubleshoot further.

@kapa.ai I have correct 1. ingress config 2. I am not accessing the server locally 3. Below are my webapp pods logs 10.30.0.207 - - [19/Oct/20241640:24 +0000] "GET /api/v1/health HTTP/1.1" 200 18 "-" "ELB-HealthChecker/2.0" "-" 10.30.0.207 - - [19/Oct/20241640:24 +0000] "GET /api/v1/health HTTP/1.1" 200 18 "-" "ELB-HealthChecker/2.0" "-" 10.30.0.207 - - [19/Oct/20241640:33 +0000] "GET /index.html HTTP/1.1" 200 19534 "-" "kube-probe/1.27+" "-" 10.30.0.207 - - [19/Oct/20241640:39 +0000] "GET /api/v1/health HTTP/1.1" 200 18 "-" "ELB-HealthChecker/2.0" "-" 10.30.0.207 - - [19/Oct/20241640:43 +0000] "GET /index.html HTTP/1.1" 200 19534 "-" "kube-probe/1.27+" "-" 10.30.0.207 - - [19/Oct/20241640:53 +0000] "GET /index.html HTTP/1.1" 200 19534 "-" "kube-probe/1.27+" "-" 10.30.0.207 - - [19/Oct/20241640:54 +0000] "GET /api/v1/health HTTP/1.1" 200 18 "-" "ELB-HealthChecker/2.0" "-" 10.30.0.207 - - [19/Oct/20241641:03 +0000] "GET /index.html HTTP/1.1" 200 19534 "-" "kube-probe/1.27+" "-" 10.30.0.207 - - [19/Oct/20241641:09 +0000] "GET /api/v1/health HTTP/1.1" 200 18 "-" "ELB-HealthChecker/2.0" "-" 10.30.0.207 - - [19/Oct/20241641:09 +0000] "GET /api/v1/health HTTP/1.1" 200 18 "-" "ELB-HealthChecker/2.0" "-" 10.30.0.207 - - [19/Oct/20241641:13 +0000] "GET /index.html HTTP/1.1" 200 19534 "-" "kube-probe/1.27+" "-" Output of kubectl get pods -n airbyte NAME READY STATUS RESTARTS AGE airbyte-airbyte-bootloader 0/1 Completed 0 8m30s airbyte-connector-builder-server-7f4c5897c6-s5qv9 1/1 Running 0 4h28m airbyte-cron-75f86c96d8-mp6gh 1/1 Running 0 4h28m airbyte-db-0 1/1 Running 0 4h28m airbyte-minio-0 1/1 Running 0 4h28m airbyte-pod-sweeper-pod-sweeper-76d944479c-rfj6k 1/1 Running 0 4h28m airbyte-server-6c7fdddff4-rr5bc 1/1 Running 0 4h28m airbyte-temporal-655f9b95b4-wxr4h 1/1 Running 0 4h28m airbyte-webapp-7cd9c46d6d-dl4dj 1/1 Running 0 4h28m airbyte-webapp-7cd9c46d6d-zng8w 1/1 Running 0 4h28m airbyte-worker-75c9ddd6bc-f6ks7 1/1 Running 0 4h28m airbyte-workload-api-server-79bdb99ff6-gsh2v 1/1 Running 0 4h28m airbyte-workload-launcher-645cdc499d-b8jrk 1/1 Running 0 4h28m kubectl get svc -n airbyte NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE airbyte-airbyte-connector-builder-server-svc NodePort 172.20.166.3 none 80:31467/TCP 4h28m airbyte-airbyte-server-svc ClusterIP 172.20.224.159 none 8001/TCP 4h28m airbyte-airbyte-webapp-svc NodePort 172.20.84.96 none 80:32390/TCP 4h28m airbyte-db-svc ClusterIP 172.20.160.33 none 5432/TCP 4h29m airbyte-minio-svc ClusterIP 172.20.129.88 none 9000/TCP 4h28m airbyte-temporal ClusterIP 172.20.95.4 none 7233/TCP 4h28m airbyte-workload-api-server-svc ClusterIP 172.20.7.217 none 8007/TCP 4h28m

A message from kapa.ai

If you have confirmed that your ingress configuration is correct and you're not accessing the server locally, there are a few other things you can check: 1. Host Configuration: Ensure that you have correctly specified the

--host

flag when running the

abctl local install

command. This should be the Fully Qualified Domain Name (FQDN) of the host which is hosting Airbyte. For example,

abctl local install --host airbyte.company.example

. By specifying the

--host

flag, Airbyte will be accessible to both

localhost

and the FQDN passed to the

--host

flag. You can find more details in the [Airbyte documentation on running Airbyte](https://docs.airbyte.com/using-airbyte/getting-started/oss-quickstart#2-run-airbyte). 2. Port Configuration: By default,

abctl

will listen on port 8000. If port 8000 is already in use or you require a different port, you can specify this by passing the

--port

flag to the

local install

command. For example,

abctl local install --port 6598

. Ensure that the security group configured for your instance allows traffic in on the port that you deploy Airbyte on. You can find more details in the [Airbyte documentation on using an EC2 instance with abctl](https://docs.airbyte.com/using-airbyte/getting-started/oss-quickstart#using-an-ec2-instance-with-abctl). 3. Firewall Rules: Ensure that your firewall rules allow traffic to the port that Airbyte is running on. For example, if you're using Redshift as a destination, you need to specifically allow port 5439, as mentioned in this [Airbyte forum post](https://discuss.airbyte.io/t/4146). If you're still having trouble after checking these things, please provide more details about your setup (e.g., the output of

kubectl get pods

,

kubectl get svc

, and any error messages you're seeing in the logs) so we can help you troubleshoot further.

A message from kapa.ai

Based on the logs and the output of your

kubectl get pods

and

kubectl get svc

commands, it seems like your Airbyte services are running correctly. The 200 status codes in your logs indicate that the health checks are passing, and your pods and services are all up and running. However, the issue seems to be with accessing the Airbyte webapp service externally. Here are a few things you can check: 1. Service Type: In your services list, the

airbyte-airbyte-webapp-svc

service is of type

NodePort

. This means it's only accessible within the cluster. If you want to access it externally, you might need to change the service type to

LoadBalancer

or use an Ingress controller. You can find more details in the [Kubernetes documentation on services](https://kubernetes.io/docs/concepts/services-networking/service/). 2. Ingress Controller: If you're using an Ingress controller, make sure it's correctly configured to route traffic to the

airbyte-airbyte-webapp-svc

service. The [Airbyte documentation on configuring ingress](https://docs.airbyte.com/enterprise-setup/implementation-guide#configuring-ingress) might be helpful. 3. DNS Configuration: Ensure that your DNS is correctly configured to point to your Kubernetes cluster. The domain

airbyte.<company_domain>.io

should resolve to the IP address of your Kubernetes cluster. 4. Firewall Rules: Check your firewall rules to ensure that they allow traffic to the port that the

airbyte-airbyte-webapp-svc

service is running on. If you're still having trouble after checking these things, please provide more details about your setup (e.g., your ingress configuration, the output of

kubectl describe svc airbyte-airbyte-webapp-svc

, and any error messages you're seeing in the logs) so we can help you troubleshoot further.