@kapa.ai ERROR Timed out waiting for ingress ERROR Unable to install Airbyte locally ERROR browser liveness check failed: context deadline exceeded

Troubleshooting: "Timed out waiting for ingress" / "browser liveness check failed" This error typically occurs during

abctl local install

when the ingress (nginx) or Airbyte services take too long to become ready. Here are the known causes and fixes: 1. Network / Proxy Issues If you're behind a corporate proxy, the Kind container (

airbyte-abctl-control-plane

) may not be able to pull images. [nginx/ingress-nginx issue] Workaround: Exec into the Kind container and verify connectivity:

docker exec -it airbyte-abctl-control-plane bash
curl https://ifconfig.io

If it fails, configure your proxy settings inside the container, then re-run

abctl local install

. 2. Insufficient Resources On constrained machines (e.g., 2 vCPUs, low RAM), pods take much longer to start and can trigger timeouts. [image pull issue] Recommendation: Use at least 4 CPUs and 8 GB RAM (8/16 GB recommended). You can also try:

abctl local install --low-resource-mode

3. Ingress Verification Timeout (Known Limitation) There is a hardcoded 1-minute ingress verification timeout in

abctl

. On slower VMs or machines, pods can legitimately take longer to become responsive, causing a false failure. [deployment reliability issue] This is a known issue — the Airbyte team has proposed making this timeout configurable. 4. Retry After Uninstall Sometimes a clean reinstall resolves the issue: [nginx/ingress-nginx issue]

abctl local uninstall
abctl local install

5. Use Helm Instead of abctl If

abctl

continues to fail, consider using the Helm-based deployment as an alternative: [troubleshooting docs] > Follow the Helm installation docs for a more manual but controllable setup. 6. Check Docker Basics Verify Docker is working correctly on your system:

docker run hello-world

If this fails, fix Docker first before retrying the Airbyte install. [troubleshooting docs] 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.