@kapa.ai Minified React error #185; visit reactjs.org/docs/error-decoder.html?invariant=185 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.

This is a known Airbyte UI issue. Minified React error #185 ("Maximum update depth exceeded") occurs when a component repeatedly calls

setState

in a loop, causing React to throw to prevent infinite re-renders. There are two known contexts where this appears in Airbyte: On the /setup page (Airbyte v2.1.0) A user reported this error after installing via

abctl local install

. A workaround that resolved it was disabling Basic Auth: [React error 185 setup]

# values.yaml
global:
  auth:
    enabled: false

Then reinstall with:

abctl local install --port 8001 --values ./values.yaml

On the connection page (Airbyte v1.4.1) This was also reported when leaving the connection page idle for some time. That issue was eventually closed as stale/potentially fixed in newer versions. [React error 185 connection] General troubleshooting tips (from the Airbyte team response on issue #76834): • Try a different browser or a fresh incognito/private window to rule out cached webapp assets. • Check if the error appears immediately on page load or only after interacting with specific fields. • Review webapp pod logs:

kubectl logs -n airbyte-abctl deploy/airbyte-abctl-webapp

• Check the browser Console and Network tabs at the moment the error appears for a component stack or repeating failed request. If you're still experiencing this, consider joining the Airbyte Community Slack or, if you're a Cloud customer, opening a support ticket. 👍 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 doing global: auth: enabled: false is dangerous

You're absolutely right — disabling Airbyte's built-in authentication should only be done if you have another layer of access control in place. The docs explicitly mention this: [Authentication docs] > "There may be times when you wish to turn off authentication, for instance if you have already configured a proxy that authenticates users with your organization's SSO." If you do disable it, the knowledge sources recommend securing your instance through other means: [Security docs] • Deploy Airbyte in a private network or use a firewall to restrict which IPs can reach your host. • Deploy behind a reverse proxy (e.g. nginx) and handle authentication and SSL there. Example nginx config:

server {
  listen 443 ssl;
  server_name airbyte.<your-domain>.com;
  client_max_body_size 200M;
  ssl_certificate <path-to-your-cert>.crt.pem;
  ssl_certificate_key <path-to-your-key>.key.pem;

  location / {
    proxy_pass http://127.0.0.1:8000;
    proxy_set_header Cookie $http_cookie;
    proxy_read_timeout 3600;
  }
}

• On GCP: use Identity-Aware Proxy • On AWS: use AWS Systems Manager Session Manager So the workaround of disabling auth is only safe as a temporary diagnostic step or when another authentication mechanism is already protecting access. Without one, your Airbyte instance — including all stored credentials — would be openly accessible. 👍 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