This message was deleted.

Thinking completed Airbyte UI Access Issue on Linux Your screenshot shows

stg-airbyte-us.transperfect.com refused to connect

(

ERR_CONNECTION_REFUSED

), which means the browser cannot reach the Airbyte host. Here are the most common causes and fixes: 1. Verify Airbyte is actually running Check the status of your installation:

abctl local status

You should see output like:

Existing cluster 'airbyte-abctl' found
Found helm chart 'airbyte-abctl'
  Status: deployed
...
Airbyte should be accessible via http://localhost:8000

[abctl status] 2. You're using a custom hostname — make sure --host was set correctly Your error shows a custom domain (

stg-airbyte-us.transperfect.com

), not

localhost

. By default,

abctl

only configures an ingress rule for

localhost

. To make Airbyte accessible via a custom hostname, you must pass the

--host

flag during installation:

abctl local install --host stg-airbyte-us.transperfect.com

If you're running over plain HTTP (not HTTPS), also add `--insecure-cookies`:

abctl local install --host stg-airbyte-us.transperfect.com --insecure-cookies

[abctl EC2 guide] [OSS Quickstart] 3. Check firewall / port access Make sure the port Airbyte is listening on (default: 8000) is open in your Linux firewall or security group. If you need a different port:

abctl local install --host stg-airbyte-us.transperfect.com --port 8000

[abctl EC2 guide] 4. Confirm Docker is running Airbyte requires Docker to be running. Make sure the Docker engine is started:

sudo systemctl start docker

Summary checklist 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help., with interactive elements

@kapa.ai

INFO    Using Kubernetes provider:
            Provider: kind
            Kubeconfig: /home/glpd/.airbyte/abctl/abctl.kubeconfig
            Context: kind-airbyte-abctl
 SUCCESS  Found Docker installation: version 28.3.3
 SUCCESS  Existing cluster 'airbyte-abctl' found
  INFO    Found helm chart 'airbyte-abctl'
            Status: deployed
            Chart Version: 2.2.0
            App Version: 2.2.0
  INFO    Found helm chart 'ingress-nginx'
            Status: deployed
            Chart Version: 4.15.1
            App Version: 1.15.1
  INFO    Airbyte should be accessible via <http://localhost:8000>

Thinking completed Airbyte Status Looks Good Your

abctl local status

output shows that Airbyte is deployed and running correctly on

localhost:8000

. [abctl status] The issue is that you're trying to access it via

stg-airbyte-us.transperfect.com

, but Airbyte is only configured to listen on

localhost

. This is why the browser gets

ERR_CONNECTION_REFUSED

on that domain. Fix: Reinstall with the --host flag To make Airbyte accessible via your custom domain, reinstall with the

--host

flag:

abctl local install --host stg-airbyte-us.transperfect.com

If you're accessing it over plain HTTP (not HTTPS), also add `--insecure-cookies`:

abctl local install --host stg-airbyte-us.transperfect.com --insecure-cookies

[abctl EC2 guide] [OSS Quickstart] Alternative: Access via SSH tunnel (no reinstall needed) If you're on a remote Linux machine, you can access the UI locally by forwarding port 8000 via SSH from your local machine:

ssh -L 8000:localhost:8000 your-user@your-linux-host

Then open

http://localhost:8000

in your local browser. This avoids needing to expose the service publicly. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai got this after reinstall: /usr/bin/xdg-open: line 881: links2: command not found /usr/bin/xdg-open: line 881: elinks: command not found /usr/bin/xdg-open: line 881: links: command not found /usr/bin/xdg-open: line 881: lynx: command not found /usr/bin/xdg-open: line 881: w3m: command not found xdg-open: no method available for opening 'localhost' WARNING Failed to launch web-browser. Please launch your web-browser to access localhost SUCCESS Airbyte installation complete. A password may be required to login. The password can by found by running the command abctl local credentials

Thinking completed Installation Successful! 🎉 The warnings about

xdg-open

and missing browser commands are not errors — they just mean your Linux machine has no graphical browser available for

abctl

to auto-launch. The important line is:

SUCCESS  Airbyte installation complete.

What to do next Since you're on a remote/headless Linux machine, access the UI from your local machine's browser using an SSH tunnel:

ssh -L 8000:localhost:8000 your-user@your-linux-host

Then open your local browser and go to:

http://localhost:8000

Get your login credentials Run this on the Linux machine to retrieve your password:

abctl local credentials

[OSS Quickstart] You can also pass

--no-browser

in future installs to suppress the browser warning cleanly:

abctl local install --host stg-airbyte-us.transperfect.com --insecure-cookies --no-browser

[abctl reference] 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai done. but still cannot access airbyte ui

Thinking completed Still Can't Access the UI Since the SSH tunnel approach isn't working, let's systematically diagnose the issue. 1. Verify Airbyte pods are actually healthy

kubectl --kubeconfig ~/.airbyte/abctl/abctl.kubeconfig --namespace airbyte-abctl get pods

All pods should show

Running

or

Completed

. Share the output if any pods are in

Error

or

CrashLoopBackOff

state. [abctl FAQ] 2. Test if Airbyte is reachable locally on the Linux machine itself Run this on the Linux machine:

curl -I http://localhost:8000

• If you get an HTTP response → Airbyte is up, the issue is with your tunnel/network • If you get

Connection refused

→ Airbyte is not listening correctly 3. Check your SSH tunnel is set up correctly Make sure you're running this on your local machine (not the remote server):

ssh -L 8000:localhost:8000 -N your-user@your-linux-host

Then open

http://localhost:8000

in your local browser. 4. Check if port 8000 is actually listening On the Linux machine:

ss -tlnp | grep 8000

You should see something listening on port 8000. The knowledge sources do not contain enough information to diagnose further without knowing the output of the above commands. Please share the results and we can narrow it down. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai root@airbyte-abctl-control-plane:/# kubectl --kubeconfig ~/.airbyte/abctl/abctl.kubeconfig --namespace airbyte-abctl get pods error: stat /root/.airbyte/abctl/abctl.kubeconfig: no such file or directory

Thinking completed Kubeconfig Not Found This is a known issue — the error occurs because you're running the

kubectl

command as root, but the kubeconfig file is stored under the non-root user's home directory (

/home/glpd/.airbyte/abctl/

), not

/root/.airbyte/abctl/

. [abctl troubleshooting] Fix: Use the correct kubeconfig path From your earlier

abctl local status

output, the kubeconfig is at

/home/glpd/.airbyte/abctl/abctl.kubeconfig

. Use that full path:

kubectl --kubeconfig /home/glpd/.airbyte/abctl/abctl.kubeconfig --namespace airbyte-abctl get pods

[abctl FAQ] Also run the curl test as the correct user Switch to the

glpd

user and test:

su - glpd
curl -I http://localhost:8000

And check if port 8000 is listening:

ss -tlnp | grep 8000

Share the output of the

get pods

command and we can continue diagnosing. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai the kubernets is in side my conatiner

Thinking completed Kubernetes Running Inside a Container (kind) This is actually expected behavior with

abctl

. It uses kind (Kubernetes IN Docker), which runs the entire Kubernetes cluster inside a Docker container on your host machine. [abctl FAQ] So the correct way to interact with it is from your host machine, not from inside the container. Run these commands on your HOST machine (as glpd user)

# Check pods
kubectl --kubeconfig /home/glpd/.airbyte/abctl/abctl.kubeconfig --namespace airbyte-abctl get pods

# Test UI access
curl -I http://localhost:8000

# Check if port 8000 is listening
ss -tlnp | grep 8000

[abctl FAQ] To get back to your host machine If you're currently inside the kind container, exit it:

exit

Then make sure you're logged in as

glpd

(the user who installed Airbyte):

su - glpd

The kubeconfig and all Airbyte files are stored under

/home/glpd/.airbyte/abctl/

, so all

abctl

and

kubectl

commands must be run as that user from the host. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.