error trying to re-install after abctl local uninstall:

SUCCESS  Installed Helm Chart nginx/ingress-nginx:
            Name: ingress-nginx
            Namespace: ingress-nginx
            Version: 4.14.3
            AppVersion: 1.14.3
            Release: 1
  INFO    No existing Ingress found, creating one
 SUCCESS  Ingress created
  DEBUG   Event watcher completed.
  ERROR   Timed out waiting for ingress
  ERROR   Unable to install Airbyte locally
  ERROR   browser liveness check failed: context deadline exceeded

The knowledge sources don’t contain a definitive fix for this exact “Timed out waiting for ingress / browser liveness check failed” error on re‑install, but they do describe related

abctl local install

/ uninstall behaviors and workarounds. A few concrete things you can try, all based on those sources: 1. Confirm the previous install is really gone After running:

bash    abctl local uninstall

also remove abctl’s local state if you’re OK starting completely fresh:

bash    abctl local uninstall --persisted    rm -rf ~/.airbyte/abctl

This is the documented way to “stop running containers and delete all data,” and is also what users have done when a previous install left behind problematic state. [[abctl docs](https://docs.airbyte.com/platform/deploying-airbyte/abctl#install-and-manage-local-airbyte-instances); [migration schema issue](https://github.com/airbytehq/airbyte/issues/58864)] 2. Check that ingress is actually working The logs show the nginx/ingress-nginx chart installs and the Ingress object is created, but

abctl

times out waiting for it to become reachable. Similar issues have been linked to: - Network / proxy problems (images or traffic blocked). - SSL / corporate proxy interception. - Port / ingress conflicts with an existing ingress controller (e.g., Traefik on k3s). [[ingress stuck issue](https://github.com/airbytehq/airbyte/issues/56386)] Steps (adapted from those reports): - Get into the control-plane container and test outbound connectivity:

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

If this fails, you likely need to configure proxy / certs inside that container before re‑running

abctl local install

. [[ingress stuck comments](https://github.com/airbytehq/airbyte/issues/56386)] - If you’re on k3s or have another ingress controller already running, there may be a port conflict with nginx‑ingress; users report nginx‑ingress install failing in that case. [[ingress stuck comments](https://github.com/airbytehq/airbyte/issues/56386)] The knowledge sources don’t document an

abctl

flag to skip nginx‑ingress, so the only documented workaround there is to follow the Helm‑only deployment path instead of

abctl

. 3. Try a completely fresh install cycle Some users with ingress‑related or stuck installs report success after a full uninstall + reinstall cycle, even though the root cause wasn’t fully understood:

bash    abctl local uninstall    abctl local install

[[ingress stuck comments](https://github.com/airbytehq/airbyte/issues/56386)] 4. If it still fails The docs and issues don’t provide a specific remedy for the “browser liveness check failed: context deadline exceeded” message. That check is essentially

abctl

waiting for the UI to become reachable through the ingress; if it times out, it’s almost always an ingress / networking / proxy / port‑conflict problem, but the exact debugging steps beyond what’s above are not described in the provided sources. If you can share whether you’re behind a corporate proxy, using k3s/minikube/kind, or have another ingress controller running, that would help narrow which of the documented workarounds is most relevant.