Your credentials were correct, but the server failed to set a cookie. You appear to have deployed over HTTP. Make sure you have disabled secure cookies. @kapa.ai

This error occurs because you've deployed Airbyte over HTTP (non-HTTPS) but haven't disabled the secure cookies requirement. Here are the available fixes: Fix 1: Upgrade abctl (Recommended) Upgrade

abctl

to version 0.29 or higher, as a bug in previous versions caused this message to appear incorrectly. [Troubleshoot Deploy] Fix 2: Use the --insecure-cookies flag Reinstall with the

--insecure-cookies

flag:

abctl local install --host example.com --insecure-cookies

[OSS Quickstart] Fix 3: Use a values.yaml file (if the flag doesn't work) Some users on newer versions (v0.30.x) have reported that the

--insecure-cookies

flag alone doesn't resolve the issue. In that case, you can configure it via a

values.yaml

file: [Cookie Security Settings]

global:
  auth:
    security:
      cookieSecureSetting: "false"

Then apply it during install:

abctl local install --host example.com --values ./values.yaml

> ⚠️ Security note: Disabling secure cookies allows cookies to be transmitted over non-secure connections. Only use this setting when HTTPS is not available. 👍 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 i install on single node

Based on your context (single node, HTTP deployment getting the secure cookies error), the most reliable workaround reported by users is to use a

values.yaml

file alongside the

--insecure-cookies

flag: [Cookie Security Settings]

abctl local install --host <YOUR_IP_OR_HOSTNAME> --insecure-cookies --values ./values.yaml

With

values.yaml

containing:

global:
  auth:
    security:
      cookieSecureSetting: "false"

If that still doesn't work, some users on v0.30.x have had success with this more explicit configuration: [--insecure-cookies issue]

global:
  auth:
    enabled: true
    cookieSecureSetting: "false"
    security:
      cookieSecureSetting: "false"

server:
  extraEnv:
    - name: AB_COOKIE_SECURE
      value: "false"
    - name: AB_COOKIE_SAME_SITE
      value: "Lax"

Note that if your single node only has an IP address (no hostname), make sure to pass that IP to

--host

. Some users have reported that nodes without a proper hostname can still have issues even with the flag set. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

i installed using abctl only created credentials. @kapa.ai

It sounds like you've installed Airbyte with

abctl

and now need to retrieve your login credentials. You can do that by running:

abctl local credentials

This will output something like: [OSS Quickstart]

Credentials:
Email: your@email.com
Password: a-random-password
Client-Id: 03ef466c-5558-4ca5-856b-4960ba7c161b
Client-Secret: m2UjnDO4iyBQ3IsRiy5GG3LaZWP6xs9I

Use the Email and Password to log into Airbyte in your browser. If the email shows as

[not set]

, you can set it manually with: [abctl reference]

abctl local credentials --email your@email.com

You can also change your password at any time:

abctl local credentials --password YourStrongPasswordExample

> Note: Some users have reported needing to run

abctl local credentials

with

sudo

to retrieve the password successfully. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

Minified React error #185; visit https://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. @kapa.ai

This is a known UI issue in Airbyte. The Minified React error #185 means "Maximum update depth exceeded" — a component is triggering infinite state updates. Known Cause & Fix This error has been reported specifically on the

/setup

page when Basic Auth is enabled. A user confirmed that disabling Basic Auth resolved it: [React error #185 on setup page]

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

With `values.yaml`:

global:
  auth:
    enabled: false

Other Things to Try 1. Try a different browser or incognito/private window — cached webapp assets can sometimes cause this. 2. Check if the error appears immediately or only after interacting with a specific field/step on the page. 3. Check webapp pod logs for any related errors:kubectl logs -n airbyte-abctl deploy/airbyte-abctl-webapp 4. Check the browser Console and Network tabs at the moment the error appears — these often reveal a repeating failed request or component stack pointing to the root cause. [React error #185 on setup page] A similar error has also been reported on the connection page after leaving it idle, though that issue was closed without a confirmed fix. [React error #185 on connection page] Given your earlier context (single-node HTTP install with

abctl

), the auth-related workaround above is the most likely fix. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.